* 2022-12-20 03:11:25 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-20 03:11:25 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-20 03:11:25 (3844) [INFO] 
* 2022-12-20 03:11:25 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-20 03:11:25 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-20 03:11:25 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-20 03:11:25 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-20 03:11:25 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-20 03:11:25 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-20 03:11:26 (3874) [INFO] 
* 2022-12-20 03:11:26 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-20 03:11:26 (3844) [INFO] 
* 2022-12-20 03:11:36 (3858) [INFO] 
* 2022-12-20 03:11:36 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-20 03:11:36 (3874) [INFO] 
* 2022-12-20 03:11:36 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-20 03:11:36 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-20 03:11:36 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-20 03:11:36 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7_ss0Va9gu/ea_profile.json
* 2022-12-20 03:11:37 (1664) [INFO] Backed up EA4 profile to /tmp/7_ss0Va9gu/ea_profile.json
* 2022-12-20 03:11:37 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-21 03:09:16 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-21 03:09:16 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-21 03:09:16 (3844) [INFO] 
* 2022-12-21 03:09:16 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-21 03:09:16 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-21 03:09:16 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-21 03:09:16 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-21 03:09:16 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-21 03:09:16 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-21 03:09:16 (3874) [INFO] 
* 2022-12-21 03:09:16 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-21 03:09:16 (3844) [INFO] 
* 2022-12-21 03:09:30 (3858) [INFO] 
* 2022-12-21 03:09:30 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-21 03:09:30 (3874) [INFO] 
* 2022-12-21 03:09:30 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-21 03:09:30 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-21 03:09:30 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-21 03:09:30 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IzHo43wh7C/ea_profile.json
* 2022-12-21 03:09:31 (1664) [INFO] Backed up EA4 profile to /tmp/IzHo43wh7C/ea_profile.json
* 2022-12-21 03:09:31 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-21 03:09:31 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-22 03:10:05 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-22 03:10:05 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-22 03:10:05 (3844) [INFO] 
* 2022-12-22 03:10:05 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-22 03:10:06 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-22 03:10:06 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-22 03:10:06 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-22 03:10:06 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-22 03:10:06 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-22 03:10:06 (3874) [INFO] 
* 2022-12-22 03:10:06 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-22 03:10:06 (3844) [INFO] 
* 2022-12-22 03:10:21 (3858) [INFO] 
* 2022-12-22 03:10:21 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-22 03:10:21 (3874) [INFO] 
* 2022-12-22 03:10:21 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-22 03:10:21 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-22 03:10:21 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-22 03:10:21 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jB7Lx31sRe/ea_profile.json
* 2022-12-22 03:10:22 (1664) [INFO] Backed up EA4 profile to /tmp/jB7Lx31sRe/ea_profile.json
* 2022-12-22 03:10:22 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-22 03:10:22 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-23 03:09:21 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-23 03:09:21 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-23 03:09:21 (3844) [INFO] 
* 2022-12-23 03:09:22 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-23 03:09:22 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-23 03:09:22 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-23 03:09:22 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-23 03:09:22 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-23 03:09:22 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-23 03:09:22 (3874) [INFO] 
* 2022-12-23 03:09:22 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-23 03:09:22 (3844) [INFO] 
* 2022-12-23 03:09:35 (3858) [INFO] 
* 2022-12-23 03:09:35 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-23 03:09:35 (3874) [INFO] 
* 2022-12-23 03:09:35 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-23 03:09:35 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-23 03:09:35 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-23 03:09:35 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b5cW1Ebz4S/ea_profile.json
* 2022-12-23 03:09:35 (1664) [INFO] Backed up EA4 profile to /tmp/b5cW1Ebz4S/ea_profile.json
* 2022-12-23 03:09:36 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-23 03:09:36 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-24 03:10:08 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-24 03:10:08 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-24 03:10:08 (3844) [INFO] 
* 2022-12-24 03:10:08 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-24 03:10:08 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-24 03:10:08 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-24 03:10:08 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-24 03:10:08 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-24 03:10:09 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-24 03:10:09 (3874) [INFO] 
* 2022-12-24 03:10:09 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-24 03:10:09 (3844) [INFO] 
* 2022-12-24 03:10:26 (3858) [INFO] 
* 2022-12-24 03:10:26 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-24 03:10:26 (3874) [INFO] 
* 2022-12-24 03:10:26 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-24 03:10:26 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-24 03:10:26 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-24 03:10:26 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EXYeBgQxAE/ea_profile.json
* 2022-12-24 03:10:27 (1664) [INFO] Backed up EA4 profile to /tmp/EXYeBgQxAE/ea_profile.json
* 2022-12-24 03:10:27 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-24 03:10:27 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-25 03:10:17 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-25 03:10:17 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-25 03:10:17 (3844) [INFO] 
* 2022-12-25 03:10:17 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-25 03:10:17 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-25 03:10:17 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-25 03:10:17 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-25 03:10:17 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-25 03:10:17 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-25 03:10:17 (3874) [INFO] 
* 2022-12-25 03:10:17 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-25 03:10:17 (3844) [INFO] 
* 2022-12-25 03:10:32 (3858) [INFO] 
* 2022-12-25 03:10:32 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-25 03:10:32 (3874) [INFO] 
* 2022-12-25 03:10:32 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-25 03:10:32 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-25 03:10:32 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-25 03:10:32 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3rIN6E1G5f/ea_profile.json
* 2022-12-25 03:10:33 (1664) [INFO] Backed up EA4 profile to /tmp/3rIN6E1G5f/ea_profile.json
* 2022-12-25 03:10:33 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-25 03:10:34 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-26 03:09:04 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2022-12-26 03:09:04 (3538) [ERROR] Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 585, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1395, in doCommand
    base.repos.populateSack(mdtype='all', cacheonly=1)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
    sack._retrieve_async(repo, data)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
    if not self._check_uncompressed_db_gen(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
    cached=repo.cache)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
    return decompress(filename, dest=dest, check_timestamps=True)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
    os.utime(out, (fi.st_mtime, fi.st_mtime))
OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2022-12-26 03:09:04 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2022-12-26 03:09:05 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-26 03:09:05 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-26 03:09:05 (3844) [INFO] 
* 2022-12-26 03:09:05 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-26 03:09:05 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-26 03:09:05 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-26 03:09:05 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-26 03:09:05 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-26 03:09:05 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-26 03:09:05 (3874) [INFO] 
* 2022-12-26 03:09:05 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-26 03:09:05 (3844) [INFO] 
* 2022-12-26 03:09:26 (3858) [INFO] 
* 2022-12-26 03:09:26 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-26 03:09:27 (3874) [INFO] 
* 2022-12-26 03:09:27 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-26 03:09:27 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-26 03:09:27 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-26 03:09:27 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n20Q1J3d8b/ea_profile.json
* 2022-12-26 03:09:27 (1664) [INFO] Backed up EA4 profile to /tmp/n20Q1J3d8b/ea_profile.json
* 2022-12-26 03:09:28 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-26 03:09:28 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-27 03:09:24 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2022-12-27 03:09:24 (3538) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/0707f359719dff892a3166fe4990f5c7e641f02d46ef1ce74049259fc52042a2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://linux.darkpenguin.net/distros/CentOS/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2022-12-27 03:09:24 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2022-12-27 03:09:24 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-27 03:09:24 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-27 03:09:24 (3844) [INFO] 
* 2022-12-27 03:09:25 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-27 03:09:25 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-27 03:09:25 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-27 03:09:25 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-27 03:09:25 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-27 03:09:25 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-27 03:09:25 (3874) [INFO] 
* 2022-12-27 03:09:25 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-27 03:09:25 (3844) [INFO] 
* 2022-12-27 03:09:39 (3858) [INFO] 
* 2022-12-27 03:09:39 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-27 03:09:39 (3874) [INFO] 
* 2022-12-27 03:09:39 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-27 03:09:39 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-27 03:09:39 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-27 03:09:39 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jaBHmcSqEj/ea_profile.json
* 2022-12-27 03:09:40 (1664) [INFO] Backed up EA4 profile to /tmp/jaBHmcSqEj/ea_profile.json
* 2022-12-27 03:09:40 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-27 03:09:40 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-28 03:09:46 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-28 03:09:46 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-28 03:09:46 (3844) [INFO] 
* 2022-12-28 03:09:46 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-28 03:09:46 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-28 03:09:46 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-28 03:09:46 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-28 03:09:46 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-28 03:09:46 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-28 03:09:46 (3874) [INFO] 
* 2022-12-28 03:09:46 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-28 03:09:46 (3844) [INFO] 
* 2022-12-28 03:09:59 (3858) [INFO] 
* 2022-12-28 03:09:59 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-28 03:09:59 (3874) [INFO] 
* 2022-12-28 03:09:59 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-28 03:09:59 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-28 03:09:59 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-28 03:09:59 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Z1Xi4RXBIZ/ea_profile.json
* 2022-12-28 03:10:00 (1664) [INFO] Backed up EA4 profile to /tmp/Z1Xi4RXBIZ/ea_profile.json
* 2022-12-28 03:10:01 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-28 03:10:01 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-29 03:09:19 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-29 03:09:19 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-29 03:09:19 (3844) [INFO] 
* 2022-12-29 03:09:19 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-29 03:09:19 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-29 03:09:19 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-29 03:09:19 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-29 03:09:19 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-29 03:09:19 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-29 03:09:19 (3874) [INFO] 
* 2022-12-29 03:09:19 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-29 03:09:19 (3844) [INFO] 
* 2022-12-29 03:09:32 (3858) [INFO] 
* 2022-12-29 03:09:32 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-29 03:09:32 (3874) [INFO] 
* 2022-12-29 03:09:32 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-29 03:09:32 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-29 03:09:32 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-29 03:09:32 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IJBjJhP5h6/ea_profile.json
* 2022-12-29 03:09:32 (1664) [INFO] Backed up EA4 profile to /tmp/IJBjJhP5h6/ea_profile.json
* 2022-12-29 03:09:32 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-29 03:09:33 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-30 03:09:45 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2022-12-30 03:09:45 (3538) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/08b312fb485dd84595e8ba8d7776587b188ca7aebf3cc695367b87daeed70945-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
* 2022-12-30 03:09:45 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2022-12-30 03:09:46 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-30 03:09:46 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-30 03:09:46 (3844) [INFO] 
* 2022-12-30 03:09:46 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-30 03:09:46 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-30 03:09:46 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-30 03:09:46 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-30 03:09:46 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-30 03:09:46 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-30 03:09:46 (3874) [INFO] 
* 2022-12-30 03:09:46 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-30 03:09:46 (3844) [INFO] 
* 2022-12-30 03:10:01 (3858) [INFO] 
* 2022-12-30 03:10:01 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-30 03:10:01 (3874) [INFO] 
* 2022-12-30 03:10:01 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-30 03:10:01 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-30 03:10:01 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-30 03:10:01 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vWshUzm8c3/ea_profile.json
* 2022-12-30 03:10:02 (1664) [INFO] Backed up EA4 profile to /tmp/vWshUzm8c3/ea_profile.json
* 2022-12-30 03:10:02 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-30 03:10:03 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2022-12-31 03:09:49 (3370) [INFO] Checking if your system is up to date: 
* 2022-12-31 03:09:49 (3843) [INFO] Running: /usr/bin/yum clean all
* 2022-12-31 03:09:49 (3844) [INFO] 
* 2022-12-31 03:09:50 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2022-12-31 03:09:50 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2022-12-31 03:09:50 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2022-12-31 03:09:50 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2022-12-31 03:09:50 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2022-12-31 03:09:50 (3858) [INFO] Cleaning up list of fastest mirrors
* 2022-12-31 03:09:50 (3874) [INFO] 
* 2022-12-31 03:09:50 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2022-12-31 03:09:50 (3844) [INFO] 
* 2022-12-31 03:10:02 (3858) [INFO] 
* 2022-12-31 03:10:02 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2022-12-31 03:10:02 (3874) [INFO] 
* 2022-12-31 03:10:02 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2022-12-31 03:10:02 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2022-12-31 03:10:02 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2022-12-31 03:10:02 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KNCH0hw9sZ/ea_profile.json
* 2022-12-31 03:10:03 (1664) [INFO] Backed up EA4 profile to /tmp/KNCH0hw9sZ/ea_profile.json
* 2022-12-31 03:10:03 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2022-12-31 03:10:03 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-01 03:09:31 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-01 03:09:31 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-01 03:09:31 (3844) [INFO] 
* 2023-01-01 03:09:32 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-01 03:09:32 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-01 03:09:32 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-01 03:09:32 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-01 03:09:32 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-01 03:09:32 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-01 03:09:32 (3874) [INFO] 
* 2023-01-01 03:09:32 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-01 03:09:32 (3844) [INFO] 
* 2023-01-01 03:09:45 (3858) [INFO] 
* 2023-01-01 03:09:45 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-01 03:09:45 (3874) [INFO] 
* 2023-01-01 03:09:45 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-01 03:09:45 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-01 03:09:45 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-01 03:09:45 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/47NNuUh26k/ea_profile.json
* 2023-01-01 03:09:46 (1664) [INFO] Backed up EA4 profile to /tmp/47NNuUh26k/ea_profile.json
* 2023-01-01 03:09:46 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-01 03:09:46 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-02 03:09:00 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-02 03:09:00 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-02 03:09:00 (3844) [INFO] 
* 2023-01-02 03:09:00 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-02 03:09:00 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-02 03:09:00 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-02 03:09:00 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-02 03:09:00 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-02 03:09:01 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-02 03:09:01 (3874) [INFO] 
* 2023-01-02 03:09:01 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-02 03:09:01 (3844) [INFO] 
* 2023-01-02 03:09:16 (3858) [INFO] 
* 2023-01-02 03:09:16 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-02 03:09:16 (3874) [INFO] 
* 2023-01-02 03:09:16 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-02 03:09:16 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-02 03:09:16 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-02 03:09:16 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jPvKgySTMr/ea_profile.json
* 2023-01-02 03:09:17 (1664) [INFO] Backed up EA4 profile to /tmp/jPvKgySTMr/ea_profile.json
* 2023-01-02 03:09:17 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-02 03:09:17 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-03 03:09:07 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-03 03:09:07 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-03 03:09:07 (3844) [INFO] 
* 2023-01-03 03:09:07 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-03 03:09:07 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-03 03:09:07 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-03 03:09:07 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-03 03:09:07 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-03 03:09:07 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-03 03:09:07 (3874) [INFO] 
* 2023-01-03 03:09:07 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-03 03:09:07 (3844) [INFO] 
* 2023-01-03 03:09:23 (3858) [INFO] 
* 2023-01-03 03:09:23 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-03 03:09:23 (3874) [INFO] 
* 2023-01-03 03:09:23 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-03 03:09:23 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-03 03:09:23 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-03 03:09:23 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dolOwwBeVE/ea_profile.json
* 2023-01-03 03:09:24 (1664) [INFO] Backed up EA4 profile to /tmp/dolOwwBeVE/ea_profile.json
* 2023-01-03 03:09:24 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-03 03:09:24 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-04 03:09:18 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-04 03:09:18 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-04 03:09:18 (3844) [INFO] 
* 2023-01-04 03:09:18 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-04 03:09:18 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-04 03:09:18 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-04 03:09:18 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-04 03:09:18 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-04 03:09:18 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-04 03:09:18 (3874) [INFO] 
* 2023-01-04 03:09:18 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-04 03:09:18 (3844) [INFO] 
* 2023-01-04 03:09:34 (3858) [INFO] 
* 2023-01-04 03:09:34 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-04 03:09:34 (3874) [INFO] 
* 2023-01-04 03:09:34 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-04 03:09:34 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-04 03:09:34 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-04 03:09:34 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IPC29LbOsB/ea_profile.json
* 2023-01-04 03:09:34 (1664) [INFO] Backed up EA4 profile to /tmp/IPC29LbOsB/ea_profile.json
* 2023-01-04 03:09:35 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-04 03:09:35 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-05 03:09:20 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-01-05 03:09:20 (3538) [ERROR] http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/0707f359719dff892a3166fe4990f5c7e641f02d46ef1ce74049259fc52042a2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2023-01-05 03:09:20 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-05 03:09:20 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-05 03:09:20 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-05 03:09:20 (3844) [INFO] 
* 2023-01-05 03:09:20 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-05 03:09:21 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-05 03:09:21 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-05 03:09:21 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-05 03:09:21 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-05 03:09:21 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-05 03:09:21 (3874) [INFO] 
* 2023-01-05 03:09:21 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-05 03:09:21 (3844) [INFO] 
* 2023-01-05 03:09:33 (3858) [INFO] 
* 2023-01-05 03:09:33 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-05 03:09:33 (3874) [INFO] 
* 2023-01-05 03:09:33 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-05 03:09:33 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-05 03:09:33 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-05 03:09:33 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eKVDs1WFXT/ea_profile.json
* 2023-01-05 03:09:33 (1664) [INFO] Backed up EA4 profile to /tmp/eKVDs1WFXT/ea_profile.json
* 2023-01-05 03:09:34 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-05 03:09:34 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-06 03:09:11 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-06 03:09:11 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-06 03:09:11 (3844) [INFO] 
* 2023-01-06 03:09:11 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-06 03:09:11 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-06 03:09:11 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-06 03:09:11 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-06 03:09:11 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-06 03:09:11 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-06 03:09:11 (3874) [INFO] 
* 2023-01-06 03:09:11 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-06 03:09:11 (3844) [INFO] 
* 2023-01-06 03:09:27 (3858) [INFO] 
* 2023-01-06 03:09:27 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-06 03:09:27 (3874) [INFO] 
* 2023-01-06 03:09:27 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-06 03:09:27 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-06 03:09:27 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-06 03:09:27 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NoEx1eY98y/ea_profile.json
* 2023-01-06 03:09:28 (1664) [INFO] Backed up EA4 profile to /tmp/NoEx1eY98y/ea_profile.json
* 2023-01-06 03:09:28 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-06 03:09:29 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-07 03:09:44 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-07 03:09:44 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-07 03:09:44 (3844) [INFO] 
* 2023-01-07 03:09:44 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-07 03:09:45 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-07 03:09:45 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-07 03:09:45 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-07 03:09:45 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-07 03:09:45 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-07 03:09:45 (3874) [INFO] 
* 2023-01-07 03:09:45 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-07 03:09:45 (3844) [INFO] 
* 2023-01-07 03:10:02 (3858) [INFO] 
* 2023-01-07 03:10:02 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-07 03:10:02 (3874) [INFO] 
* 2023-01-07 03:10:02 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-07 03:10:02 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-07 03:10:02 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-07 03:10:02 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PaFdwVLaaU/ea_profile.json
* 2023-01-07 03:10:03 (1664) [INFO] Backed up EA4 profile to /tmp/PaFdwVLaaU/ea_profile.json
* 2023-01-07 03:10:03 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-07 03:10:03 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-08 03:10:04 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-08 03:10:04 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-08 03:10:04 (3844) [INFO] 
* 2023-01-08 03:10:04 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-08 03:10:04 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-08 03:10:04 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-08 03:10:04 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-08 03:10:04 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-08 03:10:04 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-08 03:10:04 (3874) [INFO] 
* 2023-01-08 03:10:04 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-08 03:10:04 (3844) [INFO] 
* 2023-01-08 03:10:18 (3858) [INFO] 
* 2023-01-08 03:10:18 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-08 03:10:18 (3874) [INFO] 
* 2023-01-08 03:10:18 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-08 03:10:18 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-08 03:10:18 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-08 03:10:18 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/aAoHEnAh1M/ea_profile.json
* 2023-01-08 03:10:19 (1664) [INFO] Backed up EA4 profile to /tmp/aAoHEnAh1M/ea_profile.json
* 2023-01-08 03:10:19 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-08 03:10:20 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-09 03:08:59 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-09 03:08:59 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-09 03:08:59 (3844) [INFO] 
* 2023-01-09 03:08:59 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-09 03:09:00 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-09 03:09:00 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-09 03:09:00 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-09 03:09:00 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-09 03:09:00 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-09 03:09:00 (3874) [INFO] 
* 2023-01-09 03:09:00 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-09 03:09:00 (3844) [INFO] 
* 2023-01-09 03:09:16 (3858) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-01-09 03:09:16 (3858) [INFO] Trying other mirror.
* 2023-01-09 03:09:16 (3858) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/b0965056991fe2eb78a6a2e449d7c0cae0bbec72ea933ed8c5ba1582ff3912fa-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-01-09 03:09:16 (3858) [INFO] Trying other mirror.
* 2023-01-09 03:09:23 (3858) [INFO] 
* 2023-01-09 03:09:23 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-09 03:09:23 (3874) [INFO] 
* 2023-01-09 03:09:23 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-09 03:09:23 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-09 03:09:23 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-09 03:09:23 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/o8wOMh9Hyt/ea_profile.json
* 2023-01-09 03:09:24 (1664) [INFO] Backed up EA4 profile to /tmp/o8wOMh9Hyt/ea_profile.json
* 2023-01-09 03:09:24 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-09 03:09:24 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-10 03:09:24 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-10 03:09:24 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-10 03:09:24 (3844) [INFO] 
* 2023-01-10 03:09:24 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-10 03:09:24 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-10 03:09:24 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-10 03:09:24 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-10 03:09:24 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-10 03:09:24 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-10 03:09:24 (3874) [INFO] 
* 2023-01-10 03:09:24 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-10 03:09:24 (3844) [INFO] 
* 2023-01-10 03:09:39 (3858) [INFO] 
* 2023-01-10 03:09:39 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-10 03:09:39 (3874) [INFO] 
* 2023-01-10 03:09:39 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-10 03:09:39 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-10 03:09:39 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-10 03:09:39 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S463MD8__R/ea_profile.json
* 2023-01-10 03:09:40 (1664) [INFO] Backed up EA4 profile to /tmp/S463MD8__R/ea_profile.json
* 2023-01-10 03:09:40 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-10 03:09:40 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-11 03:10:17 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-11 03:10:17 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-11 03:10:17 (3844) [INFO] 
* 2023-01-11 03:10:17 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-11 03:10:17 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-11 03:10:17 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-11 03:10:17 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-11 03:10:17 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-11 03:10:18 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-11 03:10:18 (3874) [INFO] 
* 2023-01-11 03:10:18 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-11 03:10:18 (3844) [INFO] 
* 2023-01-11 03:10:31 (3858) [INFO] 
* 2023-01-11 03:10:31 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-11 03:10:31 (3874) [INFO] 
* 2023-01-11 03:10:31 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-11 03:10:31 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-11 03:10:31 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-11 03:10:31 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/A5vVRMmvyx/ea_profile.json
* 2023-01-11 03:10:32 (1664) [INFO] Backed up EA4 profile to /tmp/A5vVRMmvyx/ea_profile.json
* 2023-01-11 03:10:32 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-11 03:10:33 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-12 03:09:28 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-01-12 03:09:28 (3538) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/0707f359719dff892a3166fe4990f5c7e641f02d46ef1ce74049259fc52042a2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-01-12 03:09:28 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-12 03:09:29 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-12 03:09:29 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-12 03:09:29 (3844) [INFO] 
* 2023-01-12 03:09:29 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-12 03:09:29 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-12 03:09:29 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-12 03:09:29 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-12 03:09:29 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-12 03:09:29 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-12 03:09:29 (3874) [INFO] 
* 2023-01-12 03:09:29 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-12 03:09:29 (3844) [INFO] 
* 2023-01-12 03:09:44 (3858) [INFO] 
* 2023-01-12 03:09:44 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-12 03:09:44 (3874) [INFO] 
* 2023-01-12 03:09:44 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-12 03:09:44 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-12 03:09:44 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-12 03:09:44 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V35PHdgosv/ea_profile.json
* 2023-01-12 03:09:44 (1664) [INFO] Backed up EA4 profile to /tmp/V35PHdgosv/ea_profile.json
* 2023-01-12 03:09:45 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-12 03:09:45 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-13 03:09:04 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-01-13 03:09:04 (3538) [ERROR] Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 585, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1395, in doCommand
    base.repos.populateSack(mdtype='all', cacheonly=1)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
    sack._retrieve_async(repo, data)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
    if not self._check_uncompressed_db_gen(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
    cached=repo.cache)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
    return decompress(filename, dest=dest, check_timestamps=True)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
    os.utime(out, (fi.st_mtime, fi.st_mtime))
OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2023-01-13 03:09:04 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-13 03:09:05 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-13 03:09:05 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-13 03:09:05 (3844) [INFO] 
* 2023-01-13 03:09:05 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-13 03:09:05 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-13 03:09:05 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-13 03:09:05 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-13 03:09:05 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-13 03:09:05 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-13 03:09:05 (3874) [INFO] 
* 2023-01-13 03:09:05 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-13 03:09:05 (3844) [INFO] 
* 2023-01-13 03:09:23 (3858) [INFO] 
* 2023-01-13 03:09:23 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-13 03:09:23 (3874) [INFO] 
* 2023-01-13 03:09:23 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-13 03:09:23 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-13 03:09:23 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-13 03:09:23 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TrhPVnfpdj/ea_profile.json
* 2023-01-13 03:09:24 (1664) [INFO] Backed up EA4 profile to /tmp/TrhPVnfpdj/ea_profile.json
* 2023-01-13 03:09:24 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-13 03:09:24 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-14 03:09:42 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-14 03:09:42 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-14 03:09:42 (3844) [INFO] 
* 2023-01-14 03:09:43 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-14 03:09:43 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-14 03:09:43 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-14 03:09:43 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-14 03:09:43 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-14 03:09:43 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-14 03:09:43 (3874) [INFO] 
* 2023-01-14 03:09:43 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-14 03:09:43 (3844) [INFO] 
* 2023-01-14 03:09:57 (3858) [INFO] 
* 2023-01-14 03:09:57 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-14 03:09:57 (3874) [INFO] 
* 2023-01-14 03:09:57 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-14 03:09:57 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-14 03:09:57 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-14 03:09:57 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RMdDWkn1ED/ea_profile.json
* 2023-01-14 03:09:57 (1664) [INFO] Backed up EA4 profile to /tmp/RMdDWkn1ED/ea_profile.json
* 2023-01-14 03:09:57 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-14 03:09:58 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-15 03:09:45 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-15 03:09:45 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-15 03:09:45 (3844) [INFO] 
* 2023-01-15 03:09:45 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-15 03:09:45 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-15 03:09:45 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-15 03:09:45 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-15 03:09:45 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-15 03:09:45 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-15 03:09:45 (3874) [INFO] 
* 2023-01-15 03:09:45 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-15 03:09:45 (3844) [INFO] 
* 2023-01-15 03:09:58 (3858) [INFO] 
* 2023-01-15 03:09:58 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-15 03:09:58 (3874) [INFO] 
* 2023-01-15 03:09:58 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-15 03:09:58 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-15 03:09:58 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-15 03:09:58 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lnWzpEJEAE/ea_profile.json
* 2023-01-15 03:09:59 (1664) [INFO] Backed up EA4 profile to /tmp/lnWzpEJEAE/ea_profile.json
* 2023-01-15 03:09:59 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-15 03:10:00 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-16 03:09:19 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-16 03:09:19 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-16 03:09:19 (3844) [INFO] 
* 2023-01-16 03:09:19 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-16 03:09:19 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-16 03:09:19 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-16 03:09:19 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-16 03:09:19 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-16 03:09:19 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-16 03:09:19 (3874) [INFO] 
* 2023-01-16 03:09:19 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-16 03:09:19 (3844) [INFO] 
* 2023-01-16 03:09:34 (3858) [INFO] 
* 2023-01-16 03:09:34 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-16 03:09:34 (3874) [INFO] 
* 2023-01-16 03:09:34 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-16 03:09:34 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-16 03:09:34 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-16 03:09:34 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OHmJP5WlsC/ea_profile.json
* 2023-01-16 03:09:35 (1664) [INFO] Backed up EA4 profile to /tmp/OHmJP5WlsC/ea_profile.json
* 2023-01-16 03:09:35 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-16 03:09:35 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-17 03:09:03 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-17 03:09:03 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-17 03:09:03 (3844) [INFO] 
* 2023-01-17 03:09:03 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-17 03:09:03 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-17 03:09:03 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-17 03:09:03 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-17 03:09:03 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-17 03:09:03 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-17 03:09:03 (3874) [INFO] 
* 2023-01-17 03:09:03 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-17 03:09:03 (3844) [INFO] 
* 2023-01-17 03:09:22 (3858) [INFO] 
* 2023-01-17 03:09:22 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-17 03:09:22 (3874) [INFO] 
* 2023-01-17 03:09:22 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-17 03:09:22 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-17 03:09:22 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-17 03:09:22 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Dvb17PxQM0/ea_profile.json
* 2023-01-17 03:09:23 (1664) [INFO] Backed up EA4 profile to /tmp/Dvb17PxQM0/ea_profile.json
* 2023-01-17 03:09:23 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-17 03:09:23 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-18 03:09:26 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-18 03:09:26 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-18 03:09:26 (3844) [INFO] 
* 2023-01-18 03:09:26 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-18 03:09:27 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-18 03:09:27 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-18 03:09:27 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-18 03:09:27 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-18 03:09:27 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-18 03:09:27 (3874) [INFO] 
* 2023-01-18 03:09:27 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-18 03:09:27 (3844) [INFO] 
* 2023-01-18 03:09:40 (3858) [INFO] 
* 2023-01-18 03:09:40 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-18 03:09:40 (3874) [INFO] 
* 2023-01-18 03:09:40 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-18 03:09:40 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-18 03:09:40 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-18 03:09:40 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yRAOIxHaCO/ea_profile.json
* 2023-01-18 03:09:41 (1664) [INFO] Backed up EA4 profile to /tmp/yRAOIxHaCO/ea_profile.json
* 2023-01-18 03:09:41 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-18 03:09:42 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-19 03:10:33 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-19 03:10:33 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-19 03:10:33 (3844) [INFO] 
* 2023-01-19 03:10:33 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-19 03:10:34 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-19 03:10:34 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-19 03:10:34 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-19 03:10:34 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-19 03:10:34 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-19 03:10:34 (3874) [INFO] 
* 2023-01-19 03:10:34 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-19 03:10:34 (3844) [INFO] 
* 2023-01-19 03:10:50 (3858) [INFO] 
* 2023-01-19 03:10:50 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-19 03:10:50 (3874) [INFO] 
* 2023-01-19 03:10:50 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-19 03:10:50 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-19 03:10:50 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-19 03:10:50 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bSPUdly02t/ea_profile.json
* 2023-01-19 03:10:50 (1664) [INFO] Backed up EA4 profile to /tmp/bSPUdly02t/ea_profile.json
* 2023-01-19 03:10:50 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-19 03:10:51 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-20 03:10:44 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-20 03:10:44 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-20 03:10:44 (3844) [INFO] 
* 2023-01-20 03:10:45 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-20 03:10:45 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-20 03:10:45 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-20 03:10:45 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-20 03:10:45 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-20 03:10:45 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-20 03:10:45 (3874) [INFO] 
* 2023-01-20 03:10:45 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-20 03:10:45 (3844) [INFO] 
* 2023-01-20 03:10:58 (3858) [INFO] 
* 2023-01-20 03:10:58 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-20 03:10:58 (3874) [INFO] 
* 2023-01-20 03:10:58 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-20 03:10:58 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-20 03:10:58 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-20 03:10:58 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/094Syr6mEx/ea_profile.json
* 2023-01-20 03:10:59 (1664) [INFO] Backed up EA4 profile to /tmp/094Syr6mEx/ea_profile.json
* 2023-01-20 03:10:59 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-20 03:11:00 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-21 03:09:49 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-21 03:09:49 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-21 03:09:49 (3844) [INFO] 
* 2023-01-21 03:09:49 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-21 03:09:49 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-21 03:09:49 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-21 03:09:49 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-21 03:09:49 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-21 03:09:50 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-21 03:09:50 (3874) [INFO] 
* 2023-01-21 03:09:50 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-21 03:09:50 (3844) [INFO] 
* 2023-01-21 03:10:06 (3858) [INFO] 
* 2023-01-21 03:10:06 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-21 03:10:06 (3874) [INFO] 
* 2023-01-21 03:10:06 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-21 03:10:06 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-21 03:10:06 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-21 03:10:06 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FWZLYSdWYL/ea_profile.json
* 2023-01-21 03:10:08 (1664) [INFO] Backed up EA4 profile to /tmp/FWZLYSdWYL/ea_profile.json
* 2023-01-21 03:10:08 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-21 03:10:08 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-22 03:10:44 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-22 03:10:44 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-22 03:10:44 (3844) [INFO] 
* 2023-01-22 03:10:44 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-22 03:10:44 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-22 03:10:44 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-22 03:10:44 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-22 03:10:44 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-22 03:10:44 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-22 03:10:44 (3874) [INFO] 
* 2023-01-22 03:10:44 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-22 03:10:44 (3844) [INFO] 
* 2023-01-22 03:10:56 (3858) [INFO] 
* 2023-01-22 03:10:56 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-22 03:10:56 (3874) [INFO] 
* 2023-01-22 03:10:56 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-22 03:10:56 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-22 03:10:56 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-22 03:10:56 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wm2eVPTu_n/ea_profile.json
* 2023-01-22 03:10:57 (1664) [INFO] Backed up EA4 profile to /tmp/wm2eVPTu_n/ea_profile.json
* 2023-01-22 03:10:57 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-22 03:10:57 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-23 03:09:45 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-01-23 03:09:45 (3538) [ERROR] http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/fece8bae7e9c9b9c299411573b51dc0f42eb237b4d117fd19f7dac914ffb1b47-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/6ef195124b4916bddd2b902a53bab8abbaeaceb0137563817279b7cf9fbc0007-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/387f86a3b023ca98e73214d9876cb5695916d1f6cb699196dd0ef86d8bdbd8bf-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/c7aef26440400841d70a28d39ecc304416a22a4b86330b2192dfcc0f7e272373-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/0707f359719dff892a3166fe4990f5c7e641f02d46ef1ce74049259fc52042a2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.softaculous.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.softaculous.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://linux.darkpenguin.net/distros/CentOS/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/4679d0dbfe073cbbfdb2475610c0718f361697c45a9009ea30f6eb6111bff622-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

base: Check uncompressed DB failed
* 2023-01-23 03:09:45 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-23 03:09:46 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-23 03:09:46 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-23 03:09:46 (3844) [INFO] 
* 2023-01-23 03:09:46 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-23 03:09:46 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-23 03:09:46 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-23 03:09:46 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-23 03:09:46 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-23 03:09:47 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-23 03:09:47 (3874) [INFO] 
* 2023-01-23 03:09:47 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-23 03:09:47 (3844) [INFO] 
* 2023-01-23 03:10:04 (3858) [INFO] 
* 2023-01-23 03:10:04 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-23 03:10:04 (3874) [INFO] 
* 2023-01-23 03:10:04 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-23 03:10:04 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-23 03:10:04 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-23 03:10:04 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lV99zUoCMS/ea_profile.json
* 2023-01-23 03:10:05 (1664) [INFO] Backed up EA4 profile to /tmp/lV99zUoCMS/ea_profile.json
* 2023-01-23 03:10:05 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-23 03:10:06 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-24 03:10:22 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-24 03:10:22 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-24 03:10:22 (3844) [INFO] 
* 2023-01-24 03:10:22 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-24 03:10:23 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-24 03:10:23 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-24 03:10:23 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-24 03:10:23 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-24 03:10:23 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-24 03:10:23 (3874) [INFO] 
* 2023-01-24 03:10:23 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-24 03:10:23 (3844) [INFO] 
* 2023-01-24 03:10:39 (3858) [INFO] 
* 2023-01-24 03:10:39 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-24 03:10:39 (3874) [INFO] 
* 2023-01-24 03:10:39 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-24 03:10:39 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-24 03:10:39 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-24 03:10:39 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eXzeMsIzhO/ea_profile.json
* 2023-01-24 03:10:40 (1664) [INFO] Backed up EA4 profile to /tmp/eXzeMsIzhO/ea_profile.json
* 2023-01-24 03:10:40 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-24 03:10:41 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-25 03:11:09 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-25 03:11:09 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-25 03:11:09 (3844) [INFO] 
* 2023-01-25 03:11:09 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-25 03:11:09 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-25 03:11:09 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-25 03:11:09 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-25 03:11:09 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-25 03:11:09 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-25 03:11:09 (3874) [INFO] 
* 2023-01-25 03:11:09 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-25 03:11:09 (3844) [INFO] 
* 2023-01-25 03:11:27 (3858) [INFO] 
* 2023-01-25 03:11:27 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-25 03:11:27 (3874) [INFO] 
* 2023-01-25 03:11:27 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-25 03:11:27 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-25 03:11:27 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-25 03:11:27 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zn38VZ5S_y/ea_profile.json
* 2023-01-25 03:11:28 (1664) [INFO] Backed up EA4 profile to /tmp/zn38VZ5S_y/ea_profile.json
* 2023-01-25 03:11:28 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-25 03:11:29 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-26 03:11:51 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-01-26 03:11:51 (3538) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 4893.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  31 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:07 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  31 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:09 ago
    State  : Sleeping, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  31 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:12 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:14 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:16 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:18 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:20 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:22 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:24 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:26 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:28 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:30 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  36 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:32 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  64 M RSS (3.3 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:34 ago
    State  : Running, pid: 4893
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  72 M RSS (3.4 GB VSZ)
    Started: Thu Jan 26 03:10:28 2023 - 00:36 ago
    State  : Running, pid: 4893
* 2023-01-26 03:11:51 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-26 03:11:53 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-26 03:11:53 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-26 03:11:53 (3844) [INFO] 
* 2023-01-26 03:11:53 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-26 03:11:54 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-26 03:11:54 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-26 03:11:54 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-26 03:11:54 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-26 03:11:54 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-26 03:11:54 (3874) [INFO] 
* 2023-01-26 03:11:54 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-26 03:11:54 (3844) [INFO] 
* 2023-01-26 03:12:14 (3858) [INFO] 
* 2023-01-26 03:12:14 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-26 03:12:14 (3874) [INFO] 
* 2023-01-26 03:12:14 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-26 03:12:14 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-26 03:12:14 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-26 03:12:14 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SktG9ji0X7/ea_profile.json
* 2023-01-26 03:12:15 (1664) [INFO] Backed up EA4 profile to /tmp/SktG9ji0X7/ea_profile.json
* 2023-01-26 03:12:16 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-26 03:12:16 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-27 03:10:11 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-27 03:10:11 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-27 03:10:11 (3844) [INFO] 
* 2023-01-27 03:10:11 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-27 03:10:11 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-27 03:10:11 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-27 03:10:11 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-27 03:10:11 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-27 03:10:12 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-27 03:10:12 (3874) [INFO] 
* 2023-01-27 03:10:12 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-27 03:10:12 (3844) [INFO] 
* 2023-01-27 03:10:31 (3858) [INFO] 
* 2023-01-27 03:10:31 (3858) [INFO] kernel.x86_64                    3.10.0-1160.81.1.el7                    updates
* 2023-01-27 03:10:31 (3874) [INFO] 
* 2023-01-27 03:10:31 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-27 03:10:31 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-27 03:10:31 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-27 03:10:31 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9MHQLCCG5i/ea_profile.json
* 2023-01-27 03:10:33 (1664) [INFO] Backed up EA4 profile to /tmp/9MHQLCCG5i/ea_profile.json
* 2023-01-27 03:10:33 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-27 03:10:33 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-28 03:11:24 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-28 03:11:24 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-28 03:11:24 (3844) [INFO] 
* 2023-01-28 03:11:24 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-28 03:11:24 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-28 03:11:24 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-28 03:11:24 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-28 03:11:24 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-28 03:11:24 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-28 03:11:24 (3874) [INFO] 
* 2023-01-28 03:11:24 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-28 03:11:24 (3844) [INFO] 
* 2023-01-28 03:11:39 (3858) [INFO] 
* 2023-01-28 03:11:39 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-28 03:11:39 (3874) [INFO] 
* 2023-01-28 03:11:39 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-28 03:11:39 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-28 03:11:39 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-28 03:11:39 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rG5P2SdqQr/ea_profile.json
* 2023-01-28 03:11:40 (1664) [INFO] Backed up EA4 profile to /tmp/rG5P2SdqQr/ea_profile.json
* 2023-01-28 03:11:40 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-28 03:11:40 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-29 03:11:53 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-29 03:11:53 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-29 03:11:53 (3844) [INFO] 
* 2023-01-29 03:11:53 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-29 03:11:54 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-29 03:11:54 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-29 03:11:54 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-29 03:11:54 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-29 03:11:54 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-29 03:11:54 (3874) [INFO] 
* 2023-01-29 03:11:54 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-29 03:11:54 (3844) [INFO] 
* 2023-01-29 03:12:18 (3858) [INFO] 
* 2023-01-29 03:12:18 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-29 03:12:18 (3874) [INFO] 
* 2023-01-29 03:12:18 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-29 03:12:18 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-29 03:12:19 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-29 03:12:19 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2ZZh72LPdb/ea_profile.json
* 2023-01-29 03:12:20 (1664) [INFO] Backed up EA4 profile to /tmp/2ZZh72LPdb/ea_profile.json
* 2023-01-29 03:12:20 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-29 03:12:21 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-30 03:10:06 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-30 03:10:06 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-30 03:10:06 (3844) [INFO] 
* 2023-01-30 03:10:07 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-30 03:10:07 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-30 03:10:07 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-30 03:10:07 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-30 03:10:07 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-30 03:10:08 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-30 03:10:08 (3874) [INFO] 
* 2023-01-30 03:10:08 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-30 03:10:08 (3844) [INFO] 
* 2023-01-30 03:10:27 (3858) [INFO] 
* 2023-01-30 03:10:27 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-30 03:10:27 (3874) [INFO] 
* 2023-01-30 03:10:27 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-30 03:10:27 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-30 03:10:27 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-30 03:10:27 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tabWPLYude/ea_profile.json
* 2023-01-30 03:10:29 (1664) [INFO] Backed up EA4 profile to /tmp/tabWPLYude/ea_profile.json
* 2023-01-30 03:10:29 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-30 03:10:29 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-01-31 03:09:39 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-01-31 03:09:39 (3538) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/6dbf97bb74a628a7be064ba28d8e84c463938a526328a3fcc4a951bdf728848d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/0707f359719dff892a3166fe4990f5c7e641f02d46ef1ce74049259fc52042a2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.imt-systems.com/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/63df43ab49ba655c87dd0ee922c8381202d1824907f60340c3c77d2bf2bfaabb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-01-31 03:09:39 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-01-31 03:09:39 (3370) [INFO] Checking if your system is up to date: 
* 2023-01-31 03:09:39 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-01-31 03:09:39 (3844) [INFO] 
* 2023-01-31 03:09:40 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-01-31 03:09:40 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-01-31 03:09:40 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-01-31 03:09:40 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-01-31 03:09:40 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-01-31 03:09:40 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-01-31 03:09:40 (3874) [INFO] 
* 2023-01-31 03:09:40 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-01-31 03:09:40 (3844) [INFO] 
* 2023-01-31 03:09:55 (3858) [INFO] 
* 2023-01-31 03:09:55 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-01-31 03:09:55 (3874) [INFO] 
* 2023-01-31 03:09:55 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-01-31 03:09:55 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-01-31 03:09:55 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-01-31 03:09:55 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/16OCjYOUDr/ea_profile.json
* 2023-01-31 03:09:56 (1664) [INFO] Backed up EA4 profile to /tmp/16OCjYOUDr/ea_profile.json
* 2023-01-31 03:09:57 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-01-31 03:09:57 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-01 03:10:31 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-01 03:10:31 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-01 03:10:31 (3844) [INFO] 
* 2023-02-01 03:10:31 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-01 03:10:31 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-01 03:10:31 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-01 03:10:31 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-01 03:10:31 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-01 03:10:32 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-01 03:10:32 (3874) [INFO] 
* 2023-02-01 03:10:32 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-01 03:10:32 (3844) [INFO] 
* 2023-02-01 03:10:57 (3858) [INFO] 
* 2023-02-01 03:10:57 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-01 03:10:57 (3874) [INFO] 
* 2023-02-01 03:10:57 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-01 03:10:58 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-01 03:10:58 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-01 03:10:58 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QSbJ7_NHvM/ea_profile.json
* 2023-02-01 03:11:00 (1664) [INFO] Backed up EA4 profile to /tmp/QSbJ7_NHvM/ea_profile.json
* 2023-02-01 03:11:00 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-01 03:11:00 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-02 03:12:44 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-02 03:12:44 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-02 03:12:44 (3844) [INFO] 
* 2023-02-02 03:12:44 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-02 03:12:45 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-02 03:12:45 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-02 03:12:45 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-02 03:12:45 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-02 03:12:45 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-02 03:12:45 (3874) [INFO] 
* 2023-02-02 03:12:45 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-02 03:12:45 (3844) [INFO] 
* 2023-02-02 03:13:02 (3858) [INFO] 
* 2023-02-02 03:13:02 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-02 03:13:02 (3874) [INFO] 
* 2023-02-02 03:13:02 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-02 03:13:02 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-02 03:13:02 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-02 03:13:02 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qmZY1pw6Aa/ea_profile.json
* 2023-02-02 03:13:04 (1664) [INFO] Backed up EA4 profile to /tmp/qmZY1pw6Aa/ea_profile.json
* 2023-02-02 03:13:04 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-02 03:13:05 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-03 03:11:07 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-03 03:11:07 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-03 03:11:07 (3844) [INFO] 
* 2023-02-03 03:11:08 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-03 03:11:08 (3858) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 24138.
* 2023-02-03 03:11:08 (3858) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-02-03 03:11:08 (3858) [INFO]   The other application is: yum
* 2023-02-03 03:11:08 (3858) [INFO]     Memory :  68 M RSS (405 MB VSZ)
* 2023-02-03 03:11:08 (3858) [INFO]     Started: Fri Feb  3 03:10:01 2023 - 01:07 ago
* 2023-02-03 03:11:08 (3858) [INFO]     State  : Running, pid: 24138
* 2023-02-03 03:11:10 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-03 03:11:10 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-03 03:11:10 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-03 03:11:10 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-03 03:11:10 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-03 03:11:11 (3874) [INFO] 
* 2023-02-03 03:11:11 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-03 03:11:11 (3844) [INFO] 
* 2023-02-03 03:11:29 (3858) [INFO] 
* 2023-02-03 03:11:29 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-03 03:11:29 (3874) [INFO] 
* 2023-02-03 03:11:29 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-03 03:11:29 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-03 03:11:29 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-03 03:11:29 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ldOtAjJuZg/ea_profile.json
* 2023-02-03 03:11:30 (1664) [INFO] Backed up EA4 profile to /tmp/ldOtAjJuZg/ea_profile.json
* 2023-02-03 03:11:30 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-03 03:11:31 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-04 03:12:21 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-04 03:12:21 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-04 03:12:21 (3844) [INFO] 
* 2023-02-04 03:12:22 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-04 03:12:22 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-04 03:12:22 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-04 03:12:22 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-04 03:12:22 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-04 03:12:23 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-04 03:12:23 (3874) [INFO] 
* 2023-02-04 03:12:23 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-04 03:12:23 (3844) [INFO] 
* 2023-02-04 03:12:43 (3858) [INFO] 
* 2023-02-04 03:12:43 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-04 03:12:43 (3874) [INFO] 
* 2023-02-04 03:12:43 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-04 03:12:43 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-04 03:12:43 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-04 03:12:43 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OKDRFRPD0b/ea_profile.json
* 2023-02-04 03:12:44 (1664) [INFO] Backed up EA4 profile to /tmp/OKDRFRPD0b/ea_profile.json
* 2023-02-04 03:12:45 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-04 03:12:45 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-05 03:13:35 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-05 03:13:35 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-05 03:13:35 (3844) [INFO] 
* 2023-02-05 03:13:36 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-05 03:13:36 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-05 03:13:36 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-05 03:13:36 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-05 03:13:36 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-05 03:13:37 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-05 03:13:37 (3874) [INFO] 
* 2023-02-05 03:13:37 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-05 03:13:37 (3844) [INFO] 
* 2023-02-05 03:14:01 (3858) [INFO] 
* 2023-02-05 03:14:01 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-05 03:14:01 (3874) [INFO] 
* 2023-02-05 03:14:01 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-05 03:14:01 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-05 03:14:01 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-05 03:14:01 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GqMvOrDOl7/ea_profile.json
* 2023-02-05 03:14:03 (1664) [INFO] Backed up EA4 profile to /tmp/GqMvOrDOl7/ea_profile.json
* 2023-02-05 03:14:03 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-05 03:14:04 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-06 03:09:58 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-06 03:09:58 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-06 03:09:58 (3844) [INFO] 
* 2023-02-06 03:09:58 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-06 03:09:58 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-06 03:09:58 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-06 03:09:58 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-06 03:09:58 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-06 03:09:58 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-06 03:09:58 (3874) [INFO] 
* 2023-02-06 03:09:58 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-06 03:09:58 (3844) [INFO] 
* 2023-02-06 03:10:17 (3858) [INFO] 
* 2023-02-06 03:10:17 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-06 03:10:17 (3874) [INFO] 
* 2023-02-06 03:10:17 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-06 03:10:17 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-06 03:10:17 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-06 03:10:17 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rAzpcv_j46/ea_profile.json
* 2023-02-06 03:10:19 (1664) [INFO] Backed up EA4 profile to /tmp/rAzpcv_j46/ea_profile.json
* 2023-02-06 03:10:19 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-06 03:10:20 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-07 03:12:32 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-07 03:12:32 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-07 03:12:32 (3844) [INFO] 
* 2023-02-07 03:12:33 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-07 03:12:33 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-07 03:12:33 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-07 03:12:33 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-07 03:12:33 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-07 03:12:33 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-07 03:12:33 (3874) [INFO] 
* 2023-02-07 03:12:33 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-07 03:12:33 (3844) [INFO] 
* 2023-02-07 03:12:54 (3858) [INFO] 
* 2023-02-07 03:12:54 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-07 03:12:54 (3874) [INFO] 
* 2023-02-07 03:12:54 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-07 03:12:54 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-07 03:12:54 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-07 03:12:54 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2s0U2VPysi/ea_profile.json
* 2023-02-07 03:12:56 (1664) [INFO] Backed up EA4 profile to /tmp/2s0U2VPysi/ea_profile.json
* 2023-02-07 03:12:57 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-07 03:12:57 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-08 03:10:06 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-08 03:10:06 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-08 03:10:06 (3844) [INFO] 
* 2023-02-08 03:10:07 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-08 03:10:07 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-08 03:10:07 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-08 03:10:07 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-08 03:10:07 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-08 03:10:07 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-08 03:10:07 (3874) [INFO] 
* 2023-02-08 03:10:07 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-08 03:10:07 (3844) [INFO] 
* 2023-02-08 03:10:26 (3858) [INFO] 
* 2023-02-08 03:10:26 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-08 03:10:27 (3874) [INFO] 
* 2023-02-08 03:10:27 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-08 03:10:27 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-08 03:10:27 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-08 03:10:27 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Cbl7KZ2Hus/ea_profile.json
* 2023-02-08 03:10:28 (1664) [INFO] Backed up EA4 profile to /tmp/Cbl7KZ2Hus/ea_profile.json
* 2023-02-08 03:10:28 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-08 03:10:29 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-09 03:10:48 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-09 03:10:48 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-09 03:10:48 (3844) [INFO] 
* 2023-02-09 03:10:48 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-09 03:10:48 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-09 03:10:48 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-09 03:10:48 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-09 03:10:48 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-09 03:10:48 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-09 03:10:48 (3874) [INFO] 
* 2023-02-09 03:10:48 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-09 03:10:48 (3844) [INFO] 
* 2023-02-09 03:11:05 (3858) [INFO] 
* 2023-02-09 03:11:05 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-09 03:11:05 (3874) [INFO] 
* 2023-02-09 03:11:05 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-09 03:11:05 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-09 03:11:05 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-09 03:11:05 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X2qTV3QDjW/ea_profile.json
* 2023-02-09 03:11:06 (1664) [INFO] Backed up EA4 profile to /tmp/X2qTV3QDjW/ea_profile.json
* 2023-02-09 03:11:06 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-09 03:11:07 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-10 03:11:09 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-10 03:11:09 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-10 03:11:09 (3844) [INFO] 
* 2023-02-10 03:11:09 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-10 03:11:09 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-10 03:11:09 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-10 03:11:09 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-10 03:11:09 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-10 03:11:11 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-10 03:11:11 (3874) [INFO] 
* 2023-02-10 03:11:11 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-10 03:11:11 (3844) [INFO] 
* 2023-02-10 03:11:25 (3858) [INFO] 
* 2023-02-10 03:11:25 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-10 03:11:25 (3874) [INFO] 
* 2023-02-10 03:11:25 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-10 03:11:25 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-10 03:11:25 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-10 03:11:25 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zkMrAbF1X1/ea_profile.json
* 2023-02-10 03:11:26 (1664) [INFO] Backed up EA4 profile to /tmp/zkMrAbF1X1/ea_profile.json
* 2023-02-10 03:11:26 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-10 03:11:26 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-11 03:11:12 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-11 03:11:12 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-11 03:11:12 (3844) [INFO] 
* 2023-02-11 03:11:13 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-11 03:11:13 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-11 03:11:13 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-11 03:11:13 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-11 03:11:13 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-11 03:11:13 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-11 03:11:13 (3874) [INFO] 
* 2023-02-11 03:11:13 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-11 03:11:13 (3844) [INFO] 
* 2023-02-11 03:11:27 (3858) [INFO] 
* 2023-02-11 03:11:27 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-11 03:11:27 (3874) [INFO] 
* 2023-02-11 03:11:27 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-11 03:11:27 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-11 03:11:27 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-11 03:11:27 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RtGqBhLzM8/ea_profile.json
* 2023-02-11 03:11:28 (1664) [INFO] Backed up EA4 profile to /tmp/RtGqBhLzM8/ea_profile.json
* 2023-02-11 03:11:28 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-11 03:11:28 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-12 03:12:08 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-12 03:12:08 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-12 03:12:08 (3844) [INFO] 
* 2023-02-12 03:12:08 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-12 03:12:09 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-12 03:12:09 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-12 03:12:09 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-12 03:12:09 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-12 03:12:09 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-12 03:12:09 (3874) [INFO] 
* 2023-02-12 03:12:09 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-12 03:12:09 (3844) [INFO] 
* 2023-02-12 03:12:25 (3858) [INFO] 
* 2023-02-12 03:12:25 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-12 03:12:25 (3874) [INFO] 
* 2023-02-12 03:12:25 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-12 03:12:25 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-12 03:12:25 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-12 03:12:25 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TouvOtHpI9/ea_profile.json
* 2023-02-12 03:12:26 (1664) [INFO] Backed up EA4 profile to /tmp/TouvOtHpI9/ea_profile.json
* 2023-02-12 03:12:26 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-12 03:12:27 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-13 03:10:16 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-13 03:10:16 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-13 03:10:16 (3844) [INFO] 
* 2023-02-13 03:10:16 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-13 03:10:17 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-13 03:10:17 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-13 03:10:17 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-13 03:10:17 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-13 03:10:17 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-13 03:10:17 (3874) [INFO] 
* 2023-02-13 03:10:17 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-13 03:10:17 (3844) [INFO] 
* 2023-02-13 03:10:46 (3858) [INFO] 
* 2023-02-13 03:10:46 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-13 03:10:46 (3874) [INFO] 
* 2023-02-13 03:10:46 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-13 03:10:46 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-13 03:10:47 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-13 03:10:47 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RLSKVgqUcZ/ea_profile.json
* 2023-02-13 03:10:48 (1664) [INFO] Backed up EA4 profile to /tmp/RLSKVgqUcZ/ea_profile.json
* 2023-02-13 03:10:49 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-13 03:10:49 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-14 03:09:54 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-14 03:09:54 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-14 03:09:54 (3844) [INFO] 
* 2023-02-14 03:09:55 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-14 03:09:55 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-14 03:09:55 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-14 03:09:55 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-14 03:09:55 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-14 03:09:55 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-14 03:09:55 (3874) [INFO] 
* 2023-02-14 03:09:55 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-14 03:09:55 (3844) [INFO] 
* 2023-02-14 03:10:12 (3858) [INFO] 
* 2023-02-14 03:10:12 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-14 03:10:12 (3874) [INFO] 
* 2023-02-14 03:10:12 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-14 03:10:12 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-14 03:10:12 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-14 03:10:12 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jd5rJ7hxj2/ea_profile.json
* 2023-02-14 03:10:13 (1664) [INFO] Backed up EA4 profile to /tmp/jd5rJ7hxj2/ea_profile.json
* 2023-02-14 03:10:13 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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.

* 2023-02-14 03:10:14 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-15 03:11:56 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-15 03:11:56 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-15 03:11:56 (3844) [INFO] 
* 2023-02-15 03:11:57 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-15 03:11:57 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-15 03:11:57 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-15 03:11:57 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-15 03:11:57 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-15 03:11:57 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-15 03:11:57 (3874) [INFO] 
* 2023-02-15 03:11:57 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-15 03:11:57 (3844) [INFO] 
* 2023-02-15 03:12:31 (3858) [INFO] 
* 2023-02-15 03:12:31 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-15 03:12:31 (3874) [INFO] 
* 2023-02-15 03:12:31 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-15 03:12:31 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-15 03:12:31 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-15 03:12:31 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SvhJTvx0TH/ea_profile.json
* 2023-02-15 03:12:33 (1664) [INFO] Backed up EA4 profile to /tmp/SvhJTvx0TH/ea_profile.json
* 2023-02-15 03:12:33 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:12:34 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-16 03:09:46 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-02-16 03:09:46 (3538) [ERROR] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.1.2/wp-toolkit/repodata/89f2f2134e0ce542d3adba54ecda0a3b3d12e4b74b97f7d1aa5facfc4ce71020-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.1.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

wp-toolkit-cpanel: Check uncompressed DB failed
* 2023-02-16 03:09:46 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-02-16 03:09:46 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-16 03:09:46 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-16 03:09:46 (3844) [INFO] 
* 2023-02-16 03:09:47 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-16 03:09:47 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-16 03:09:47 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-16 03:09:47 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-16 03:09:47 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-16 03:09:48 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-16 03:09:48 (3874) [INFO] 
* 2023-02-16 03:09:48 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-16 03:09:48 (3844) [INFO] 
* 2023-02-16 03:10:06 (3858) [INFO] 
* 2023-02-16 03:10:06 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-16 03:10:06 (3874) [INFO] 
* 2023-02-16 03:10:06 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-16 03:10:06 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-16 03:10:06 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-16 03:10:06 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/elc_7pI1nG/ea_profile.json
* 2023-02-16 03:10:08 (1664) [INFO] Backed up EA4 profile to /tmp/elc_7pI1nG/ea_profile.json
* 2023-02-16 03:10:09 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:10:09 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-17 03:11:33 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-17 03:11:33 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-17 03:11:33 (3844) [INFO] 
* 2023-02-17 03:11:33 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-17 03:11:33 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-17 03:11:33 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-17 03:11:33 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-17 03:11:33 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-17 03:11:33 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-17 03:11:33 (3874) [INFO] 
* 2023-02-17 03:11:33 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-17 03:11:33 (3844) [INFO] 
* 2023-02-17 03:11:49 (3858) [INFO] 
* 2023-02-17 03:11:49 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-17 03:11:49 (3874) [INFO] 
* 2023-02-17 03:11:49 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-17 03:11:49 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-17 03:11:49 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-17 03:11:49 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q389kU2mzk/ea_profile.json
* 2023-02-17 03:11:50 (1664) [INFO] Backed up EA4 profile to /tmp/q389kU2mzk/ea_profile.json
* 2023-02-17 03:11:50 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:11:51 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-18 03:10:59 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-18 03:10:59 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-18 03:10:59 (3844) [INFO] 
* 2023-02-18 03:10:59 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-18 03:10:59 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-18 03:10:59 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-18 03:10:59 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-18 03:10:59 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-18 03:10:59 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-18 03:10:59 (3874) [INFO] 
* 2023-02-18 03:10:59 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-18 03:10:59 (3844) [INFO] 
* 2023-02-18 03:11:13 (3858) [INFO] 
* 2023-02-18 03:11:13 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-18 03:11:13 (3874) [INFO] 
* 2023-02-18 03:11:13 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-18 03:11:13 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-18 03:11:13 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-18 03:11:13 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lCF7Wn0_zr/ea_profile.json
* 2023-02-18 03:11:15 (1664) [INFO] Backed up EA4 profile to /tmp/lCF7Wn0_zr/ea_profile.json
* 2023-02-18 03:11:15 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:11:15 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-19 03:11:33 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-19 03:11:33 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-19 03:11:33 (3844) [INFO] 
* 2023-02-19 03:11:33 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-19 03:11:33 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-19 03:11:33 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-19 03:11:33 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-19 03:11:33 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-19 03:11:33 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-19 03:11:33 (3874) [INFO] 
* 2023-02-19 03:11:33 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-19 03:11:33 (3844) [INFO] 
* 2023-02-19 03:11:50 (3858) [INFO] 
* 2023-02-19 03:11:50 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-19 03:11:50 (3874) [INFO] 
* 2023-02-19 03:11:50 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-19 03:11:50 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-19 03:11:50 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-19 03:11:50 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V5kDpS0YTZ/ea_profile.json
* 2023-02-19 03:11:52 (1664) [INFO] Backed up EA4 profile to /tmp/V5kDpS0YTZ/ea_profile.json
* 2023-02-19 03:11:53 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:11:53 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-20 03:09:58 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-20 03:09:58 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-20 03:09:58 (3844) [INFO] 
* 2023-02-20 03:09:59 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-20 03:09:59 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-20 03:09:59 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-20 03:09:59 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-20 03:09:59 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-20 03:09:59 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-20 03:09:59 (3874) [INFO] 
* 2023-02-20 03:09:59 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-20 03:09:59 (3844) [INFO] 
* 2023-02-20 03:10:23 (3858) [INFO] 
* 2023-02-20 03:10:23 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-20 03:10:23 (3874) [INFO] 
* 2023-02-20 03:10:23 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-20 03:10:23 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-20 03:10:24 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-20 03:10:24 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oEaelhrpRS/ea_profile.json
* 2023-02-20 03:10:25 (1664) [INFO] Backed up EA4 profile to /tmp/oEaelhrpRS/ea_profile.json
* 2023-02-20 03:10:26 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:10:26 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-21 03:10:59 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-21 03:10:59 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-21 03:10:59 (3844) [INFO] 
* 2023-02-21 03:11:00 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-21 03:11:00 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-21 03:11:00 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-21 03:11:00 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-21 03:11:00 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-21 03:11:00 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-21 03:11:00 (3874) [INFO] 
* 2023-02-21 03:11:00 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-21 03:11:00 (3844) [INFO] 
* 2023-02-21 03:11:20 (3858) [INFO] 
* 2023-02-21 03:11:20 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-21 03:11:20 (3874) [INFO] 
* 2023-02-21 03:11:20 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-21 03:11:20 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-21 03:11:20 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-21 03:11:20 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Vtsk1Br_jb/ea_profile.json
* 2023-02-21 03:11:21 (1664) [INFO] Backed up EA4 profile to /tmp/Vtsk1Br_jb/ea_profile.json
* 2023-02-21 03:11:21 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:11:21 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-22 03:09:55 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-22 03:09:55 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-22 03:09:55 (3844) [INFO] 
* 2023-02-22 03:09:56 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-22 03:09:56 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-22 03:09:56 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-22 03:09:56 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-22 03:09:56 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-22 03:09:56 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-22 03:09:56 (3874) [INFO] 
* 2023-02-22 03:09:56 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-22 03:09:56 (3844) [INFO] 
* 2023-02-22 03:10:18 (3858) [INFO] 
* 2023-02-22 03:10:18 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-22 03:10:18 (3874) [INFO] 
* 2023-02-22 03:10:18 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-22 03:10:18 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-22 03:10:18 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-22 03:10:18 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FzLBUmD5nM/ea_profile.json
* 2023-02-22 03:10:19 (1664) [INFO] Backed up EA4 profile to /tmp/FzLBUmD5nM/ea_profile.json
* 2023-02-22 03:10:19 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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 03:10:20 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-23 03:10:57 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-23 03:10:57 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-23 03:10:57 (3844) [INFO] 
* 2023-02-23 03:10:57 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-23 03:10:58 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-23 03:10:58 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-23 03:10:58 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-23 03:10:58 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-23 03:10:58 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-23 03:10:58 (3874) [INFO] 
* 2023-02-23 03:10:58 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-23 03:10:58 (3844) [INFO] 
* 2023-02-23 03:11:15 (3858) [INFO] 
* 2023-02-23 03:11:15 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-23 03:11:15 (3874) [INFO] 
* 2023-02-23 03:11:15 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-23 03:11:15 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-23 03:11:15 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-23 03:11:15 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6d8R6s9OO6/ea_profile.json
* 2023-02-23 03:11:16 (1664) [INFO] Backed up EA4 profile to /tmp/6d8R6s9OO6/ea_profile.json
* 2023-02-23 03:11:16 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-23 03:11:16 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-24 03:11:12 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-24 03:11:12 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-24 03:11:12 (3844) [INFO] 
* 2023-02-24 03:11:12 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-24 03:11:13 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-24 03:11:13 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-24 03:11:13 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-24 03:11:13 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-24 03:11:13 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-24 03:11:13 (3874) [INFO] 
* 2023-02-24 03:11:13 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-24 03:11:13 (3844) [INFO] 
* 2023-02-24 03:11:32 (3858) [INFO] 
* 2023-02-24 03:11:32 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-24 03:11:32 (3874) [INFO] 
* 2023-02-24 03:11:32 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-24 03:11:32 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-24 03:11:32 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-24 03:11:32 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4N0hBWMf37/ea_profile.json
* 2023-02-24 03:11:33 (1664) [INFO] Backed up EA4 profile to /tmp/4N0hBWMf37/ea_profile.json
* 2023-02-24 03:11:33 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-24 03:11:34 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-25 03:13:42 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-25 03:13:42 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-25 03:13:42 (3844) [INFO] 
* 2023-02-25 03:13:42 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-25 03:13:42 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-25 03:13:42 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-25 03:13:42 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-25 03:13:42 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-25 03:13:43 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-25 03:13:43 (3874) [INFO] 
* 2023-02-25 03:13:43 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-25 03:13:43 (3844) [INFO] 
* 2023-02-25 03:13:59 (3858) [INFO] 
* 2023-02-25 03:13:59 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-25 03:13:59 (3874) [INFO] 
* 2023-02-25 03:13:59 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-25 03:13:59 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-25 03:13:59 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-25 03:13:59 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8ywgAWsKO9/ea_profile.json
* 2023-02-25 03:14:00 (1664) [INFO] Backed up EA4 profile to /tmp/8ywgAWsKO9/ea_profile.json
* 2023-02-25 03:14:00 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-25 03:14:00 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-26 03:10:30 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-26 03:10:30 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-26 03:10:30 (3844) [INFO] 
* 2023-02-26 03:10:30 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-26 03:10:30 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-26 03:10:30 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-26 03:10:30 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-26 03:10:30 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-26 03:10:31 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-26 03:10:31 (3874) [INFO] 
* 2023-02-26 03:10:31 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-26 03:10:31 (3844) [INFO] 
* 2023-02-26 03:10:46 (3858) [INFO] 
* 2023-02-26 03:10:46 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-26 03:10:46 (3874) [INFO] 
* 2023-02-26 03:10:46 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-26 03:10:46 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-26 03:10:46 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-26 03:10:46 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8wrXNHTvoj/ea_profile.json
* 2023-02-26 03:10:47 (1664) [INFO] Backed up EA4 profile to /tmp/8wrXNHTvoj/ea_profile.json
* 2023-02-26 03:10:47 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-26 03:10:47 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-27 03:09:45 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-27 03:09:45 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-27 03:09:45 (3844) [INFO] 
* 2023-02-27 03:09:45 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-27 03:09:46 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-27 03:09:46 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-27 03:09:46 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-27 03:09:46 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-27 03:09:46 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-27 03:09:46 (3874) [INFO] 
* 2023-02-27 03:09:46 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-27 03:09:46 (3844) [INFO] 
* 2023-02-27 03:10:03 (3858) [INFO] 
* 2023-02-27 03:10:03 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-27 03:10:03 (3874) [INFO] 
* 2023-02-27 03:10:03 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-27 03:10:03 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-27 03:10:03 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-27 03:10:03 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5k77WdG8E6/ea_profile.json
* 2023-02-27 03:10:04 (1664) [INFO] Backed up EA4 profile to /tmp/5k77WdG8E6/ea_profile.json
* 2023-02-27 03:10:04 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-27 03:10:05 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-02-28 03:10:19 (3370) [INFO] Checking if your system is up to date: 
* 2023-02-28 03:10:19 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-02-28 03:10:19 (3844) [INFO] 
* 2023-02-28 03:10:19 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-02-28 03:10:19 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-02-28 03:10:19 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-02-28 03:10:19 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-02-28 03:10:19 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-02-28 03:10:19 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-02-28 03:10:19 (3874) [INFO] 
* 2023-02-28 03:10:19 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-02-28 03:10:19 (3844) [INFO] 
* 2023-02-28 03:10:34 (3858) [INFO] 
* 2023-02-28 03:10:34 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-02-28 03:10:34 (3874) [INFO] 
* 2023-02-28 03:10:34 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-02-28 03:10:34 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-02-28 03:10:34 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-02-28 03:10:34 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JRrCQzQLc2/ea_profile.json
* 2023-02-28 03:10:35 (1664) [INFO] Backed up EA4 profile to /tmp/JRrCQzQLc2/ea_profile.json
* 2023-02-28 03:10:35 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-28 03:10:36 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-01 03:09:41 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-01 03:09:41 (3538) [ERROR] http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/0707f359719dff892a3166fe4990f5c7e641f02d46ef1ce74049259fc52042a2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://linux.darkpenguin.net/distros/CentOS/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/1faa5eab0438fde01764d4705689a4b118fc011ab5064e30191ac755a86c6028-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-03-01 03:09:41 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-01 03:09:42 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-01 03:09:42 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-01 03:09:42 (3844) [INFO] 
* 2023-03-01 03:09:42 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-01 03:09:42 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-01 03:09:42 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-01 03:09:42 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-01 03:09:42 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-01 03:09:42 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-01 03:09:42 (3874) [INFO] 
* 2023-03-01 03:09:42 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-01 03:09:42 (3844) [INFO] 
* 2023-03-01 03:09:55 (3858) [INFO] 
* 2023-03-01 03:09:55 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-01 03:09:56 (3874) [INFO] 
* 2023-03-01 03:09:56 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-01 03:09:56 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-01 03:09:56 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-01 03:09:56 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MEeVmm3GJb/ea_profile.json
* 2023-03-01 03:09:56 (1664) [INFO] Backed up EA4 profile to /tmp/MEeVmm3GJb/ea_profile.json
* 2023-03-01 03:09:57 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-01 03:09:57 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-02 03:09:45 (3537) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-02 03:09:45 (3538) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-03-02 03:09:45 (2712) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-02 03:09:45 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-02 03:09:45 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-02 03:09:45 (3844) [INFO] 
* 2023-03-02 03:09:45 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-02 03:09:45 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-02 03:09:45 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-02 03:09:45 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-02 03:09:45 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-02 03:09:46 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-02 03:09:46 (3874) [INFO] 
* 2023-03-02 03:09:46 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-02 03:09:46 (3844) [INFO] 
* 2023-03-02 03:09:59 (3858) [INFO] 
* 2023-03-02 03:09:59 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-02 03:09:59 (3874) [INFO] 
* 2023-03-02 03:09:59 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-02 03:09:59 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-02 03:09:59 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-02 03:09:59 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/npj3BuioZJ/ea_profile.json
* 2023-03-02 03:10:00 (1664) [INFO] Backed up EA4 profile to /tmp/npj3BuioZJ/ea_profile.json
* 2023-03-02 03:10:00 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-02 03:10:00 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-03 03:10:21 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-03 03:10:21 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-03 03:10:21 (3844) [INFO] 
* 2023-03-03 03:10:21 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-03 03:10:21 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-03 03:10:21 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-03 03:10:21 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-03 03:10:21 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-03 03:10:21 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-03 03:10:21 (3874) [INFO] 
* 2023-03-03 03:10:21 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-03 03:10:21 (3844) [INFO] 
* 2023-03-03 03:10:38 (3858) [INFO] 
* 2023-03-03 03:10:38 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-03 03:10:38 (3874) [INFO] 
* 2023-03-03 03:10:38 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-03 03:10:38 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-03 03:10:38 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-03 03:10:38 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_42r9DJ9GF/ea_profile.json
* 2023-03-03 03:10:39 (1664) [INFO] Backed up EA4 profile to /tmp/_42r9DJ9GF/ea_profile.json
* 2023-03-03 03:10:39 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-03 03:10:40 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-04 03:09:52 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-04 03:09:52 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-04 03:09:52 (3844) [INFO] 
* 2023-03-04 03:09:53 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-04 03:09:53 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-04 03:09:53 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-04 03:09:53 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-04 03:09:53 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-04 03:09:53 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-04 03:09:53 (3874) [INFO] 
* 2023-03-04 03:09:53 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-04 03:09:53 (3844) [INFO] 
* 2023-03-04 03:10:06 (3858) [INFO] 
* 2023-03-04 03:10:06 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-04 03:10:06 (3874) [INFO] 
* 2023-03-04 03:10:06 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-04 03:10:06 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-04 03:10:06 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-04 03:10:06 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/cNCW5_P0Kc/ea_profile.json
* 2023-03-04 03:10:07 (1664) [INFO] Backed up EA4 profile to /tmp/cNCW5_P0Kc/ea_profile.json
* 2023-03-04 03:10:08 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-04 03:10:09 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-05 03:10:17 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-05 03:10:17 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-05 03:10:17 (3844) [INFO] 
* 2023-03-05 03:10:18 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-05 03:10:18 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-05 03:10:18 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-05 03:10:18 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-05 03:10:18 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-05 03:10:18 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-05 03:10:18 (3874) [INFO] 
* 2023-03-05 03:10:18 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-05 03:10:18 (3844) [INFO] 
* 2023-03-05 03:10:32 (3858) [INFO] 
* 2023-03-05 03:10:32 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-05 03:10:32 (3874) [INFO] 
* 2023-03-05 03:10:32 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-05 03:10:32 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-05 03:10:32 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-05 03:10:32 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/v6_8OiWy6d/ea_profile.json
* 2023-03-05 03:10:33 (1664) [INFO] Backed up EA4 profile to /tmp/v6_8OiWy6d/ea_profile.json
* 2023-03-05 03:10:33 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-05 03:10:33 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-06 03:09:36 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-06 03:09:36 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-06 03:09:36 (3844) [INFO] 
* 2023-03-06 03:09:36 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-06 03:09:36 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-06 03:09:36 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-06 03:09:36 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-06 03:09:36 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-06 03:09:37 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-06 03:09:37 (3874) [INFO] 
* 2023-03-06 03:09:37 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-06 03:09:37 (3844) [INFO] 
* 2023-03-06 03:09:50 (3858) [INFO] 
* 2023-03-06 03:09:50 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-06 03:09:50 (3874) [INFO] 
* 2023-03-06 03:09:50 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-06 03:09:50 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-06 03:09:50 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-06 03:09:50 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6O3qnCt1lr/ea_profile.json
* 2023-03-06 03:09:51 (1664) [INFO] Backed up EA4 profile to /tmp/6O3qnCt1lr/ea_profile.json
* 2023-03-06 03:09:51 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-06 03:09:51 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-07 03:10:17 (3370) [INFO] Checking if your system is up to date: 
* 2023-03-07 03:10:17 (3843) [INFO] Running: /usr/bin/yum clean all
* 2023-03-07 03:10:17 (3844) [INFO] 
* 2023-03-07 03:10:17 (3858) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-07 03:10:17 (3858) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-07 03:10:17 (3858) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-07 03:10:17 (3858) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-07 03:10:17 (3858) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-07 03:10:17 (3858) [INFO] Cleaning up list of fastest mirrors
* 2023-03-07 03:10:18 (3874) [INFO] 
* 2023-03-07 03:10:18 (3843) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-07 03:10:18 (3844) [INFO] 
* 2023-03-07 03:10:37 (3858) [INFO] 
* 2023-03-07 03:10:37 (3858) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-07 03:10:37 (3874) [INFO] 
* 2023-03-07 03:10:37 (3378) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-07 03:10:37 (2712) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-07 03:10:37 (3032) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-07 03:10:37 (1639) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AMavnB8rII/ea_profile.json
* 2023-03-07 03:10:38 (1664) [INFO] Backed up EA4 profile to /tmp/AMavnB8rII/ea_profile.json
* 2023-03-07 03:10:38 (2712) [WARN] *** Elevation Blocker detected: ***
This script (version 3) 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-03-07 03:10:39 (709) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-08 03:14:12 (366) [INFO] Self-update of script version 3 requested.
* 2023-03-08 03:14:12 (371) [INFO] Newer version of script found. Downloading.
* 2023-03-08 03:14:12 (380) [INFO] Script update to version 5 successful.
* 2023-03-08 03:14:23 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-08 03:14:23 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-08 03:14:23 (4079) [INFO] 
* 2023-03-08 03:14:23 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-08 03:14:23 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-08 03:14:23 (4093) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-08 03:14:23 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-08 03:14:23 (4093) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-08 03:14:23 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-08 03:14:23 (4110) [INFO] 
* 2023-03-08 03:14:23 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-08 03:14:23 (4079) [INFO] 
* 2023-03-08 03:14:39 (4093) [INFO] 
* 2023-03-08 03:14:39 (4093) [INFO] kernel.x86_64                    3.10.0-1160.83.1.el7                    updates
* 2023-03-08 03:14:39 (4110) [INFO] 
* 2023-03-08 03:14:39 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-08 03:14:39 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-08 03:14:39 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-08 03:14:39 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Pmt1AqsaYo/ea_profile.json
* 2023-03-08 03:14:40 (1694) [INFO] Backed up EA4 profile to /tmp/Pmt1AqsaYo/ea_profile.json
* 2023-03-08 03:14:41 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-09 03:11:18 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-09 03:11:18 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-09 03:11:18 (4079) [INFO] 
* 2023-03-09 03:11:18 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-09 03:11:18 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-09 03:11:18 (4093) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-09 03:11:18 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-09 03:11:18 (4093) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-09 03:11:18 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-09 03:11:18 (4110) [INFO] 
* 2023-03-09 03:11:18 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-09 03:11:18 (4079) [INFO] 
* 2023-03-09 03:11:33 (4093) [INFO] 
* 2023-03-09 03:11:33 (4093) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-09 03:11:33 (4110) [INFO] 
* 2023-03-09 03:11:33 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-09 03:11:33 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-09 03:11:33 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-09 03:11:33 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bGkf6fVl1i/ea_profile.json
* 2023-03-09 03:11:34 (1694) [INFO] Backed up EA4 profile to /tmp/bGkf6fVl1i/ea_profile.json
* 2023-03-09 03:11:35 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-10 03:09:54 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-10 03:09:54 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-10 03:09:54 (4079) [INFO] 
* 2023-03-10 03:09:55 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-10 03:09:55 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-10 03:09:55 (4093) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-10 03:09:55 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-10 03:09:55 (4093) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-10 03:09:55 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-10 03:09:55 (4110) [INFO] 
* 2023-03-10 03:09:55 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-10 03:09:55 (4079) [INFO] 
* 2023-03-10 03:10:10 (4093) [INFO] 
* 2023-03-10 03:10:10 (4093) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-10 03:10:10 (4110) [INFO] 
* 2023-03-10 03:10:10 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-10 03:10:10 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-10 03:10:10 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-10 03:10:10 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qDxVTuKxmA/ea_profile.json
* 2023-03-10 03:10:11 (1694) [INFO] Backed up EA4 profile to /tmp/qDxVTuKxmA/ea_profile.json
* 2023-03-10 03:10:13 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-11 03:11:07 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-11 03:11:07 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-11 03:11:07 (4079) [INFO] 
* 2023-03-11 03:11:07 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-11 03:11:07 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-11 03:11:07 (4093) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-11 03:11:07 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-11 03:11:07 (4093) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-11 03:11:08 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-11 03:11:08 (4110) [INFO] 
* 2023-03-11 03:11:08 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-11 03:11:08 (4079) [INFO] 
* 2023-03-11 03:11:25 (4093) [INFO] 
* 2023-03-11 03:11:25 (4093) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-11 03:11:26 (4110) [INFO] 
* 2023-03-11 03:11:26 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-11 03:11:26 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-11 03:11:26 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-11 03:11:26 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JwLr707A7m/ea_profile.json
* 2023-03-11 03:11:27 (1694) [INFO] Backed up EA4 profile to /tmp/JwLr707A7m/ea_profile.json
* 2023-03-11 03:11:28 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-12 03:11:18 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-12 03:11:18 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-12 03:11:18 (4079) [INFO] 
* 2023-03-12 03:11:18 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-12 03:11:18 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-12 03:11:18 (4093) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-12 03:11:18 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-12 03:11:18 (4093) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-12 03:11:19 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-12 03:11:19 (4110) [INFO] 
* 2023-03-12 03:11:19 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-12 03:11:19 (4079) [INFO] 
* 2023-03-12 03:11:34 (4093) [INFO] 
* 2023-03-12 03:11:34 (4093) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-12 03:11:34 (4110) [INFO] 
* 2023-03-12 03:11:34 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-12 03:11:34 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-12 03:11:34 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-12 03:11:34 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yc6DebSqiQ/ea_profile.json
* 2023-03-12 03:11:36 (1694) [INFO] Backed up EA4 profile to /tmp/yc6DebSqiQ/ea_profile.json
* 2023-03-12 03:11:37 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-13 03:09:48 (3733) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-13 03:09:48 (3734) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/1eaa6106703d9957043fa3767b474747948570fa899a7c7920354bba44d55c91-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/1eaa6106703d9957043fa3767b474747948570fa899a7c7920354bba44d55c91-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-03-13 03:09:48 (2749) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-13 03:09:49 (3566) [INFO] Checking if your system is up to date: 
* 2023-03-13 03:09:49 (4078) [INFO] Running: /usr/bin/yum clean all
* 2023-03-13 03:09:49 (4079) [INFO] 
* 2023-03-13 03:09:49 (4093) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-13 03:09:49 (4093) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-13 03:09:49 (4093) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-13 03:09:49 (4093) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-13 03:09:49 (4093) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-13 03:09:50 (4093) [INFO] Cleaning up list of fastest mirrors
* 2023-03-13 03:09:50 (4110) [INFO] 
* 2023-03-13 03:09:50 (4078) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-13 03:09:50 (4079) [INFO] 
* 2023-03-13 03:10:04 (4093) [INFO] 
* 2023-03-13 03:10:04 (4093) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-13 03:10:04 (4110) [INFO] 
* 2023-03-13 03:10:04 (3574) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-13 03:10:04 (2749) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-13 03:10:04 (3227) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-13 03:10:04 (1669) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vXaMfYsPZt/ea_profile.json
* 2023-03-13 03:10:05 (1694) [INFO] Backed up EA4 profile to /tmp/vXaMfYsPZt/ea_profile.json
* 2023-03-13 03:10:07 (713) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-14 03:09:36 (368) [INFO] Self-update of script version 5 requested.
* 2023-03-14 03:09:36 (373) [INFO] Newer version of script found. Downloading.
* 2023-03-14 03:09:36 (382) [INFO] Script update to version 6 successful.
* 2023-03-14 03:09:58 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-14 03:09:58 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-14 03:09:58 (4151) [INFO] 
* 2023-03-14 03:09:59 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-14 03:09:59 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-14 03:09:59 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-14 03:09:59 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-14 03:09:59 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-14 03:09:59 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-14 03:09:59 (4182) [INFO] 
* 2023-03-14 03:09:59 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-14 03:09:59 (4151) [INFO] 
* 2023-03-14 03:10:13 (4165) [INFO] 
* 2023-03-14 03:10:13 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-14 03:10:13 (4182) [INFO] 
* 2023-03-14 03:10:13 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-14 03:10:13 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-14 03:10:14 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-14 03:10:14 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EUNNG_Qh2A/ea_profile.json
* 2023-03-14 03:10:14 (1765) [INFO] Backed up EA4 profile to /tmp/EUNNG_Qh2A/ea_profile.json
* 2023-03-14 03:10:16 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-15 03:09:28 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-15 03:09:28 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-15 03:09:28 (4151) [INFO] 
* 2023-03-15 03:09:28 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-15 03:09:28 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-15 03:09:28 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-15 03:09:28 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-15 03:09:28 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-15 03:09:28 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-15 03:09:28 (4182) [INFO] 
* 2023-03-15 03:09:28 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-15 03:09:28 (4151) [INFO] 
* 2023-03-15 03:09:42 (4165) [INFO] 
* 2023-03-15 03:09:42 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-15 03:09:42 (4182) [INFO] 
* 2023-03-15 03:09:42 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-15 03:09:42 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-15 03:09:42 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-15 03:09:42 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DRZ7VBRJRd/ea_profile.json
* 2023-03-15 03:09:43 (1765) [INFO] Backed up EA4 profile to /tmp/DRZ7VBRJRd/ea_profile.json
* 2023-03-15 03:09:43 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-16 03:10:25 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-16 03:10:25 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-16 03:10:25 (4151) [INFO] 
* 2023-03-16 03:10:25 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-16 03:10:25 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-16 03:10:25 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-16 03:10:25 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-16 03:10:25 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-16 03:10:25 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-16 03:10:25 (4182) [INFO] 
* 2023-03-16 03:10:25 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-16 03:10:25 (4151) [INFO] 
* 2023-03-16 03:10:43 (4165) [INFO] 
* 2023-03-16 03:10:43 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-16 03:10:43 (4182) [INFO] 
* 2023-03-16 03:10:43 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-16 03:10:43 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-16 03:10:43 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-16 03:10:43 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lj9ZM1XMzX/ea_profile.json
* 2023-03-16 03:10:44 (1765) [INFO] Backed up EA4 profile to /tmp/lj9ZM1XMzX/ea_profile.json
* 2023-03-16 03:10:45 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-17 03:09:48 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-17 03:09:48 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-17 03:09:48 (4151) [INFO] 
* 2023-03-17 03:09:48 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-17 03:09:48 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-17 03:09:48 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-17 03:09:48 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-17 03:09:48 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-17 03:09:48 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-17 03:09:48 (4182) [INFO] 
* 2023-03-17 03:09:48 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-17 03:09:48 (4151) [INFO] 
* 2023-03-17 03:10:04 (4165) [INFO] 
* 2023-03-17 03:10:04 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-17 03:10:04 (4182) [INFO] 
* 2023-03-17 03:10:04 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-17 03:10:04 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-17 03:10:04 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-17 03:10:04 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JT8NIW4y8o/ea_profile.json
* 2023-03-17 03:10:05 (1765) [INFO] Backed up EA4 profile to /tmp/JT8NIW4y8o/ea_profile.json
* 2023-03-17 03:10:06 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-18 03:13:37 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-18 03:13:37 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-18 03:13:37 (4151) [INFO] 
* 2023-03-18 03:13:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-18 03:13:38 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-18 03:13:38 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-18 03:13:38 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-18 03:13:38 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-18 03:13:39 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-18 03:13:39 (4182) [INFO] 
* 2023-03-18 03:13:39 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-18 03:13:39 (4151) [INFO] 
* 2023-03-18 03:14:50 (4165) [INFO] 
* 2023-03-18 03:14:50 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-18 03:14:50 (4182) [INFO] 
* 2023-03-18 03:14:50 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-18 03:14:50 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-18 03:14:50 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-18 03:14:50 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wIVfGhuj5T/ea_profile.json
* 2023-03-18 03:14:51 (1765) [INFO] Backed up EA4 profile to /tmp/wIVfGhuj5T/ea_profile.json
* 2023-03-18 03:14:54 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-19 03:10:29 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-19 03:10:29 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-19 03:10:29 (4151) [INFO] 
* 2023-03-19 03:10:29 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-19 03:10:29 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-19 03:10:29 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-19 03:10:29 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-19 03:10:29 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-19 03:10:31 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-19 03:10:31 (4182) [INFO] 
* 2023-03-19 03:10:31 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-19 03:10:31 (4151) [INFO] 
* 2023-03-19 03:10:45 (4165) [INFO] 
* 2023-03-19 03:10:45 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-19 03:10:45 (4182) [INFO] 
* 2023-03-19 03:10:45 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-19 03:10:45 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-19 03:10:45 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-19 03:10:45 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Bt2I5XXvm7/ea_profile.json
* 2023-03-19 03:10:46 (1765) [INFO] Backed up EA4 profile to /tmp/Bt2I5XXvm7/ea_profile.json
* 2023-03-19 03:10:47 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-20 03:09:35 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-20 03:09:35 (3806) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f9b2480c2935d1e8d279c69baba33466c72c63deb9e8aec2f8aa4f147559c101-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.1.3/wp-toolkit/repodata/f94ac2de6ad46e32415519b0fc2677cc67636657572cd37263fcfde22917c523-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.1.3/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/bc8950506fb13622afd9eb93c811884b6e2e7570afd5fac946f708ac01ae0cff-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-03-20 03:09:35 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-20 03:09:35 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-20 03:09:35 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-20 03:09:35 (4151) [INFO] 
* 2023-03-20 03:09:35 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-20 03:09:35 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-20 03:09:35 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-20 03:09:35 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-20 03:09:35 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-20 03:09:35 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-20 03:09:35 (4182) [INFO] 
* 2023-03-20 03:09:35 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-20 03:09:35 (4151) [INFO] 
* 2023-03-20 03:09:49 (4165) [INFO] 
* 2023-03-20 03:09:49 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-20 03:09:49 (4182) [INFO] 
* 2023-03-20 03:09:49 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-20 03:09:49 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-20 03:09:49 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-20 03:09:49 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/acc5Sc_rDy/ea_profile.json
* 2023-03-20 03:09:50 (1765) [INFO] Backed up EA4 profile to /tmp/acc5Sc_rDy/ea_profile.json
* 2023-03-20 03:09:52 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-21 03:10:05 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-21 03:10:05 (3806) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-03-21 03:10:05 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-21 03:10:06 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-21 03:10:06 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-21 03:10:06 (4151) [INFO] 
* 2023-03-21 03:10:06 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-21 03:10:06 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-21 03:10:06 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-21 03:10:06 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-21 03:10:06 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-21 03:10:06 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-21 03:10:06 (4182) [INFO] 
* 2023-03-21 03:10:06 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-21 03:10:06 (4151) [INFO] 
* 2023-03-21 03:10:19 (4165) [INFO] 
* 2023-03-21 03:10:19 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-21 03:10:19 (4182) [INFO] 
* 2023-03-21 03:10:19 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-21 03:10:19 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-21 03:10:19 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-21 03:10:19 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/B2gNZUhED8/ea_profile.json
* 2023-03-21 03:10:20 (1765) [INFO] Backed up EA4 profile to /tmp/B2gNZUhED8/ea_profile.json
* 2023-03-21 03:10:22 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-22 03:10:07 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-22 03:10:07 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-22 03:10:07 (4151) [INFO] 
* 2023-03-22 03:10:07 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-22 03:10:08 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-22 03:10:08 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-22 03:10:08 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-22 03:10:08 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-22 03:10:08 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-22 03:10:08 (4182) [INFO] 
* 2023-03-22 03:10:08 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-22 03:10:08 (4151) [INFO] 
* 2023-03-22 03:10:25 (4165) [INFO] 
* 2023-03-22 03:10:25 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-22 03:10:25 (4182) [INFO] 
* 2023-03-22 03:10:25 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-22 03:10:25 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-22 03:10:25 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-22 03:10:25 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V3DSHq0z5J/ea_profile.json
* 2023-03-22 03:10:26 (1765) [INFO] Backed up EA4 profile to /tmp/V3DSHq0z5J/ea_profile.json
* 2023-03-22 03:10:27 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-23 03:10:09 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-23 03:10:09 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-23 03:10:09 (4151) [INFO] 
* 2023-03-23 03:10:09 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-23 03:10:09 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-23 03:10:09 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-23 03:10:09 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-23 03:10:09 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-23 03:10:09 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-23 03:10:09 (4182) [INFO] 
* 2023-03-23 03:10:09 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-23 03:10:09 (4151) [INFO] 
* 2023-03-23 03:10:22 (4165) [INFO] 
* 2023-03-23 03:10:22 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-23 03:10:22 (4182) [INFO] 
* 2023-03-23 03:10:22 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-23 03:10:22 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-23 03:10:23 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-23 03:10:23 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L5NCokYfZi/ea_profile.json
* 2023-03-23 03:10:23 (1765) [INFO] Backed up EA4 profile to /tmp/L5NCokYfZi/ea_profile.json
* 2023-03-23 03:10:24 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-24 03:10:43 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-24 03:10:43 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-24 03:10:43 (4151) [INFO] 
* 2023-03-24 03:10:43 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-24 03:10:43 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-24 03:10:43 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-24 03:10:43 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-24 03:10:43 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-24 03:10:43 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-24 03:10:43 (4182) [INFO] 
* 2023-03-24 03:10:43 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-24 03:10:43 (4151) [INFO] 
* 2023-03-24 03:11:11 (4165) [INFO] 
* 2023-03-24 03:11:11 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-24 03:11:11 (4182) [INFO] 
* 2023-03-24 03:11:11 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-24 03:11:11 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-24 03:11:11 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-24 03:11:11 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9fB2mXsc_w/ea_profile.json
* 2023-03-24 03:11:12 (1765) [INFO] Backed up EA4 profile to /tmp/9fB2mXsc_w/ea_profile.json
* 2023-03-24 03:11:13 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-25 03:11:44 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-25 03:11:44 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-25 03:11:44 (4151) [INFO] 
* 2023-03-25 03:11:44 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-25 03:11:44 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-25 03:11:44 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-25 03:11:44 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-25 03:11:44 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-25 03:11:45 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-25 03:11:45 (4182) [INFO] 
* 2023-03-25 03:11:45 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-25 03:11:45 (4151) [INFO] 
* 2023-03-25 03:12:05 (4165) [INFO] 
* 2023-03-25 03:12:05 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-25 03:12:05 (4182) [INFO] 
* 2023-03-25 03:12:05 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-25 03:12:05 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-25 03:12:05 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-25 03:12:05 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/N69L0U0e8a/ea_profile.json
* 2023-03-25 03:12:06 (1765) [INFO] Backed up EA4 profile to /tmp/N69L0U0e8a/ea_profile.json
* 2023-03-25 03:12:10 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-26 03:14:01 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-26 03:14:01 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-26 03:14:01 (4151) [INFO] 
* 2023-03-26 03:14:01 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-26 03:14:02 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-26 03:14:02 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-26 03:14:02 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-26 03:14:02 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-26 03:14:02 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-26 03:14:02 (4182) [INFO] 
* 2023-03-26 03:14:02 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-26 03:14:02 (4151) [INFO] 
* 2023-03-26 03:14:16 (4165) [INFO] 
* 2023-03-26 03:14:16 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-26 03:14:16 (4182) [INFO] 
* 2023-03-26 03:14:16 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-26 03:14:16 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-26 03:14:16 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-26 03:14:16 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d4fyIu0oKb/ea_profile.json
* 2023-03-26 03:14:17 (1765) [INFO] Backed up EA4 profile to /tmp/d4fyIu0oKb/ea_profile.json
* 2023-03-26 03:14:18 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-27 03:09:21 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-27 03:09:21 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-27 03:09:21 (4151) [INFO] 
* 2023-03-27 03:09:21 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-27 03:09:22 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-27 03:09:22 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-27 03:09:22 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-27 03:09:22 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-27 03:09:22 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-27 03:09:22 (4182) [INFO] 
* 2023-03-27 03:09:22 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-27 03:09:22 (4151) [INFO] 
* 2023-03-27 03:09:34 (4165) [INFO] 
* 2023-03-27 03:09:34 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-27 03:09:34 (4182) [INFO] 
* 2023-03-27 03:09:34 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-27 03:09:34 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-27 03:09:34 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-27 03:09:34 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/klSLEilk9E/ea_profile.json
* 2023-03-27 03:09:35 (1765) [INFO] Backed up EA4 profile to /tmp/klSLEilk9E/ea_profile.json
* 2023-03-27 03:09:36 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-28 03:13:09 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-28 03:13:09 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-28 03:13:09 (4151) [INFO] 
* 2023-03-28 03:13:09 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-28 03:13:09 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-28 03:13:09 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-28 03:13:09 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-28 03:13:09 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-28 03:13:09 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-28 03:13:09 (4182) [INFO] 
* 2023-03-28 03:13:09 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-28 03:13:09 (4151) [INFO] 
* 2023-03-28 03:13:49 (4165) [INFO] 
* 2023-03-28 03:13:49 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-28 03:13:49 (4182) [INFO] 
* 2023-03-28 03:13:49 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-28 03:13:49 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-28 03:13:49 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-28 03:13:49 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WhivKOFADs/ea_profile.json
* 2023-03-28 03:13:50 (1765) [INFO] Backed up EA4 profile to /tmp/WhivKOFADs/ea_profile.json
* 2023-03-28 03:14:01 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-29 03:09:33 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-29 03:09:33 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-29 03:09:33 (4151) [INFO] 
* 2023-03-29 03:09:33 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-29 03:09:34 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-29 03:09:34 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-29 03:09:34 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-29 03:09:34 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-29 03:09:34 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-29 03:09:34 (4182) [INFO] 
* 2023-03-29 03:09:34 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-29 03:09:34 (4151) [INFO] 
* 2023-03-29 03:09:47 (4165) [INFO] 
* 2023-03-29 03:09:47 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-29 03:09:47 (4182) [INFO] 
* 2023-03-29 03:09:47 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-29 03:09:47 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-29 03:09:47 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-29 03:09:47 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RFCISg0IGL/ea_profile.json
* 2023-03-29 03:09:48 (1765) [INFO] Backed up EA4 profile to /tmp/RFCISg0IGL/ea_profile.json
* 2023-03-29 03:09:50 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-30 03:11:03 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-30 03:11:03 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-30 03:11:03 (4151) [INFO] 
* 2023-03-30 03:11:03 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-30 03:11:03 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-30 03:11:03 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-30 03:11:03 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-30 03:11:03 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-30 03:11:03 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-30 03:11:03 (4182) [INFO] 
* 2023-03-30 03:11:03 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-30 03:11:03 (4151) [INFO] 
* 2023-03-30 03:11:17 (4165) [INFO] 
* 2023-03-30 03:11:17 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-03-30 03:11:17 (4182) [INFO] 
* 2023-03-30 03:11:17 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-30 03:11:17 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-03-30 03:11:17 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-30 03:11:17 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wzy3CD1Sio/ea_profile.json
* 2023-03-30 03:11:18 (1765) [INFO] Backed up EA4 profile to /tmp/Wzy3CD1Sio/ea_profile.json
* 2023-03-30 03:11:19 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-03-31 03:09:15 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-03-31 03:09:15 (3806) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.


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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from imunify360: [Errno 256] No more mirrors to try.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-03-31 03:09:15 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-03-31 03:09:15 (3638) [INFO] Checking if your system is up to date: 
* 2023-03-31 03:09:15 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-03-31 03:09:15 (4151) [INFO] 
* 2023-03-31 03:09:15 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-03-31 03:09:15 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-03-31 03:09:15 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-03-31 03:09:15 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-03-31 03:09:15 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-03-31 03:09:15 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-03-31 03:09:15 (4182) [INFO] 
* 2023-03-31 03:09:15 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-03-31 03:09:15 (4151) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]  One of the configured repositories failed (Unknown),
* 2023-03-31 03:09:43 (4165) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-03-31 03:09:43 (4165) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-03-31 03:09:43 (4165) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-03-31 03:09:43 (4165) [INFO]         distribution release than is supported by the repository (and the
* 2023-03-31 03:09:43 (4165) [INFO]         packages for the previous distribution release still work).
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-03-31 03:09:43 (4165) [INFO]             yum --disablerepo=<repoid> ...
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-03-31 03:09:43 (4165) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-03-31 03:09:43 (4165) [INFO]         again or use --enablerepo for temporary usage:
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]             yum-config-manager --disable <repoid>
* 2023-03-31 03:09:43 (4165) [INFO]         or
* 2023-03-31 03:09:43 (4165) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-03-31 03:09:43 (4165) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-03-31 03:09:43 (4165) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-03-31 03:09:43 (4165) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-03-31 03:09:43 (4165) [INFO]         compromise:
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-03-31 03:09:43 (4165) [INFO] 
* 2023-03-31 03:09:43 (4165) [INFO] updates: Check uncompressed DB failed
* 2023-03-31 03:09:43 (4182) [INFO] 
* 2023-03-31 03:09:43 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-03-31 03:09:43 (3661) [INFO] Checking /scripts/sysup
* 2023-03-31 03:09:43 (4150) [INFO] Running: /scripts/sysup
* 2023-03-31 03:09:43 (4151) [INFO] 
* 2023-03-31 03:09:44 (4165) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-03-31 03:09:44 (4165) [INFO]   All Needed Packages are already installed.
* 2023-03-31 03:09:44 (4182) [INFO] 
* 2023-03-31 03:09:44 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-03-31 03:09:44 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/H7UoPEnfwC/ea_profile.json
* 2023-03-31 03:09:52 (1765) [INFO] Backed up EA4 profile to /tmp/H7UoPEnfwC/ea_profile.json
* 2023-03-31 03:09:53 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-01 03:10:28 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-01 03:10:28 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-01 03:10:28 (4151) [INFO] 
* 2023-04-01 03:10:28 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-01 03:10:28 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-01 03:10:28 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-01 03:10:28 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-01 03:10:28 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-01 03:10:28 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-01 03:10:28 (4182) [INFO] 
* 2023-04-01 03:10:28 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-01 03:10:28 (4151) [INFO] 
* 2023-04-01 03:10:41 (4165) [INFO] 
* 2023-04-01 03:10:41 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-01 03:10:41 (4182) [INFO] 
* 2023-04-01 03:10:41 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-01 03:10:41 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-01 03:10:41 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-01 03:10:41 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eHCv78Btu2/ea_profile.json
* 2023-04-01 03:10:42 (1765) [INFO] Backed up EA4 profile to /tmp/eHCv78Btu2/ea_profile.json
* 2023-04-01 03:10:43 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-02 03:11:47 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-02 03:11:47 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-02 03:11:47 (4151) [INFO] 
* 2023-04-02 03:11:47 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-02 03:11:48 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-02 03:11:48 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-02 03:11:48 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-02 03:11:48 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-02 03:11:48 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-02 03:11:48 (4182) [INFO] 
* 2023-04-02 03:11:48 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-02 03:11:48 (4151) [INFO] 
* 2023-04-02 03:11:48 (4165) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 13659.
* 2023-04-02 03:11:48 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:11:48 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:11:48 (4165) [INFO]     Memory :  27 M RSS (420 MB VSZ)
* 2023-04-02 03:11:48 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:35 ago
* 2023-04-02 03:11:48 (4165) [INFO]     State  : Sleeping, pid: 13659
* 2023-04-02 03:11:50 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:11:50 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:11:50 (4165) [INFO]     Memory :  30 M RSS (3.3 GB VSZ)
* 2023-04-02 03:11:50 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:37 ago
* 2023-04-02 03:11:50 (4165) [INFO]     State  : Sleeping, pid: 13659
* 2023-04-02 03:11:52 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:11:52 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:11:52 (4165) [INFO]     Memory :  31 M RSS (3.3 GB VSZ)
* 2023-04-02 03:11:52 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:39 ago
* 2023-04-02 03:11:52 (4165) [INFO]     State  : Sleeping, pid: 13659
* 2023-04-02 03:11:54 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:11:54 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:11:54 (4165) [INFO]     Memory :  36 M RSS (3.3 GB VSZ)
* 2023-04-02 03:11:54 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:41 ago
* 2023-04-02 03:11:54 (4165) [INFO]     State  : Running, pid: 13659
* 2023-04-02 03:11:56 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:11:56 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:11:56 (4165) [INFO]     Memory :  36 M RSS (3.3 GB VSZ)
* 2023-04-02 03:11:56 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:43 ago
* 2023-04-02 03:11:56 (4165) [INFO]     State  : Running, pid: 13659
* 2023-04-02 03:11:58 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:11:59 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:11:59 (4165) [INFO]     Memory :  36 M RSS (3.3 GB VSZ)
* 2023-04-02 03:11:59 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:46 ago
* 2023-04-02 03:11:59 (4165) [INFO]     State  : Running, pid: 13659
* 2023-04-02 03:12:01 (4165) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-04-02 03:12:01 (4165) [INFO]   The other application is: yum
* 2023-04-02 03:12:01 (4165) [INFO]     Memory :  73 M RSS (3.4 GB VSZ)
* 2023-04-02 03:12:01 (4165) [INFO]     Started: Sun Apr  2 03:11:13 2023 - 00:48 ago
* 2023-04-02 03:12:01 (4165) [INFO]     State  : Running, pid: 13659
* 2023-04-02 03:12:04 (4165) [INFO] 
* 2023-04-02 03:12:04 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-02 03:12:04 (4182) [INFO] 
* 2023-04-02 03:12:04 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-02 03:12:04 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-02 03:12:04 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-02 03:12:04 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/69mX7SFdce/ea_profile.json
* 2023-04-02 03:12:05 (1765) [INFO] Backed up EA4 profile to /tmp/69mX7SFdce/ea_profile.json
* 2023-04-02 03:12:16 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-03 03:09:36 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-03 03:09:36 (3806) [ERROR] http://31.22.112.31/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/2bcf741d36a02697eba7f6ef4c8163ed7f98c9f4a815bcd7e31b47c40006d209-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/bb452a8d63e354778468cf59183ada4f7e23753fcb4cb561d99d6110126f74cf-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/e084d2af0c0b13a2b0b07c2c616b316f8aaccf2e3c881d222baa5442738eebd8-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/8ddc8d02ebd4fd7943b867afab37b42744bfc32c6e0ac8980a0343641be43e71-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/36b305338c3a266e6340ee844918c817c9a3cc6baa8a6253d087b10d430e6d38-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/3a1bb3405a379c99763fcd900cb7bb093c2ef18b997a84452f9f1b79602d1379-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/f94ac2de6ad46e32415519b0fc2677cc67636657572cd37263fcfde22917c523-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/extras/x86_64/repodata/511a574b4c3f907f9acfe5603566958fb6f09137292c5cd5d5d57c298864790f-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/1117ab2561f3d54eccdd8b8d6c0d9507082d4cf7e09c79d25f5a68b9b629a5a5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

MariaDB106: Check uncompressed DB failed
* 2023-04-03 03:09:36 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-03 03:09:36 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-03 03:09:36 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-03 03:09:36 (4151) [INFO] 
* 2023-04-03 03:09:37 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-03 03:09:37 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-03 03:09:37 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-03 03:09:37 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-03 03:09:37 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-03 03:09:37 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-03 03:09:37 (4182) [INFO] 
* 2023-04-03 03:09:37 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-03 03:09:37 (4151) [INFO] 
* 2023-04-03 03:09:51 (4165) [INFO] 
* 2023-04-03 03:09:51 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-03 03:09:51 (4182) [INFO] 
* 2023-04-03 03:09:51 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-03 03:09:51 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-03 03:09:51 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-03 03:09:51 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TybFRvmBs1/ea_profile.json
* 2023-04-03 03:09:53 (1765) [INFO] Backed up EA4 profile to /tmp/TybFRvmBs1/ea_profile.json
* 2023-04-03 03:09:54 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-04 03:09:50 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-04 03:09:50 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-04 03:09:50 (4151) [INFO] 
* 2023-04-04 03:09:50 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-04 03:09:50 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-04 03:09:50 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-04 03:09:50 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-04 03:09:50 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-04 03:09:50 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-04 03:09:50 (4182) [INFO] 
* 2023-04-04 03:09:50 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-04 03:09:50 (4151) [INFO] 
* 2023-04-04 03:10:07 (4165) [INFO] 
* 2023-04-04 03:10:07 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-04 03:10:07 (4182) [INFO] 
* 2023-04-04 03:10:07 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-04 03:10:07 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-04 03:10:07 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-04 03:10:07 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/VxAAtLX_kM/ea_profile.json
* 2023-04-04 03:10:08 (1765) [INFO] Backed up EA4 profile to /tmp/VxAAtLX_kM/ea_profile.json
* 2023-04-04 03:10:09 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-05 03:09:50 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-05 03:09:50 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-05 03:09:50 (4151) [INFO] 
* 2023-04-05 03:09:50 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-05 03:09:50 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-05 03:09:50 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-05 03:09:50 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-05 03:09:50 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-05 03:09:50 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-05 03:09:51 (4182) [INFO] 
* 2023-04-05 03:09:51 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-05 03:09:51 (4151) [INFO] 
* 2023-04-05 03:10:06 (4165) [INFO] 
* 2023-04-05 03:10:06 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-05 03:10:06 (4182) [INFO] 
* 2023-04-05 03:10:06 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-05 03:10:06 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-05 03:10:06 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-05 03:10:06 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T8AFWDR073/ea_profile.json
* 2023-04-05 03:10:06 (1765) [INFO] Backed up EA4 profile to /tmp/T8AFWDR073/ea_profile.json
* 2023-04-05 03:10:09 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-06 03:13:11 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-06 03:13:11 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-06 03:13:11 (4151) [INFO] 
* 2023-04-06 03:13:11 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-06 03:13:11 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-06 03:13:11 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-06 03:13:11 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-06 03:13:11 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-06 03:13:12 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-06 03:13:12 (4182) [INFO] 
* 2023-04-06 03:13:12 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-06 03:13:12 (4151) [INFO] 
* 2023-04-06 03:13:29 (4165) [INFO] 
* 2023-04-06 03:13:29 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-06 03:13:29 (4182) [INFO] 
* 2023-04-06 03:13:29 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-06 03:13:29 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-06 03:13:29 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-06 03:13:29 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/he6DasLviz/ea_profile.json
* 2023-04-06 03:13:30 (1765) [INFO] Backed up EA4 profile to /tmp/he6DasLviz/ea_profile.json
* 2023-04-06 03:13:33 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-07 03:09:39 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-07 03:09:39 (3806) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/f94ac2de6ad46e32415519b0fc2677cc67636657572cd37263fcfde22917c523-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-04-07 03:09:39 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-07 03:09:40 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-07 03:09:40 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-07 03:09:40 (4151) [INFO] 
* 2023-04-07 03:09:40 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-07 03:09:40 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-07 03:09:40 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-07 03:09:40 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-07 03:09:40 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-07 03:09:40 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-07 03:09:40 (4182) [INFO] 
* 2023-04-07 03:09:40 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-07 03:09:40 (4151) [INFO] 
* 2023-04-07 03:09:52 (4165) [INFO] 
* 2023-04-07 03:09:52 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-07 03:09:52 (4182) [INFO] 
* 2023-04-07 03:09:52 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-07 03:09:52 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-07 03:09:52 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-07 03:09:52 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DH4FbRAD3H/ea_profile.json
* 2023-04-07 03:09:53 (1765) [INFO] Backed up EA4 profile to /tmp/DH4FbRAD3H/ea_profile.json
* 2023-04-07 03:09:54 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-08 03:11:13 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-08 03:11:13 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-08 03:11:13 (4151) [INFO] 
* 2023-04-08 03:11:13 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-08 03:11:13 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-08 03:11:13 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-08 03:11:13 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-08 03:11:13 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-08 03:11:14 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-08 03:11:14 (4182) [INFO] 
* 2023-04-08 03:11:14 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-08 03:11:14 (4151) [INFO] 
* 2023-04-08 03:11:29 (4165) [INFO] 
* 2023-04-08 03:11:29 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-08 03:11:29 (4182) [INFO] 
* 2023-04-08 03:11:29 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-08 03:11:29 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-08 03:11:29 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-08 03:11:29 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CbCZCVjv0C/ea_profile.json
* 2023-04-08 03:11:29 (1765) [INFO] Backed up EA4 profile to /tmp/CbCZCVjv0C/ea_profile.json
* 2023-04-08 03:11:33 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-09 03:10:23 (3805) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-09 03:10:23 (3806) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 6350.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  74 M RSS (3.4 GB VSZ)
    Started: Sun Apr  9 03:10:02 2023 - 00:03 ago
    State  : Running, pid: 6350
* 2023-04-09 03:10:23 (2820) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-09 03:10:24 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-09 03:10:24 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-09 03:10:24 (4151) [INFO] 
* 2023-04-09 03:10:24 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-09 03:10:24 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-09 03:10:24 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-09 03:10:24 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-09 03:10:24 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-09 03:10:25 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-09 03:10:25 (4182) [INFO] 
* 2023-04-09 03:10:25 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-09 03:10:25 (4151) [INFO] 
* 2023-04-09 03:10:39 (4165) [INFO] 
* 2023-04-09 03:10:39 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-09 03:10:39 (4182) [INFO] 
* 2023-04-09 03:10:39 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-09 03:10:39 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-09 03:10:39 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-09 03:10:39 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/883FiTkKob/ea_profile.json
* 2023-04-09 03:10:40 (1765) [INFO] Backed up EA4 profile to /tmp/883FiTkKob/ea_profile.json
* 2023-04-09 03:10:41 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-10 03:09:53 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-10 03:09:53 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-10 03:09:53 (4151) [INFO] 
* 2023-04-10 03:09:54 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-10 03:09:54 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-10 03:09:54 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-10 03:09:54 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-10 03:09:54 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-10 03:09:54 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-10 03:09:54 (4182) [INFO] 
* 2023-04-10 03:09:54 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-10 03:09:54 (4151) [INFO] 
* 2023-04-10 03:10:12 (4165) [INFO] 
* 2023-04-10 03:10:12 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-10 03:10:12 (4182) [INFO] 
* 2023-04-10 03:10:12 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-10 03:10:12 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-10 03:10:12 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-10 03:10:12 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iJiD4iBdlc/ea_profile.json
* 2023-04-10 03:10:13 (1765) [INFO] Backed up EA4 profile to /tmp/iJiD4iBdlc/ea_profile.json
* 2023-04-10 03:10:14 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-11 03:11:53 (3638) [INFO] Checking if your system is up to date: 
* 2023-04-11 03:11:53 (4150) [INFO] Running: /usr/bin/yum clean all
* 2023-04-11 03:11:53 (4151) [INFO] 
* 2023-04-11 03:11:53 (4165) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-11 03:11:53 (4165) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-11 03:11:53 (4165) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-11 03:11:53 (4165) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-11 03:11:53 (4165) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-11 03:11:53 (4165) [INFO] Cleaning up list of fastest mirrors
* 2023-04-11 03:11:53 (4182) [INFO] 
* 2023-04-11 03:11:53 (4150) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-11 03:11:53 (4151) [INFO] 
* 2023-04-11 03:12:09 (4165) [INFO] 
* 2023-04-11 03:12:09 (4165) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-11 03:12:09 (4182) [INFO] 
* 2023-04-11 03:12:09 (3646) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-11 03:12:09 (2820) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-11 03:12:09 (3298) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-11 03:12:09 (1740) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/78Z3dIDKQQ/ea_profile.json
* 2023-04-11 03:12:10 (1765) [INFO] Backed up EA4 profile to /tmp/78Z3dIDKQQ/ea_profile.json
* 2023-04-11 03:12:11 (759) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-12 03:08:57 (372) [INFO] Self-update of script version 6 requested.
* 2023-04-12 03:08:57 (377) [INFO] Newer version of script found. Downloading.
* 2023-04-12 03:08:58 (386) [INFO] Script update to version 7 successful.
* 2023-04-12 03:09:39 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-12 03:09:39 (3854) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/f94ac2de6ad46e32415519b0fc2677cc67636657572cd37263fcfde22917c523-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-04-12 03:09:39 (2856) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-12 03:09:39 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-12 03:09:39 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-12 03:09:39 (4199) [INFO] 
* 2023-04-12 03:09:39 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-12 03:09:39 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-12 03:09:39 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-12 03:09:39 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-12 03:09:39 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-12 03:09:39 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-12 03:09:39 (4230) [INFO] 
* 2023-04-12 03:09:39 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-12 03:09:39 (4199) [INFO] 
* 2023-04-12 03:09:51 (4213) [INFO] 
* 2023-04-12 03:09:51 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-12 03:09:51 (4230) [INFO] 
* 2023-04-12 03:09:51 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-12 03:09:51 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-12 03:09:51 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-12 03:09:51 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4IYkzsU9hm/ea_profile.json
* 2023-04-12 03:09:52 (1805) [INFO] Backed up EA4 profile to /tmp/4IYkzsU9hm/ea_profile.json
* 2023-04-12 03:09:53 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-13 03:10:28 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-13 03:10:28 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-13 03:10:28 (4199) [INFO] 
* 2023-04-13 03:10:28 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-13 03:10:28 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-13 03:10:28 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-13 03:10:28 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-13 03:10:28 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-13 03:10:28 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-13 03:10:28 (4230) [INFO] 
* 2023-04-13 03:10:28 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-13 03:10:28 (4199) [INFO] 
* 2023-04-13 03:10:43 (4213) [INFO] 
* 2023-04-13 03:10:43 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-13 03:10:43 (4230) [INFO] 
* 2023-04-13 03:10:43 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-13 03:10:43 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-13 03:10:43 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-13 03:10:43 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/oPgywVjUSy/ea_profile.json
* 2023-04-13 03:10:44 (1805) [INFO] Backed up EA4 profile to /tmp/oPgywVjUSy/ea_profile.json
* 2023-04-13 03:10:46 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-14 03:10:04 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-14 03:10:04 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-14 03:10:04 (4199) [INFO] 
* 2023-04-14 03:10:04 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-14 03:10:04 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-14 03:10:04 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-14 03:10:04 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-14 03:10:04 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-14 03:10:05 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-14 03:10:05 (4230) [INFO] 
* 2023-04-14 03:10:05 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-14 03:10:05 (4199) [INFO] 
* 2023-04-14 03:10:19 (4213) [INFO] 
* 2023-04-14 03:10:19 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-14 03:10:19 (4230) [INFO] 
* 2023-04-14 03:10:19 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-14 03:10:19 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-14 03:10:20 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-14 03:10:20 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_EBye_MOoS/ea_profile.json
* 2023-04-14 03:10:21 (1805) [INFO] Backed up EA4 profile to /tmp/_EBye_MOoS/ea_profile.json
* 2023-04-14 03:10:22 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-15 03:10:43 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-15 03:10:43 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-15 03:10:43 (4199) [INFO] 
* 2023-04-15 03:10:43 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-15 03:10:43 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-15 03:10:43 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-15 03:10:43 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-15 03:10:43 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-15 03:10:46 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-15 03:10:46 (4230) [INFO] 
* 2023-04-15 03:10:46 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-15 03:10:46 (4199) [INFO] 
* 2023-04-15 03:11:04 (4213) [INFO] 
* 2023-04-15 03:11:04 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-15 03:11:04 (4230) [INFO] 
* 2023-04-15 03:11:04 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-15 03:11:04 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-15 03:11:04 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-15 03:11:04 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/slEtKTUnKq/ea_profile.json
* 2023-04-15 03:11:05 (1805) [INFO] Backed up EA4 profile to /tmp/slEtKTUnKq/ea_profile.json
* 2023-04-15 03:11:07 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-16 03:11:51 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-16 03:11:51 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-16 03:11:51 (4199) [INFO] 
* 2023-04-16 03:11:52 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-16 03:11:52 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-16 03:11:52 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-16 03:11:52 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-16 03:11:52 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-16 03:11:52 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-16 03:11:52 (4230) [INFO] 
* 2023-04-16 03:11:52 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-16 03:11:52 (4199) [INFO] 
* 2023-04-16 03:12:07 (4213) [INFO] 
* 2023-04-16 03:12:07 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-16 03:12:07 (4230) [INFO] 
* 2023-04-16 03:12:07 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-16 03:12:07 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-16 03:12:07 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-16 03:12:07 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ly2t3s1zrQ/ea_profile.json
* 2023-04-16 03:12:08 (1805) [INFO] Backed up EA4 profile to /tmp/ly2t3s1zrQ/ea_profile.json
* 2023-04-16 03:12:09 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-17 03:09:40 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-17 03:09:40 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-17 03:09:40 (4199) [INFO] 
* 2023-04-17 03:09:40 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-17 03:09:40 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-17 03:09:40 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-17 03:09:40 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-17 03:09:40 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-17 03:09:40 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-17 03:09:40 (4230) [INFO] 
* 2023-04-17 03:09:40 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-17 03:09:40 (4199) [INFO] 
* 2023-04-17 03:09:55 (4213) [INFO] 
* 2023-04-17 03:09:55 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-17 03:09:55 (4230) [INFO] 
* 2023-04-17 03:09:55 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-17 03:09:55 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-17 03:09:55 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-17 03:09:55 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NbSSnMVU7c/ea_profile.json
* 2023-04-17 03:09:56 (1805) [INFO] Backed up EA4 profile to /tmp/NbSSnMVU7c/ea_profile.json
* 2023-04-17 03:09:57 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-18 03:10:55 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-18 03:10:55 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-18 03:10:55 (4199) [INFO] 
* 2023-04-18 03:10:55 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-18 03:10:55 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-18 03:10:55 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-18 03:10:55 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-18 03:10:55 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-18 03:10:55 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-18 03:10:55 (4230) [INFO] 
* 2023-04-18 03:10:55 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-18 03:10:55 (4199) [INFO] 
* 2023-04-18 03:11:24 (4213) [INFO] 
* 2023-04-18 03:11:24 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-18 03:11:25 (4230) [INFO] 
* 2023-04-18 03:11:25 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-18 03:11:25 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-18 03:11:25 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-18 03:11:25 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/D4YgOtmKHt/ea_profile.json
* 2023-04-18 03:11:25 (1805) [INFO] Backed up EA4 profile to /tmp/D4YgOtmKHt/ea_profile.json
* 2023-04-18 03:11:36 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-19 03:09:16 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-19 03:09:16 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-19 03:09:16 (4199) [INFO] 
* 2023-04-19 03:09:16 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-19 03:09:16 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-19 03:09:16 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-19 03:09:16 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-19 03:09:16 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-19 03:09:16 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-19 03:09:16 (4230) [INFO] 
* 2023-04-19 03:09:16 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-19 03:09:16 (4199) [INFO] 
* 2023-04-19 03:09:37 (4213) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-04-19 03:09:37 (4213) [INFO] Trying other mirror.
* 2023-04-19 03:09:47 (4213) [INFO] 
* 2023-04-19 03:09:47 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-19 03:09:47 (4230) [INFO] 
* 2023-04-19 03:09:47 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-19 03:09:47 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-19 03:09:47 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-19 03:09:47 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r8i4EB4EpH/ea_profile.json
* 2023-04-19 03:09:48 (1805) [INFO] Backed up EA4 profile to /tmp/r8i4EB4EpH/ea_profile.json
* 2023-04-19 03:09:49 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-20 03:09:44 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-20 03:09:44 (3854) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c8a028f8eb53e3881dc4540c375a04064e066381b4964a73f198301a3f1715a-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-04-20 03:09:44 (2856) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-20 03:09:44 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-20 03:09:44 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-20 03:09:44 (4199) [INFO] 
* 2023-04-20 03:09:45 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-20 03:09:45 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-20 03:09:45 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-20 03:09:45 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-20 03:09:45 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-20 03:09:45 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-20 03:09:45 (4230) [INFO] 
* 2023-04-20 03:09:45 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-20 03:09:45 (4199) [INFO] 
* 2023-04-20 03:09:59 (4213) [INFO] 
* 2023-04-20 03:09:59 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-20 03:09:59 (4230) [INFO] 
* 2023-04-20 03:09:59 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-20 03:09:59 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-20 03:09:59 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-20 03:09:59 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/wbp90TUMBV/ea_profile.json
* 2023-04-20 03:10:00 (1805) [INFO] Backed up EA4 profile to /tmp/wbp90TUMBV/ea_profile.json
* 2023-04-20 03:10:01 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-21 03:09:46 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-21 03:09:46 (3854) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/ba1935697ebb717db8064d6bf20e0e1d0abd107db7c682fb4f8a0d3f61d36327-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://linux.darkpenguin.net/distros/CentOS/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

updates: Check uncompressed DB failed
* 2023-04-21 03:09:46 (2856) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-21 03:09:46 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-21 03:09:46 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-21 03:09:46 (4199) [INFO] 
* 2023-04-21 03:09:46 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-21 03:09:47 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-21 03:09:47 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-21 03:09:47 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-21 03:09:47 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-21 03:09:47 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-21 03:09:47 (4230) [INFO] 
* 2023-04-21 03:09:47 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-21 03:09:47 (4199) [INFO] 
* 2023-04-21 03:09:58 (4213) [INFO] 
* 2023-04-21 03:09:58 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-21 03:09:58 (4230) [INFO] 
* 2023-04-21 03:09:58 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-21 03:09:58 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-21 03:09:58 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-21 03:09:58 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/I4SU3eb247/ea_profile.json
* 2023-04-21 03:09:59 (1805) [INFO] Backed up EA4 profile to /tmp/I4SU3eb247/ea_profile.json
* 2023-04-21 03:09:59 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-22 03:09:52 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-22 03:09:52 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-22 03:09:52 (4199) [INFO] 
* 2023-04-22 03:09:52 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-22 03:09:52 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-22 03:09:52 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-22 03:09:52 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-22 03:09:52 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-22 03:09:52 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-22 03:09:52 (4230) [INFO] 
* 2023-04-22 03:09:52 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-22 03:09:52 (4199) [INFO] 
* 2023-04-22 03:10:06 (4213) [INFO] 
* 2023-04-22 03:10:06 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-22 03:10:06 (4230) [INFO] 
* 2023-04-22 03:10:06 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-22 03:10:06 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-22 03:10:06 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-22 03:10:06 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L9vYsskJFb/ea_profile.json
* 2023-04-22 03:10:07 (1805) [INFO] Backed up EA4 profile to /tmp/L9vYsskJFb/ea_profile.json
* 2023-04-22 03:10:08 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-23 03:09:37 (3853) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-04-23 03:09:37 (3854) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/wp-toolkit/repodata/ba1935697ebb717db8064d6bf20e0e1d0abd107db7c682fb4f8a0d3f61d36327-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/latest/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/eabbf2228efaaa842195b0dcb1769012294094c16de9b80204b20fc0687e8e0b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-04-23 03:09:37 (2856) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-04-23 03:09:37 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-23 03:09:37 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-23 03:09:37 (4199) [INFO] 
* 2023-04-23 03:09:37 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-23 03:09:38 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-23 03:09:38 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-23 03:09:38 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-23 03:09:38 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-23 03:09:38 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-23 03:09:38 (4230) [INFO] 
* 2023-04-23 03:09:38 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-23 03:09:38 (4199) [INFO] 
* 2023-04-23 03:09:50 (4213) [INFO] 
* 2023-04-23 03:09:50 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-23 03:09:50 (4230) [INFO] 
* 2023-04-23 03:09:50 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-23 03:09:50 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-23 03:09:50 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-23 03:09:50 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9ChozYsgW7/ea_profile.json
* 2023-04-23 03:09:51 (1805) [INFO] Backed up EA4 profile to /tmp/9ChozYsgW7/ea_profile.json
* 2023-04-23 03:09:52 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-24 03:09:17 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-24 03:09:17 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-24 03:09:17 (4199) [INFO] 
* 2023-04-24 03:09:17 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-24 03:09:17 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-24 03:09:17 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-24 03:09:17 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-24 03:09:17 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-24 03:09:18 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-24 03:09:18 (4230) [INFO] 
* 2023-04-24 03:09:18 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-24 03:09:18 (4199) [INFO] 
* 2023-04-24 03:09:40 (4213) [INFO] 
* 2023-04-24 03:09:40 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-24 03:09:40 (4230) [INFO] 
* 2023-04-24 03:09:40 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-24 03:09:40 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-24 03:09:40 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-24 03:09:40 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_3lJHGW6zX/ea_profile.json
* 2023-04-24 03:09:41 (1805) [INFO] Backed up EA4 profile to /tmp/_3lJHGW6zX/ea_profile.json
* 2023-04-24 03:09:42 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-25 03:09:00 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-25 03:09:00 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-25 03:09:00 (4199) [INFO] 
* 2023-04-25 03:09:00 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-25 03:09:00 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-25 03:09:00 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-25 03:09:00 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-25 03:09:00 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-25 03:09:00 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-25 03:09:00 (4230) [INFO] 
* 2023-04-25 03:09:00 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-25 03:09:00 (4199) [INFO] 
* 2023-04-25 03:09:14 (4213) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-25 03:09:14 (4213) [INFO] Trying other mirror.
* 2023-04-25 03:09:15 (4213) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/772f9f427d9231c82378b86df9d0e4d82ee2d932d17f935d3e4ca2c244638207-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-25 03:09:15 (4213) [INFO] Trying other mirror.
* 2023-04-25 03:09:16 (4213) [INFO] Traceback (most recent call last):
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-04-25 03:09:16 (4213) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-04-25 03:09:16 (4213) [INFO]     errcode = main(args)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-04-25 03:09:16 (4213) [INFO]     result, resultmsgs = base.doCommands()
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-04-25 03:09:16 (4213) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-04-25 03:09:16 (4213) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-04-25 03:09:16 (4213) [INFO]     ignore_case=True, repoid=repoid)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-04-25 03:09:16 (4213) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-04-25 03:09:16 (4213) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-04-25 03:09:16 (4213) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-04-25 03:09:16 (4213) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-04-25 03:09:16 (4213) [INFO]     self.repos.populateSack(which=repos)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2023-04-25 03:09:16 (4213) [INFO]     sack._retrieve_async(repo, data)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2023-04-25 03:09:16 (4213) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-04-25 03:09:16 (4213) [INFO]     cached=repo.cache)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-04-25 03:09:16 (4213) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-04-25 03:09:16 (4213) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-04-25 03:09:16 (4213) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-04-25 03:09:16 (4213) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/EA4/gen/primary_db.sqlite'
* 2023-04-25 03:09:16 (4230) [INFO] 
* 2023-04-25 03:09:16 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-25 03:09:16 (3709) [INFO] Checking /scripts/sysup
* 2023-04-25 03:09:16 (4198) [INFO] Running: /scripts/sysup
* 2023-04-25 03:09:16 (4199) [INFO] 
* 2023-04-25 03:09:16 (4213) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-04-25 03:09:17 (4213) [INFO]   All Needed Packages are already installed.
* 2023-04-25 03:09:17 (4230) [INFO] 
* 2023-04-25 03:09:17 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-25 03:09:17 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GctBuXrS3v/ea_profile.json
* 2023-04-25 03:09:24 (1805) [INFO] Backed up EA4 profile to /tmp/GctBuXrS3v/ea_profile.json
* 2023-04-25 03:09:25 (803) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-04-26 03:09:15 (3686) [INFO] Checking if your system is up to date: 
* 2023-04-26 03:09:15 (4198) [INFO] Running: /usr/bin/yum clean all
* 2023-04-26 03:09:15 (4199) [INFO] 
* 2023-04-26 03:09:15 (4213) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-26 03:09:16 (4213) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-26 03:09:16 (4213) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-26 03:09:16 (4213) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-26 03:09:16 (4213) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-26 03:09:16 (4213) [INFO] Cleaning up list of fastest mirrors
* 2023-04-26 03:09:16 (4230) [INFO] 
* 2023-04-26 03:09:16 (4198) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-26 03:09:16 (4199) [INFO] 
* 2023-04-26 03:09:38 (4213) [INFO] 
* 2023-04-26 03:09:38 (4213) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-26 03:09:38 (4230) [INFO] 
* 2023-04-26 03:09:38 (3694) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-26 03:09:38 (2856) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-26 03:09:38 (3346) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-26 03:09:38 (1780) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/F8ele8C_rm/ea_profile.json
* 2023-04-26 03:09:39 (1805) [INFO] Backed up EA4 profile to /tmp/F8ele8C_rm/ea_profile.json
* 2023-04-26 03:09:40 (797) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-27 03:09:01 (410) [INFO] Self-update of script version 7 requested.
* 2023-04-27 03:09:01 (415) [INFO] Newer version of script found. Downloading.
* 2023-04-27 03:09:01 (424) [INFO] Script update to version 8 successful.
* 2023-04-27 03:09:02 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-27 03:09:02 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-27 03:09:02 (3854) [INFO] 
* 2023-04-27 03:09:02 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-27 03:09:03 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-27 03:09:03 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-27 03:09:03 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-27 03:09:03 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-27 03:09:03 (3884) [INFO] 
* 2023-04-27 03:09:03 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-27 03:09:03 (3854) [INFO] 
* 2023-04-27 03:09:25 (3867) [INFO] 
* 2023-04-27 03:09:25 (3867) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-27 03:09:25 (3884) [INFO] 
* 2023-04-27 03:09:25 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-27 03:09:25 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-27 03:09:43 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-27 03:09:43 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hNTY2HMllm/ea_profile.json
* 2023-04-27 03:09:44 (2038) [INFO] Backed up EA4 profile to /tmp/hNTY2HMllm/ea_profile.json
* 2023-04-27 03:09:44 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-28 03:08:59 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-28 03:08:59 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-28 03:08:59 (3854) [INFO] 
* 2023-04-28 03:09:00 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-28 03:09:00 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-28 03:09:00 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-28 03:09:00 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-28 03:09:00 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-28 03:09:00 (3884) [INFO] 
* 2023-04-28 03:09:00 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-28 03:09:00 (3854) [INFO] 
* 2023-04-28 03:09:22 (3867) [INFO] 
* 2023-04-28 03:09:22 (3867) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-28 03:09:22 (3884) [INFO] 
* 2023-04-28 03:09:22 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-28 03:09:22 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-28 03:09:46 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-28 03:09:46 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NkYqMhyvpm/ea_profile.json
* 2023-04-28 03:09:47 (2038) [INFO] Backed up EA4 profile to /tmp/NkYqMhyvpm/ea_profile.json
* 2023-04-28 03:09:48 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-04-29 03:09:19 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-29 03:09:19 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-29 03:09:19 (3854) [INFO] 
* 2023-04-29 03:09:19 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-29 03:09:19 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-29 03:09:19 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-29 03:09:19 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-29 03:09:19 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-29 03:09:19 (3884) [INFO] 
* 2023-04-29 03:09:19 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-29 03:09:19 (3854) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]  One of the configured repositories failed (Unknown),
* 2023-04-29 03:09:30 (3867) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-04-29 03:09:30 (3867) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-04-29 03:09:30 (3867) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-04-29 03:09:30 (3867) [INFO]         distribution release than is supported by the repository (and the
* 2023-04-29 03:09:30 (3867) [INFO]         packages for the previous distribution release still work).
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-04-29 03:09:30 (3867) [INFO]             yum --disablerepo=<repoid> ...
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-04-29 03:09:30 (3867) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-04-29 03:09:30 (3867) [INFO]         again or use --enablerepo for temporary usage:
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]             yum-config-manager --disable <repoid>
* 2023-04-29 03:09:30 (3867) [INFO]         or
* 2023-04-29 03:09:30 (3867) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-04-29 03:09:30 (3867) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-04-29 03:09:30 (3867) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-04-29 03:09:30 (3867) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-04-29 03:09:30 (3867) [INFO]         compromise:
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-04-29 03:09:30 (3867) [INFO] 
* 2023-04-29 03:09:30 (3867) [INFO] database disk image is malformed
* 2023-04-29 03:09:30 (3884) [INFO] 
* 2023-04-29 03:09:30 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-29 03:09:30 (1594) [INFO] Checking /scripts/sysup
* 2023-04-29 03:09:30 (3853) [INFO] Running: /scripts/sysup
* 2023-04-29 03:09:30 (3854) [INFO] 
* 2023-04-29 03:09:31 (3867) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-04-29 03:09:31 (3867) [INFO]   All Needed Packages are already installed.
* 2023-04-29 03:09:31 (3884) [INFO] 
* 2023-04-29 03:09:46 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-29 03:09:46 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q17tFhB8R8/ea_profile.json
* 2023-04-29 03:09:47 (2038) [INFO] Backed up EA4 profile to /tmp/q17tFhB8R8/ea_profile.json
* 2023-04-29 03:09:48 (250) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-04-30 03:09:19 (1573) [INFO] Checking if your system is up to date: 
* 2023-04-30 03:09:19 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-04-30 03:09:19 (3854) [INFO] 
* 2023-04-30 03:09:20 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-04-30 03:09:20 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-04-30 03:09:20 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-04-30 03:09:20 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-04-30 03:09:20 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-04-30 03:09:20 (3884) [INFO] 
* 2023-04-30 03:09:20 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-04-30 03:09:20 (3854) [INFO] 
* 2023-04-30 03:09:28 (3867) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-30 03:09:28 (3867) [INFO] Trying other mirror.
* 2023-04-30 03:09:29 (3867) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/73371a71982e512337abcc8babb093cc1db1d2133d655b1fa8600a85639572fb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-04-30 03:09:29 (3867) [INFO] Trying other mirror.
* 2023-04-30 03:09:37 (3867) [INFO] 
* 2023-04-30 03:09:37 (3867) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-04-30 03:09:37 (3884) [INFO] 
* 2023-04-30 03:09:37 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-04-30 03:09:37 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-04-30 03:09:53 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-04-30 03:09:53 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9nZho7_Xl7/ea_profile.json
* 2023-04-30 03:09:54 (2038) [INFO] Backed up EA4 profile to /tmp/9nZho7_Xl7/ea_profile.json
* 2023-04-30 03:09:55 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-01 03:08:33 (1573) [INFO] Checking if your system is up to date: 
* 2023-05-01 03:08:33 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-05-01 03:08:33 (3854) [INFO] 
* 2023-05-01 03:08:33 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-01 03:08:33 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-01 03:08:33 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-01 03:08:33 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-01 03:08:33 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-01 03:08:33 (3884) [INFO] 
* 2023-05-01 03:08:33 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-01 03:08:33 (3854) [INFO] 
* 2023-05-01 03:08:47 (3867) [INFO] 
* 2023-05-01 03:08:47 (3867) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-01 03:08:47 (3884) [INFO] 
* 2023-05-01 03:08:47 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-01 03:08:47 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-01 03:09:04 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-01 03:09:04 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Zt5YG5cECB/ea_profile.json
* 2023-05-01 03:09:05 (2038) [INFO] Backed up EA4 profile to /tmp/Zt5YG5cECB/ea_profile.json
* 2023-05-01 03:09:06 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-02 03:09:49 (1573) [INFO] Checking if your system is up to date: 
* 2023-05-02 03:09:49 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-05-02 03:09:49 (3854) [INFO] 
* 2023-05-02 03:09:49 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-02 03:09:49 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-02 03:09:49 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-02 03:09:49 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-02 03:09:49 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-02 03:09:50 (3884) [INFO] 
* 2023-05-02 03:09:50 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-02 03:09:50 (3854) [INFO] 
* 2023-05-02 03:10:02 (3867) [INFO] 
* 2023-05-02 03:10:02 (3867) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-02 03:10:02 (3884) [INFO] 
* 2023-05-02 03:10:02 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-02 03:10:02 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-02 03:10:16 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-02 03:10:16 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZP5ELEAMFT/ea_profile.json
* 2023-05-02 03:10:17 (2038) [INFO] Backed up EA4 profile to /tmp/ZP5ELEAMFT/ea_profile.json
* 2023-05-02 03:10:18 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-03 03:08:37 (1573) [INFO] Checking if your system is up to date: 
* 2023-05-03 03:08:37 (3853) [INFO] Running: /usr/bin/yum clean all
* 2023-05-03 03:08:37 (3854) [INFO] 
* 2023-05-03 03:08:37 (3867) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-03 03:08:37 (3867) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-03 03:08:37 (3867) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-03 03:08:37 (3867) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-03 03:08:37 (3867) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-03 03:08:37 (3884) [INFO] 
* 2023-05-03 03:08:37 (3853) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-03 03:08:37 (3854) [INFO] 
* 2023-05-03 03:08:52 (3867) [INFO] 
* 2023-05-03 03:08:52 (3867) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-03 03:08:52 (3884) [INFO] 
* 2023-05-03 03:08:52 (1580) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-03 03:08:52 (144) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-03 03:09:09 (681) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-03 03:09:09 (2015) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/U2YGUL7g9O/ea_profile.json
* 2023-05-03 03:09:10 (2038) [INFO] Backed up EA4 profile to /tmp/U2YGUL7g9O/ea_profile.json
* 2023-05-03 03:09:11 (244) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-04 03:09:07 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-04 03:09:07 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-04 03:09:07 (3906) [INFO] 
* 2023-05-04 03:09:08 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-04 03:09:08 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-04 03:09:08 (3919) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-04 03:09:08 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-04 03:09:08 (3919) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-04 03:09:08 (3936) [INFO] 
* 2023-05-04 03:09:08 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-04 03:09:08 (3906) [INFO] 
* 2023-05-04 03:09:25 (3919) [INFO] Traceback (most recent call last):
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-05-04 03:09:25 (3919) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-05-04 03:09:25 (3919) [INFO]     errcode = main(args)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-05-04 03:09:25 (3919) [INFO]     result, resultmsgs = base.doCommands()
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-05-04 03:09:25 (3919) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-05-04 03:09:25 (3919) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-05-04 03:09:25 (3919) [INFO]     ignore_case=True, repoid=repoid)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-05-04 03:09:25 (3919) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-05-04 03:09:25 (3919) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-05-04 03:09:25 (3919) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-05-04 03:09:25 (3919) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-05-04 03:09:25 (3919) [INFO]     self.repos.populateSack(which=repos)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2023-05-04 03:09:25 (3919) [INFO]     sack._retrieve_async(repo, data)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2023-05-04 03:09:25 (3919) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-05-04 03:09:25 (3919) [INFO]     cached=repo.cache)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-05-04 03:09:25 (3919) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-05-04 03:09:25 (3919) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-05-04 03:09:25 (3919) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-05-04 03:09:25 (3919) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2023-05-04 03:09:25 (3936) [INFO] 
* 2023-05-04 03:09:25 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-04 03:09:25 (1646) [INFO] Checking /scripts/sysup
* 2023-05-04 03:09:25 (3905) [INFO] Running: /scripts/sysup
* 2023-05-04 03:09:25 (3906) [INFO] 
* 2023-05-04 03:09:25 (3919) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-04 03:09:25 (3919) [INFO]   All Needed Packages are already installed.
* 2023-05-04 03:09:25 (3936) [INFO] 
* 2023-05-04 03:09:43 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-04 03:09:43 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9dEb36QTeF/ea_profile.json
* 2023-05-04 03:09:44 (2090) [INFO] Backed up EA4 profile to /tmp/9dEb36QTeF/ea_profile.json
* 2023-05-04 03:09:45 (252) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-05 03:08:32 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-05 03:08:32 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-05 03:08:32 (3906) [INFO] 
* 2023-05-05 03:08:32 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-05 03:08:32 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-05 03:08:32 (3919) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-05 03:08:32 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-05 03:08:32 (3919) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-05 03:08:32 (3936) [INFO] 
* 2023-05-05 03:08:32 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-05 03:08:32 (3906) [INFO] 
* 2023-05-05 03:08:43 (3919) [INFO] 
* 2023-05-05 03:08:43 (3919) [INFO] kernel.x86_64                    3.10.0-1160.88.1.el7                    updates
* 2023-05-05 03:08:43 (3936) [INFO] 
* 2023-05-05 03:08:43 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-05 03:08:43 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-05 03:08:57 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-05 03:08:57 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/51xBtISJ0Y/ea_profile.json
* 2023-05-05 03:08:57 (2090) [INFO] Backed up EA4 profile to /tmp/51xBtISJ0Y/ea_profile.json
* 2023-05-05 03:08:58 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-06 03:09:53 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-06 03:09:53 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-06 03:09:53 (3906) [INFO] 
* 2023-05-06 03:09:53 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-06 03:09:53 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-06 03:09:53 (3919) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-06 03:09:53 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-06 03:09:53 (3919) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-06 03:09:53 (3936) [INFO] 
* 2023-05-06 03:09:53 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-06 03:09:53 (3906) [INFO] 
* 2023-05-06 03:10:05 (3919) [INFO] 
* 2023-05-06 03:10:05 (3919) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-06 03:10:05 (3936) [INFO] 
* 2023-05-06 03:10:05 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-06 03:10:05 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-06 03:10:19 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-06 03:10:19 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pihmU9NypT/ea_profile.json
* 2023-05-06 03:10:20 (2090) [INFO] Backed up EA4 profile to /tmp/pihmU9NypT/ea_profile.json
* 2023-05-06 03:10:21 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-07 03:09:31 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-07 03:09:31 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-07 03:09:31 (3906) [INFO] 
* 2023-05-07 03:09:31 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-07 03:09:31 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-07 03:09:31 (3919) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-07 03:09:31 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-07 03:09:31 (3919) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-07 03:09:31 (3936) [INFO] 
* 2023-05-07 03:09:31 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-07 03:09:31 (3906) [INFO] 
* 2023-05-07 03:09:44 (3919) [INFO] 
* 2023-05-07 03:09:44 (3919) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-07 03:09:44 (3936) [INFO] 
* 2023-05-07 03:09:44 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-07 03:09:44 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-07 03:10:04 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-07 03:10:04 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jrAgJgZGSt/ea_profile.json
* 2023-05-07 03:10:05 (2090) [INFO] Backed up EA4 profile to /tmp/jrAgJgZGSt/ea_profile.json
* 2023-05-07 03:10:06 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-08 03:08:35 (1625) [INFO] Checking if your system is up to date: 
* 2023-05-08 03:08:35 (3905) [INFO] Running: /usr/bin/yum clean all
* 2023-05-08 03:08:35 (3906) [INFO] 
* 2023-05-08 03:08:35 (3919) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-08 03:08:35 (3919) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-08 03:08:35 (3919) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-08 03:08:35 (3919) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-08 03:08:35 (3919) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-08 03:08:35 (3936) [INFO] 
* 2023-05-08 03:08:35 (3905) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-08 03:08:35 (3906) [INFO] 
* 2023-05-08 03:08:48 (3919) [INFO] 
* 2023-05-08 03:08:48 (3919) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-08 03:08:48 (3936) [INFO] 
* 2023-05-08 03:08:48 (1632) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-08 03:08:48 (145) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-08 03:09:01 (734) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-08 03:09:01 (2067) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WZuDS9z4Gl/ea_profile.json
* 2023-05-08 03:09:02 (2090) [INFO] Backed up EA4 profile to /tmp/WZuDS9z4Gl/ea_profile.json
* 2023-05-08 03:09:03 (246) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-09 03:08:39 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-09 03:08:39 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-09 03:08:39 (3975) [INFO] 
* 2023-05-09 03:08:39 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-09 03:08:39 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-09 03:08:39 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-09 03:08:39 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-09 03:08:39 (3988) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-09 03:08:39 (4005) [INFO] 
* 2023-05-09 03:08:39 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-09 03:08:39 (3975) [INFO] 
* 2023-05-09 03:08:52 (3988) [INFO] 
* 2023-05-09 03:08:52 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-09 03:08:53 (4005) [INFO] 
* 2023-05-09 03:08:53 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-09 03:08:53 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-09 03:09:09 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-09 03:09:09 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j1WHv1woZo/ea_profile.json
* 2023-05-09 03:09:10 (2159) [INFO] Backed up EA4 profile to /tmp/j1WHv1woZo/ea_profile.json
* 2023-05-09 03:09:11 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-10 03:08:42 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-10 03:08:42 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-10 03:08:42 (3975) [INFO] 
* 2023-05-10 03:08:42 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-10 03:08:42 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-10 03:08:42 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-10 03:08:42 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 updates
* 2023-05-10 03:08:42 (3988) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-10 03:08:42 (4005) [INFO] 
* 2023-05-10 03:08:42 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-10 03:08:42 (3975) [INFO] 
* 2023-05-10 03:08:56 (3988) [INFO] 
* 2023-05-10 03:08:56 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-10 03:08:56 (4005) [INFO] 
* 2023-05-10 03:08:56 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-10 03:08:56 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-10 03:09:12 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-10 03:09:12 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uVCjRcft7l/ea_profile.json
* 2023-05-10 03:09:12 (2159) [INFO] Backed up EA4 profile to /tmp/uVCjRcft7l/ea_profile.json
* 2023-05-10 03:09:13 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-11 03:12:01 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-11 03:12:01 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-11 03:12:01 (3975) [INFO] 
* 2023-05-11 03:12:01 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-11 03:12:02 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-11 03:12:02 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-11 03:12:02 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-11 03:12:02 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-11 03:12:02 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-11 03:12:02 (4005) [INFO] 
* 2023-05-11 03:12:02 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-11 03:12:02 (3975) [INFO] 
* 2023-05-11 03:12:09 (3988) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
* 2023-05-11 03:12:09 (3988) [INFO] Trying other mirror.
* 2023-05-11 03:12:09 (3988) [INFO] To address this issue please refer to the below wiki article 
* 2023-05-11 03:12:09 (3988) [INFO] 
* 2023-05-11 03:12:09 (3988) [INFO] https://wiki.centos.org/yum-errors
* 2023-05-11 03:12:09 (3988) [INFO] 
* 2023-05-11 03:12:09 (3988) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2023-05-11 03:12:09 (3988) [INFO] 
* 2023-05-11 03:12:11 (3988) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
* 2023-05-11 03:12:11 (3988) [INFO] Trying other mirror.
* 2023-05-11 03:12:14 (3988) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
* 2023-05-11 03:12:14 (3988) [INFO] Trying other mirror.
* 2023-05-11 03:12:31 (3988) [INFO] 
* 2023-05-11 03:12:31 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-11 03:12:31 (4005) [INFO] 
* 2023-05-11 03:12:31 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-11 03:12:31 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-11 03:12:32 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 03:12:32 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 03:12:32 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 03:12:32 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-11 03:12:55 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-11 03:12:55 (1526) [ERROR] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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

https://download.imunify360.com/el/7/slot-7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
* 2023-05-11 03:12:55 (148) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-11 03:12:55 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-11 03:12:55 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nkMh5LgiI6/ea_profile.json
* 2023-05-11 03:12:57 (2159) [INFO] Backed up EA4 profile to /tmp/nkMh5LgiI6/ea_profile.json
* 2023-05-11 03:12:58 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-12 03:08:39 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-12 03:08:39 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-12 03:08:39 (3975) [INFO] 
* 2023-05-12 03:08:39 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-12 03:08:39 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-12 03:08:39 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-12 03:08:39 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-12 03:08:39 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-12 03:08:39 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-12 03:08:39 (4005) [INFO] 
* 2023-05-12 03:08:39 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-12 03:08:39 (3975) [INFO] 
* 2023-05-12 03:08:55 (3988) [INFO] 
* 2023-05-12 03:08:55 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-12 03:08:55 (4005) [INFO] 
* 2023-05-12 03:08:55 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-12 03:08:55 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-12 03:08:57 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 03:08:57 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 03:08:57 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 03:08:57 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-12 03:09:36 (1525) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-12 03:09:36 (1526) [ERROR] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/25203984190353e3d6642c0f5eab9ddce6c1d1a048e112072d2d72592a7c6311-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-05-12 03:09:36 (148) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-12 03:09:36 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-12 03:09:36 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YvdD3ztt3C/ea_profile.json
* 2023-05-12 03:09:37 (2159) [INFO] Backed up EA4 profile to /tmp/YvdD3ztt3C/ea_profile.json
* 2023-05-12 03:09:38 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-13 03:09:22 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-13 03:09:22 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-13 03:09:22 (3975) [INFO] 
* 2023-05-13 03:09:22 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-13 03:09:22 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-13 03:09:22 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-13 03:09:22 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-13 03:09:22 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-13 03:09:22 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-13 03:09:22 (4005) [INFO] 
* 2023-05-13 03:09:22 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-13 03:09:22 (3975) [INFO] 
* 2023-05-13 03:09:34 (3988) [INFO] 
* 2023-05-13 03:09:34 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-13 03:09:34 (4005) [INFO] 
* 2023-05-13 03:09:34 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-13 03:09:34 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-13 03:09:35 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 03:09:35 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 03:09:35 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 03:09:35 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-13 03:09:50 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-13 03:09:50 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/r7SR_9TU56/ea_profile.json
* 2023-05-13 03:09:51 (2159) [INFO] Backed up EA4 profile to /tmp/r7SR_9TU56/ea_profile.json
* 2023-05-13 03:09:52 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-14 03:09:26 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-14 03:09:26 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-14 03:09:26 (3975) [INFO] 
* 2023-05-14 03:09:26 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-14 03:09:26 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-14 03:09:26 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-14 03:09:26 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-14 03:09:26 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-14 03:09:26 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-14 03:09:27 (4005) [INFO] 
* 2023-05-14 03:09:27 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-14 03:09:27 (3975) [INFO] 
* 2023-05-14 03:09:39 (3988) [INFO] 
* 2023-05-14 03:09:39 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-14 03:09:39 (4005) [INFO] 
* 2023-05-14 03:09:39 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-14 03:09:39 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-14 03:09:41 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 03:09:41 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 03:09:41 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 03:09:41 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-14 03:09:55 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-14 03:09:55 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZQ7ouiidWV/ea_profile.json
* 2023-05-14 03:09:56 (2159) [INFO] Backed up EA4 profile to /tmp/ZQ7ouiidWV/ea_profile.json
* 2023-05-14 03:09:57 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-15 03:08:38 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-15 03:08:38 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-15 03:08:38 (3975) [INFO] 
* 2023-05-15 03:08:38 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-15 03:08:38 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-15 03:08:38 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-15 03:08:38 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-15 03:08:38 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-15 03:08:38 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-15 03:08:38 (4005) [INFO] 
* 2023-05-15 03:08:38 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-15 03:08:38 (3975) [INFO] 
* 2023-05-15 03:08:54 (3988) [INFO] 
* 2023-05-15 03:08:54 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-15 03:08:54 (4005) [INFO] 
* 2023-05-15 03:08:54 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-15 03:08:54 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-15 03:08:55 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 03:08:55 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 03:08:55 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 03:08:55 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-15 03:09:11 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-15 03:09:11 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pVb8_VF3ry/ea_profile.json
* 2023-05-15 03:09:12 (2159) [INFO] Backed up EA4 profile to /tmp/pVb8_VF3ry/ea_profile.json
* 2023-05-15 03:09:13 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-16 03:08:38 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-16 03:08:38 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-16 03:08:38 (3975) [INFO] 
* 2023-05-16 03:08:38 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-16 03:08:38 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-16 03:08:38 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-16 03:08:38 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-16 03:08:38 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-16 03:08:38 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-16 03:08:38 (4005) [INFO] 
* 2023-05-16 03:08:38 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-16 03:08:38 (3975) [INFO] 
* 2023-05-16 03:08:51 (3988) [INFO] 
* 2023-05-16 03:08:51 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-16 03:08:51 (4005) [INFO] 
* 2023-05-16 03:08:51 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-16 03:08:51 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-16 03:08:53 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 03:08:53 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 03:08:53 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 03:08:53 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-16 03:09:08 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-16 03:09:08 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XN_JUIOqsf/ea_profile.json
* 2023-05-16 03:09:08 (2159) [INFO] Backed up EA4 profile to /tmp/XN_JUIOqsf/ea_profile.json
* 2023-05-16 03:09:10 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-17 03:08:46 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-17 03:08:46 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-17 03:08:46 (3975) [INFO] 
* 2023-05-17 03:08:46 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-17 03:08:46 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-17 03:08:46 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-17 03:08:46 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-17 03:08:46 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-17 03:08:46 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-17 03:08:47 (4005) [INFO] 
* 2023-05-17 03:08:47 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-17 03:08:47 (3975) [INFO] 
* 2023-05-17 03:09:01 (3988) [INFO] 
* 2023-05-17 03:09:01 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-17 03:09:01 (4005) [INFO] 
* 2023-05-17 03:09:01 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-17 03:09:01 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-17 03:09:02 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 03:09:02 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 03:09:02 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 03:09:02 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-17 03:09:39 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-17 03:09:39 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vbrrqWQYfh/ea_profile.json
* 2023-05-17 03:09:40 (2159) [INFO] Backed up EA4 profile to /tmp/vbrrqWQYfh/ea_profile.json
* 2023-05-17 03:09:41 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-18 03:09:03 (1659) [INFO] Checking if your system is up to date: 
* 2023-05-18 03:09:03 (3974) [INFO] Running: /usr/bin/yum clean all
* 2023-05-18 03:09:03 (3975) [INFO] 
* 2023-05-18 03:09:04 (3988) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-18 03:09:04 (3988) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-18 03:09:04 (3988) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-18 03:09:04 (3988) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-18 03:09:04 (3988) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-18 03:09:04 (3988) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-18 03:09:04 (4005) [INFO] 
* 2023-05-18 03:09:04 (3974) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-18 03:09:04 (3975) [INFO] 
* 2023-05-18 03:09:30 (3988) [INFO] 
* 2023-05-18 03:09:30 (3988) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-18 03:09:30 (4005) [INFO] 
* 2023-05-18 03:09:30 (1666) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-18 03:09:30 (148) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-18 03:09:31 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-5' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 03:09:31 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-6' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 03:09:31 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-7' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 03:09:31 (1595) [INFO] Unsupported YUM repo enabled 'imunify360-rollout-8' without packages installed from /etc/yum.repos.d/imunify-new-rollout.repo, these will be disabled before ELevation
* 2023-05-18 03:09:45 (741) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-18 03:09:45 (2136) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2_74VEDQHg/ea_profile.json
* 2023-05-18 03:09:46 (2159) [INFO] Backed up EA4 profile to /tmp/2_74VEDQHg/ea_profile.json
* 2023-05-18 03:09:47 (251) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-19 03:08:49 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-19 03:08:49 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-19 03:08:49 (4086) [INFO] 
* 2023-05-19 03:08:50 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-19 03:08:50 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-19 03:08:50 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-19 03:08:50 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-19 03:08:50 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-19 03:08:50 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-19 03:08:50 (4116) [INFO] 
* 2023-05-19 03:08:50 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-19 03:08:50 (4086) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]  One of the configured repositories failed (Unknown),
* 2023-05-19 03:09:11 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-19 03:09:11 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-19 03:09:11 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-19 03:09:11 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-19 03:09:11 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-19 03:09:11 (4099) [INFO]             yum --disablerepo=<repoid> ...
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-19 03:09:11 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-19 03:09:11 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]             yum-config-manager --disable <repoid>
* 2023-05-19 03:09:11 (4099) [INFO]         or
* 2023-05-19 03:09:11 (4099) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-19 03:09:11 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-19 03:09:11 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-19 03:09:11 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-19 03:09:11 (4099) [INFO]         compromise:
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-05-19 03:09:11 (4099) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO] updates: Check uncompressed DB failed
* 2023-05-19 03:09:11 (4116) [INFO] 
* 2023-05-19 03:09:11 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-19 03:09:11 (1720) [INFO] Checking /scripts/sysup
* 2023-05-19 03:09:11 (4085) [INFO] Running: /scripts/sysup
* 2023-05-19 03:09:11 (4086) [INFO] 
* 2023-05-19 03:09:11 (4099) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-19 03:09:11 (4099) [INFO]   All Needed Packages are already installed.
* 2023-05-19 03:09:11 (4116) [INFO] 
* 2023-05-19 03:10:00 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-19 03:10:00 (1566) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-05-19 03:10:00 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-19 03:10:00 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-19 03:10:00 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SSw9ipM00u/ea_profile.json
* 2023-05-19 03:10:01 (2258) [INFO] Backed up EA4 profile to /tmp/SSw9ipM00u/ea_profile.json
* 2023-05-19 03:10:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-20 03:09:05 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-20 03:09:05 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-20 03:09:05 (4086) [INFO] 
* 2023-05-20 03:09:05 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-20 03:09:05 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-20 03:09:05 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-20 03:09:05 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-20 03:09:05 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-20 03:09:05 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-20 03:09:05 (4116) [INFO] 
* 2023-05-20 03:09:05 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-20 03:09:05 (4086) [INFO] 
* 2023-05-20 03:09:28 (4099) [INFO] 
* 2023-05-20 03:09:28 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-20 03:09:28 (4116) [INFO] 
* 2023-05-20 03:09:28 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-20 03:09:28 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-20 03:09:42 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-20 03:09:42 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qomi6he1BS/ea_profile.json
* 2023-05-20 03:09:43 (2258) [INFO] Backed up EA4 profile to /tmp/qomi6he1BS/ea_profile.json
* 2023-05-20 03:09:44 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-21 03:09:09 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-21 03:09:09 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-21 03:09:09 (4086) [INFO] 
* 2023-05-21 03:09:09 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-21 03:09:09 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-21 03:09:09 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-21 03:09:09 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-21 03:09:09 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-21 03:09:09 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-21 03:09:09 (4116) [INFO] 
* 2023-05-21 03:09:09 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-21 03:09:09 (4086) [INFO] 
* 2023-05-21 03:09:15 (4099) [INFO] http://185.157.208.252/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-21 03:09:15 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:15 (4099) [INFO] http://185.157.208.252/cpanelsync/repos/CentOS/7/cpanel-plugins/x86_64/repodata/1c03b65350f8c5c116276e763e35f60987b11d291698f81a0fb12e8c631cf422-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-21 03:09:15 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:15 (4099) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/fcee46d3d8f8ebaf09d6f5ba0a2a5ae20220f17117f6749216b03875ad957c53-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-05-21 03:09:15 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:15 (4099) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/b7bb7cd4ac46a6f7ec4aa3e87d636c87c2acb26a71bffb50fbdece1e50e7c90b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-05-21 03:09:15 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:16 (4099) [INFO] http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/01db8db9253867f3f7004688d878f7a17657f0b7ffdeca4b351307dec45a25f0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-21 03:09:16 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:19 (4099) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-21 03:09:19 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:26 (4099) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-05-21 03:09:26 (4099) [INFO] Trying other mirror.
* 2023-05-21 03:09:26 (4099) [INFO] 
* 2023-05-21 03:09:26 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-21 03:09:26 (4116) [INFO] 
* 2023-05-21 03:09:26 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-21 03:09:26 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-21 03:09:40 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-21 03:09:40 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rkPZR_mjIL/ea_profile.json
* 2023-05-21 03:09:41 (2258) [INFO] Backed up EA4 profile to /tmp/rkPZR_mjIL/ea_profile.json
* 2023-05-21 03:09:42 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-22 03:08:31 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-22 03:08:31 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-22 03:08:31 (4086) [INFO] 
* 2023-05-22 03:08:31 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-22 03:08:32 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-22 03:08:32 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-22 03:08:32 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-22 03:08:32 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-22 03:08:32 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-22 03:08:32 (4116) [INFO] 
* 2023-05-22 03:08:32 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-22 03:08:32 (4086) [INFO] 
* 2023-05-22 03:08:44 (4099) [INFO] 
* 2023-05-22 03:08:44 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-22 03:08:44 (4116) [INFO] 
* 2023-05-22 03:08:44 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-22 03:08:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-22 03:08:59 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-22 03:08:59 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/To1iNrcvic/ea_profile.json
* 2023-05-22 03:09:00 (2258) [INFO] Backed up EA4 profile to /tmp/To1iNrcvic/ea_profile.json
* 2023-05-22 03:09:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-23 03:09:52 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-23 03:09:52 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-23 03:09:52 (4086) [INFO] 
* 2023-05-23 03:09:52 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-23 03:09:52 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-23 03:09:52 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-23 03:09:52 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-23 03:09:52 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-23 03:09:52 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-23 03:09:52 (4116) [INFO] 
* 2023-05-23 03:09:52 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-23 03:09:52 (4086) [INFO] 
* 2023-05-23 03:11:15 (4099) [INFO] 
* 2023-05-23 03:11:15 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-23 03:11:15 (4116) [INFO] 
* 2023-05-23 03:11:15 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-23 03:11:15 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-23 03:13:29 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-23 03:13:29 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PLa7Cm1NjT/ea_profile.json
* 2023-05-23 03:13:29 (2258) [INFO] Backed up EA4 profile to /tmp/PLa7Cm1NjT/ea_profile.json
* 2023-05-23 03:13:30 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-24 03:08:37 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-24 03:08:37 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-24 03:08:37 (4086) [INFO] 
* 2023-05-24 03:08:37 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-24 03:08:37 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-24 03:08:37 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-24 03:08:37 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-24 03:08:37 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-24 03:08:37 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-24 03:08:37 (4116) [INFO] 
* 2023-05-24 03:08:37 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-24 03:08:37 (4086) [INFO] 
* 2023-05-24 03:08:52 (4099) [INFO] 
* 2023-05-24 03:08:52 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-24 03:08:52 (4116) [INFO] 
* 2023-05-24 03:08:52 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-24 03:08:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-24 03:09:55 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-24 03:09:55 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8bMNOZwBwL/ea_profile.json
* 2023-05-24 03:09:55 (2258) [INFO] Backed up EA4 profile to /tmp/8bMNOZwBwL/ea_profile.json
* 2023-05-24 03:09:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-25 03:09:13 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-25 03:09:13 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-25 03:09:13 (4086) [INFO] 
* 2023-05-25 03:09:13 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-25 03:09:14 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-25 03:09:14 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-25 03:09:14 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-25 03:09:14 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-25 03:09:14 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-25 03:09:14 (4116) [INFO] 
* 2023-05-25 03:09:14 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-25 03:09:14 (4086) [INFO] 
* 2023-05-25 03:09:27 (4099) [INFO] http://185.157.208.252/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-25 03:09:27 (4099) [INFO] Trying other mirror.
* 2023-05-25 03:09:28 (4099) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-25 03:09:28 (4099) [INFO] Trying other mirror.
* 2023-05-25 03:09:29 (4099) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-25 03:09:29 (4099) [INFO] Trying other mirror.
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]  One of the configured repositories failed (Unknown),
* 2023-05-25 03:09:40 (4099) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-05-25 03:09:40 (4099) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-05-25 03:09:40 (4099) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-05-25 03:09:40 (4099) [INFO]         distribution release than is supported by the repository (and the
* 2023-05-25 03:09:40 (4099) [INFO]         packages for the previous distribution release still work).
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-05-25 03:09:40 (4099) [INFO]             yum --disablerepo=<repoid> ...
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-05-25 03:09:40 (4099) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-05-25 03:09:40 (4099) [INFO]         again or use --enablerepo for temporary usage:
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]             yum-config-manager --disable <repoid>
* 2023-05-25 03:09:40 (4099) [INFO]         or
* 2023-05-25 03:09:40 (4099) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-05-25 03:09:40 (4099) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-05-25 03:09:40 (4099) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-05-25 03:09:40 (4099) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-05-25 03:09:40 (4099) [INFO]         compromise:
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-05-25 03:09:40 (4099) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO] EA4: Check uncompressed DB failed
* 2023-05-25 03:09:40 (4116) [INFO] 
* 2023-05-25 03:09:40 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-25 03:09:40 (1720) [INFO] Checking /scripts/sysup
* 2023-05-25 03:09:40 (4085) [INFO] Running: /scripts/sysup
* 2023-05-25 03:09:40 (4086) [INFO] 
* 2023-05-25 03:09:40 (4099) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-05-25 03:09:41 (4099) [INFO]   All Needed Packages are already installed.
* 2023-05-25 03:09:41 (4116) [INFO] 
* 2023-05-25 03:10:01 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-25 03:10:01 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7H0CuflPZm/ea_profile.json
* 2023-05-25 03:10:02 (2258) [INFO] Backed up EA4 profile to /tmp/7H0CuflPZm/ea_profile.json
* 2023-05-25 03:10:03 (268) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-05-26 03:09:09 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-26 03:09:09 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-26 03:09:09 (4086) [INFO] 
* 2023-05-26 03:09:09 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-26 03:09:09 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-26 03:09:09 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-26 03:09:09 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-26 03:09:09 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-26 03:09:09 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-26 03:09:09 (4116) [INFO] 
* 2023-05-26 03:09:09 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-26 03:09:09 (4086) [INFO] 
* 2023-05-26 03:10:09 (4099) [INFO] 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-26 03:10:09 (4099) [INFO] Trying other mirror.
* 2023-05-26 03:10:11 (4099) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/734f657df436c7e9955fc2676b51f53804e80dbbbc11b38e590ac8fafda76c01-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-05-26 03:10:11 (4099) [INFO] Trying other mirror.
* 2023-05-26 03:10:21 (4099) [INFO] 
* 2023-05-26 03:10:21 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-26 03:10:21 (4116) [INFO] 
* 2023-05-26 03:10:21 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-26 03:10:21 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-26 03:11:19 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-26 03:11:19 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JZmMnDJHtU/ea_profile.json
* 2023-05-26 03:11:19 (2258) [INFO] Backed up EA4 profile to /tmp/JZmMnDJHtU/ea_profile.json
* 2023-05-26 03:11:20 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-27 03:09:31 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-27 03:09:31 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-27 03:09:31 (4086) [INFO] 
* 2023-05-27 03:09:31 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-27 03:09:31 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-27 03:09:31 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-27 03:09:31 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-27 03:09:31 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-27 03:09:31 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-27 03:09:31 (4116) [INFO] 
* 2023-05-27 03:09:31 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-27 03:09:31 (4086) [INFO] 
* 2023-05-27 03:10:46 (4099) [INFO] 
* 2023-05-27 03:10:46 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-27 03:10:47 (4116) [INFO] 
* 2023-05-27 03:10:47 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-27 03:10:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-27 03:13:08 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-27 03:13:08 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yr1oGg3nje/ea_profile.json
* 2023-05-27 03:13:09 (2258) [INFO] Backed up EA4 profile to /tmp/yr1oGg3nje/ea_profile.json
* 2023-05-27 03:13:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-28 03:09:29 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-28 03:09:29 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-28 03:09:29 (4086) [INFO] 
* 2023-05-28 03:09:29 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-28 03:09:29 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-28 03:09:29 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-28 03:09:29 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-28 03:09:29 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-28 03:09:29 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-28 03:09:29 (4116) [INFO] 
* 2023-05-28 03:09:29 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-28 03:09:29 (4086) [INFO] 
* 2023-05-28 03:10:48 (4099) [INFO] 
* 2023-05-28 03:10:48 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-28 03:10:48 (4116) [INFO] 
* 2023-05-28 03:10:48 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-28 03:10:48 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-28 03:11:27 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-28 03:11:27 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nFwKOL8eOH/ea_profile.json
* 2023-05-28 03:11:28 (2258) [INFO] Backed up EA4 profile to /tmp/nFwKOL8eOH/ea_profile.json
* 2023-05-28 03:11:29 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-29 03:08:38 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-29 03:08:38 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-29 03:08:38 (4086) [INFO] 
* 2023-05-29 03:08:38 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-29 03:08:38 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-29 03:08:38 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-29 03:08:38 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-29 03:08:38 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-29 03:08:38 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-29 03:08:38 (4116) [INFO] 
* 2023-05-29 03:08:38 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-29 03:08:38 (4086) [INFO] 
* 2023-05-29 03:08:54 (4099) [INFO] 
* 2023-05-29 03:08:54 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-29 03:08:54 (4116) [INFO] 
* 2023-05-29 03:08:54 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-29 03:08:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-29 03:09:53 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-29 03:09:53 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pvdLSaYYKM/ea_profile.json
* 2023-05-29 03:09:54 (2258) [INFO] Backed up EA4 profile to /tmp/pvdLSaYYKM/ea_profile.json
* 2023-05-29 03:09:55 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-30 03:08:42 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-30 03:08:42 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-30 03:08:42 (4086) [INFO] 
* 2023-05-30 03:08:42 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-30 03:08:42 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-30 03:08:42 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-30 03:08:42 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-30 03:08:42 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-30 03:08:42 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-30 03:08:42 (4116) [INFO] 
* 2023-05-30 03:08:42 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-30 03:08:42 (4086) [INFO] 
* 2023-05-30 03:08:59 (4099) [INFO] 
* 2023-05-30 03:08:59 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-30 03:08:59 (4116) [INFO] 
* 2023-05-30 03:08:59 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-30 03:08:59 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-30 03:13:17 (1565) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-05-30 03:13:17 (1566) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/cc74aba667fb92daf851201fc62a3b857f025af3a1d73f8bf8d2280f91f8c817-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-05-30 03:13:17 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-05-30 03:13:17 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-30 03:13:17 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JGiZNtsEzO/ea_profile.json
* 2023-05-30 03:13:22 (2258) [INFO] Backed up EA4 profile to /tmp/JGiZNtsEzO/ea_profile.json
* 2023-05-30 03:13:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-05-31 03:13:14 (315) [INFO] Successfully verified signature for cpanel (key types: release).
* 2023-05-31 03:13:14 (1699) [INFO] Checking if your system is up to date: 
* 2023-05-31 03:13:14 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-05-31 03:13:14 (4086) [INFO] 
* 2023-05-31 03:13:14 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-05-31 03:13:14 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-05-31 03:13:14 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-05-31 03:13:14 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-05-31 03:13:14 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-05-31 03:13:14 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-05-31 03:13:14 (4116) [INFO] 
* 2023-05-31 03:13:14 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-05-31 03:13:14 (4086) [INFO] 
* 2023-05-31 03:14:31 (4099) [INFO] 
* 2023-05-31 03:14:31 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-05-31 03:14:31 (4116) [INFO] 
* 2023-05-31 03:14:31 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-05-31 03:14:31 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-05-31 03:16:59 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-05-31 03:16:59 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QViDdT5yO_/ea_profile.json
* 2023-05-31 03:17:01 (2258) [INFO] Backed up EA4 profile to /tmp/QViDdT5yO_/ea_profile.json
* 2023-05-31 03:17:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-06-01 03:09:22 (1699) [INFO] Checking if your system is up to date: 
* 2023-06-01 03:09:22 (4085) [INFO] Running: /usr/bin/yum clean all
* 2023-06-01 03:09:22 (4086) [INFO] 
* 2023-06-01 03:09:22 (4099) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-01 03:09:22 (4099) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-01 03:09:22 (4099) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-01 03:09:22 (4099) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-01 03:09:22 (4099) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-01 03:09:22 (4099) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-01 03:09:22 (4116) [INFO] 
* 2023-06-01 03:09:22 (4085) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-01 03:09:22 (4086) [INFO] 
* 2023-06-01 03:09:50 (4099) [INFO] 
* 2023-06-01 03:09:50 (4099) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-01 03:09:50 (4116) [INFO] 
* 2023-06-01 03:09:50 (1706) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-01 03:09:50 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-01 03:10:44 (777) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-01 03:10:44 (2235) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/U5TCcL94SN/ea_profile.json
* 2023-06-01 03:10:45 (2258) [INFO] Backed up EA4 profile to /tmp/U5TCcL94SN/ea_profile.json
* 2023-06-01 03:10:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
* 2023-06-02 03:08:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-02 03:08:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-02 03:08:45 (4089) [INFO] 
* 2023-06-02 03:08:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-02 03:08:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-02 03:08:46 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-02 03:08:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-02 03:08:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-02 03:08:46 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-02 03:08:46 (4119) [INFO] 
* 2023-06-02 03:08:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-02 03:08:46 (4089) [INFO] 
* 2023-06-02 03:09:01 (4102) [INFO] 
* 2023-06-02 03:09:01 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-02 03:09:01 (4119) [INFO] 
* 2023-06-02 03:09:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-02 03:09:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-02 03:09:40 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-02 03:09:40 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PPiJprDVIz/ea_profile.json
* 2023-06-02 03:09:40 (2259) [INFO] Backed up EA4 profile to /tmp/PPiJprDVIz/ea_profile.json
* 2023-06-02 03:09:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-03 03:09:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-03 03:09:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-03 03:09:34 (4089) [INFO] 
* 2023-06-03 03:09:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-03 03:09:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-03 03:09:34 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-03 03:09:34 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-03 03:09:34 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-03 03:09:34 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-03 03:09:34 (4119) [INFO] 
* 2023-06-03 03:09:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-03 03:09:34 (4089) [INFO] 
* 2023-06-03 03:12:34 (4102) [INFO] 
* 2023-06-03 03:12:34 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-03 03:12:34 (4119) [INFO] 
* 2023-06-03 03:12:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-03 03:12:34 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-03 03:16:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-03 03:16:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2AdyVX5vZj/ea_profile.json
* 2023-06-03 03:16:12 (2259) [INFO] Backed up EA4 profile to /tmp/2AdyVX5vZj/ea_profile.json
* 2023-06-03 03:16:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-04 03:09:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-04 03:09:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-04 03:09:34 (4089) [INFO] 
* 2023-06-04 03:09:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-04 03:09:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-04 03:09:35 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-04 03:09:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-04 03:09:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-04 03:09:35 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-04 03:09:35 (4119) [INFO] 
* 2023-06-04 03:09:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-04 03:09:35 (4089) [INFO] 
* 2023-06-04 03:09:53 (4102) [INFO] 
* 2023-06-04 03:09:53 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-04 03:09:53 (4119) [INFO] 
* 2023-06-04 03:09:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-04 03:09:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-04 03:10:16 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-04 03:10:16 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0Q8FTwPqkq/ea_profile.json
* 2023-06-04 03:10:17 (2259) [INFO] Backed up EA4 profile to /tmp/0Q8FTwPqkq/ea_profile.json
* 2023-06-04 03:10:18 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-05 03:08:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-05 03:08:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-05 03:08:40 (4089) [INFO] 
* 2023-06-05 03:08:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-05 03:08:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-05 03:08:40 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-05 03:08:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-05 03:08:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-05 03:08:40 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-05 03:08:40 (4119) [INFO] 
* 2023-06-05 03:08:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-05 03:08:40 (4089) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-06-05 03:09:11 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-06-05 03:09:11 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-06-05 03:09:11 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-06-05 03:09:11 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-06-05 03:09:11 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-06-05 03:09:11 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-06-05 03:09:11 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-06-05 03:09:11 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-06-05 03:09:11 (4102) [INFO]         or
* 2023-06-05 03:09:11 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-06-05 03:09:11 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-06-05 03:09:11 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-06-05 03:09:11 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-06-05 03:09:11 (4102) [INFO]         compromise:
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-06-05 03:09:11 (4102) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-06-05 03:09:11 (4119) [INFO] 
* 2023-06-05 03:09:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-05 03:09:11 (1721) [INFO] Checking /scripts/sysup
* 2023-06-05 03:09:11 (4088) [INFO] Running: /scripts/sysup
* 2023-06-05 03:09:11 (4089) [INFO] 
* 2023-06-05 03:09:11 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-06-05 03:09:12 (4102) [INFO]   All Needed Packages are already installed.
* 2023-06-05 03:09:12 (4119) [INFO] 
* 2023-06-05 03:15:16 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-05 03:15:16 (1567) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 11058.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  26 M RSS (421 MB VSZ)
    Started: Mon Jun  5 03:09:07 2023 - 00:05 ago
    State  : Sleeping, pid: 11058
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  27 M RSS (421 MB VSZ)
    Started: Mon Jun  5 03:09:07 2023 - 00:07 ago
    State  : Sleeping, pid: 11058
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  29 M RSS (427 MB VSZ)
    Started: Mon Jun  5 03:09:07 2023 - 00:09 ago
    State  : Sleeping, pid: 11058
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  30 M RSS (427 MB VSZ)
    Started: Mon Jun  5 03:09:07 2023 - 00:11 ago
    State  : Sleeping, pid: 11058
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (433 MB VSZ)
    Started: Mon Jun  5 03:09:07 2023 - 00:13 ago
    State  : Running, pid: 11058
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (433 MB VSZ)
    Started: Mon Jun  5 03:09:07 2023 - 00:15 ago
    State  : Running, pid: 11058
* 2023-06-05 03:15:16 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-05 03:15:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-05 03:15:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LdbGdYaT1A/ea_profile.json
* 2023-06-05 03:15:18 (2259) [INFO] Backed up EA4 profile to /tmp/LdbGdYaT1A/ea_profile.json
* 2023-06-05 03:15:19 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-06 03:11:04 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-06 03:11:04 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-06 03:11:04 (4089) [INFO] 
* 2023-06-06 03:11:04 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-06 03:11:04 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-06 03:11:04 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-06 03:11:04 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-06 03:11:04 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-06 03:11:04 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-06 03:11:04 (4119) [INFO] 
* 2023-06-06 03:11:04 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-06 03:11:04 (4089) [INFO] 
* 2023-06-06 03:11:34 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-06-06 03:11:34 (4102) [INFO] Trying other mirror.
* 2023-06-06 03:11:41 (4102) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-06-06 03:11:41 (4102) [INFO] Trying other mirror.
* 2023-06-06 03:11:44 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-06 03:11:44 (4102) [INFO] Trying other mirror.
* 2023-06-06 03:13:54 (4102) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-06-06 03:13:54 (4102) [INFO] Trying other mirror.
* 2023-06-06 03:13:56 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-06 03:13:56 (4102) [INFO] Trying other mirror.
* 2023-06-06 03:14:02 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-06-06 03:14:02 (4102) [INFO] Trying other mirror.
* 2023-06-06 03:14:11 (4102) [INFO] 
* 2023-06-06 03:14:11 (4102) [INFO] ai-bolit.x86_64                    1:31.18.0-1.el7          imunify360          
* 2023-06-06 03:14:11 (4102) [INFO] alt-sqlite.x86_64                  3.39.4-1.el7             imunify360-rollout-8
* 2023-06-06 03:14:11 (4102) [INFO] imunify-antivirus.noarch           7.1.3-1                  imunify360          
* 2023-06-06 03:14:11 (4102) [INFO] imunify-antivirus-cpanel.noarch    7.1.3-1                  imunify360          
* 2023-06-06 03:14:11 (4102) [INFO] imunify-common.x86_64              1.2.4-2.el7              imunify360          
* 2023-06-06 03:14:11 (4102) [INFO] imunify360-venv.x86_64             2.1.0-1                  imunify360          
* 2023-06-06 03:14:11 (4102) [INFO] kernel.x86_64                      3.10.0-1160.90.1.el7     updates             
* 2023-06-06 03:14:11 (4119) [INFO] 
* 2023-06-06 03:14:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-06 03:14:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-06 03:17:37 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-06 03:17:37 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
* 2023-06-06 03:17:37 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-06 03:17:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-06 03:17:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sKGv1YaQ1j/ea_profile.json
* 2023-06-06 03:17:39 (2259) [INFO] Backed up EA4 profile to /tmp/sKGv1YaQ1j/ea_profile.json
* 2023-06-06 03:17:40 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-07 03:08:55 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-07 03:08:55 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-07 03:08:55 (4089) [INFO] 
* 2023-06-07 03:08:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-07 03:08:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-07 03:08:55 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-07 03:08:55 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-07 03:08:55 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-07 03:08:55 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-07 03:08:55 (4119) [INFO] 
* 2023-06-07 03:08:55 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-07 03:08:55 (4089) [INFO] 
* 2023-06-07 03:09:08 (4102) [INFO] 
* 2023-06-07 03:09:08 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-07 03:09:08 (4119) [INFO] 
* 2023-06-07 03:09:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-07 03:09:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-07 03:09:36 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-07 03:09:36 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/c3ysP0X5Df/ea_profile.json
* 2023-06-07 03:09:37 (2259) [INFO] Backed up EA4 profile to /tmp/c3ysP0X5Df/ea_profile.json
* 2023-06-07 03:09:38 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-08 03:09:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-08 03:09:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-08 03:09:28 (4089) [INFO] 
* 2023-06-08 03:09:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-08 03:09:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-08 03:09:28 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-08 03:09:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-08 03:09:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-08 03:09:28 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-08 03:09:28 (4119) [INFO] 
* 2023-06-08 03:09:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-08 03:09:28 (4089) [INFO] 
* 2023-06-08 03:09:41 (4102) [INFO] 
* 2023-06-08 03:09:41 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-08 03:09:41 (4119) [INFO] 
* 2023-06-08 03:09:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-08 03:09:41 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-08 03:09:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-08 03:09:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CewSRxFDkc/ea_profile.json
* 2023-06-08 03:09:55 (2259) [INFO] Backed up EA4 profile to /tmp/CewSRxFDkc/ea_profile.json
* 2023-06-08 03:09:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-09 03:08:29 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-09 03:08:29 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-09 03:08:29 (4089) [INFO] 
* 2023-06-09 03:08:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-09 03:08:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-09 03:08:29 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-09 03:08:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-09 03:08:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-09 03:08:29 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-09 03:08:29 (4119) [INFO] 
* 2023-06-09 03:08:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-09 03:08:29 (4089) [INFO] 
* 2023-06-09 03:08:44 (4102) [INFO] 
* 2023-06-09 03:08:44 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-09 03:08:44 (4119) [INFO] 
* 2023-06-09 03:08:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-09 03:08:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-09 03:09:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-09 03:09:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xd0dy40rDE/ea_profile.json
* 2023-06-09 03:09:10 (2259) [INFO] Backed up EA4 profile to /tmp/xd0dy40rDE/ea_profile.json
* 2023-06-09 03:09:11 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-10 03:09:18 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-10 03:09:18 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-10 03:09:18 (4089) [INFO] 
* 2023-06-10 03:09:18 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-10 03:09:18 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-10 03:09:18 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-10 03:09:18 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-10 03:09:18 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-10 03:09:18 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-10 03:09:18 (4119) [INFO] 
* 2023-06-10 03:09:18 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-10 03:09:18 (4089) [INFO] 
* 2023-06-10 03:09:36 (4102) [INFO] 
* 2023-06-10 03:09:36 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-10 03:09:36 (4119) [INFO] 
* 2023-06-10 03:09:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-10 03:09:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-10 03:09:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-10 03:09:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Kjgd0mYkt4/ea_profile.json
* 2023-06-10 03:09:51 (2259) [INFO] Backed up EA4 profile to /tmp/Kjgd0mYkt4/ea_profile.json
* 2023-06-10 03:09:52 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-11 03:09:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-11 03:09:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-11 03:09:25 (4089) [INFO] 
* 2023-06-11 03:09:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-11 03:09:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-11 03:09:26 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-11 03:09:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-11 03:09:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-11 03:09:26 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-11 03:09:26 (4119) [INFO] 
* 2023-06-11 03:09:26 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-11 03:09:26 (4089) [INFO] 
* 2023-06-11 03:09:40 (4102) [INFO] 
* 2023-06-11 03:09:40 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-11 03:09:40 (4119) [INFO] 
* 2023-06-11 03:09:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-11 03:09:40 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-11 03:09:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-11 03:09:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gmx1zT8PeQ/ea_profile.json
* 2023-06-11 03:09:56 (2259) [INFO] Backed up EA4 profile to /tmp/gmx1zT8PeQ/ea_profile.json
* 2023-06-11 03:09:57 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-12 03:08:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-12 03:08:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-12 03:08:31 (4089) [INFO] 
* 2023-06-12 03:08:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-12 03:08:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-12 03:08:31 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-12 03:08:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-12 03:08:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-12 03:08:31 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-12 03:08:32 (4119) [INFO] 
* 2023-06-12 03:08:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-12 03:08:32 (4089) [INFO] 
* 2023-06-12 03:08:44 (4102) [INFO] 
* 2023-06-12 03:08:44 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-12 03:08:44 (4119) [INFO] 
* 2023-06-12 03:08:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-12 03:08:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-12 03:08:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-12 03:08:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8Kiq6P6YFM/ea_profile.json
* 2023-06-12 03:08:59 (2259) [INFO] Backed up EA4 profile to /tmp/8Kiq6P6YFM/ea_profile.json
* 2023-06-12 03:09:00 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-13 03:08:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-13 03:08:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-13 03:08:40 (4089) [INFO] 
* 2023-06-13 03:08:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-13 03:08:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-13 03:08:40 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-13 03:08:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-13 03:08:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-13 03:08:40 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-13 03:08:40 (4119) [INFO] 
* 2023-06-13 03:08:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-13 03:08:40 (4089) [INFO] 
* 2023-06-13 03:08:55 (4102) [INFO] 
* 2023-06-13 03:08:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-13 03:08:55 (4119) [INFO] 
* 2023-06-13 03:08:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-13 03:08:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-13 03:09:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-13 03:09:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h8dJV8uDFm/ea_profile.json
* 2023-06-13 03:09:12 (2259) [INFO] Backed up EA4 profile to /tmp/h8dJV8uDFm/ea_profile.json
* 2023-06-13 03:09:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-14 03:08:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-14 03:08:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-14 03:08:39 (4089) [INFO] 
* 2023-06-14 03:08:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-14 03:08:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-14 03:08:40 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-14 03:08:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-14 03:08:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-14 03:08:40 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-14 03:08:40 (4119) [INFO] 
* 2023-06-14 03:08:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-14 03:08:40 (4089) [INFO] 
* 2023-06-14 03:08:54 (4102) [INFO] 
* 2023-06-14 03:08:54 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-14 03:08:54 (4119) [INFO] 
* 2023-06-14 03:08:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-14 03:08:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-14 03:09:09 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-14 03:09:09 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fSzUc6nckC/ea_profile.json
* 2023-06-14 03:09:10 (2259) [INFO] Backed up EA4 profile to /tmp/fSzUc6nckC/ea_profile.json
* 2023-06-14 03:09:11 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-15 03:09:14 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-15 03:09:14 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-15 03:09:14 (4089) [INFO] 
* 2023-06-15 03:09:14 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-15 03:09:14 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-15 03:09:14 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-15 03:09:14 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-15 03:09:14 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-15 03:09:14 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-15 03:09:14 (4119) [INFO] 
* 2023-06-15 03:09:14 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-15 03:09:14 (4089) [INFO] 
* 2023-06-15 03:09:53 (4102) [INFO] 
* 2023-06-15 03:09:53 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-15 03:09:53 (4119) [INFO] 
* 2023-06-15 03:09:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-15 03:09:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-15 03:10:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-15 03:10:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3gjman7f8r/ea_profile.json
* 2023-06-15 03:10:09 (2259) [INFO] Backed up EA4 profile to /tmp/3gjman7f8r/ea_profile.json
* 2023-06-15 03:10:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-16 03:08:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-16 03:08:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-16 03:08:40 (4089) [INFO] 
* 2023-06-16 03:08:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-16 03:08:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-16 03:08:40 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-16 03:08:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-16 03:08:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-16 03:08:40 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-16 03:08:40 (4119) [INFO] 
* 2023-06-16 03:08:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-16 03:08:40 (4089) [INFO] 
* 2023-06-16 03:08:55 (4102) [INFO] 
* 2023-06-16 03:08:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-16 03:08:55 (4119) [INFO] 
* 2023-06-16 03:08:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-16 03:08:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-16 03:09:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-16 03:09:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bMBI9C2XMS/ea_profile.json
* 2023-06-16 03:09:18 (2259) [INFO] Backed up EA4 profile to /tmp/bMBI9C2XMS/ea_profile.json
* 2023-06-16 03:09:19 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-17 03:09:19 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-17 03:09:19 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-17 03:09:19 (4089) [INFO] 
* 2023-06-17 03:09:19 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-17 03:09:19 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-17 03:09:19 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-17 03:09:19 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-17 03:09:19 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-17 03:09:19 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-17 03:09:19 (4119) [INFO] 
* 2023-06-17 03:09:19 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-17 03:09:19 (4089) [INFO] 
* 2023-06-17 03:09:26 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-17 03:09:26 (4102) [INFO] Trying other mirror.
* 2023-06-17 03:09:33 (4102) [INFO] 
* 2023-06-17 03:09:33 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-17 03:09:33 (4119) [INFO] 
* 2023-06-17 03:09:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-17 03:09:33 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-17 03:09:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-17 03:09:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Eu4NtQV0eF/ea_profile.json
* 2023-06-17 03:09:47 (2259) [INFO] Backed up EA4 profile to /tmp/Eu4NtQV0eF/ea_profile.json
* 2023-06-17 03:09:48 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-18 03:09:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-18 03:09:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-18 03:09:35 (4089) [INFO] 
* 2023-06-18 03:09:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-18 03:09:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-18 03:09:35 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-18 03:09:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-18 03:09:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-18 03:09:35 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-18 03:09:35 (4119) [INFO] 
* 2023-06-18 03:09:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-18 03:09:35 (4089) [INFO] 
* 2023-06-18 03:09:50 (4102) [INFO] 
* 2023-06-18 03:09:50 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-18 03:09:51 (4119) [INFO] 
* 2023-06-18 03:09:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-18 03:09:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-18 03:10:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-18 03:10:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gZHipFCWSf/ea_profile.json
* 2023-06-18 03:10:06 (2259) [INFO] Backed up EA4 profile to /tmp/gZHipFCWSf/ea_profile.json
* 2023-06-18 03:10:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-19 03:08:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-19 03:08:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-19 03:08:37 (4089) [INFO] 
* 2023-06-19 03:08:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-19 03:08:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-19 03:08:37 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-19 03:08:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-19 03:08:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-19 03:08:37 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-19 03:08:37 (4119) [INFO] 
* 2023-06-19 03:08:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-19 03:08:37 (4089) [INFO] 
* 2023-06-19 03:08:52 (4102) [INFO] 
* 2023-06-19 03:08:52 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-19 03:08:52 (4119) [INFO] 
* 2023-06-19 03:08:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-19 03:08:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-19 03:09:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-19 03:09:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xcYHyl2JUs/ea_profile.json
* 2023-06-19 03:09:07 (2259) [INFO] Backed up EA4 profile to /tmp/xcYHyl2JUs/ea_profile.json
* 2023-06-19 03:09:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-20 03:08:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-20 03:08:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-20 03:08:37 (4089) [INFO] 
* 2023-06-20 03:08:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-20 03:08:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-20 03:08:37 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-20 03:08:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-20 03:08:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-20 03:08:37 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-20 03:08:37 (4119) [INFO] 
* 2023-06-20 03:08:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-20 03:08:37 (4089) [INFO] 
* 2023-06-20 03:08:53 (4102) [INFO] 
* 2023-06-20 03:08:53 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-20 03:08:53 (4119) [INFO] 
* 2023-06-20 03:08:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-20 03:08:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-20 03:09:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-20 03:09:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4ywpLWfg_z/ea_profile.json
* 2023-06-20 03:09:11 (2259) [INFO] Backed up EA4 profile to /tmp/4ywpLWfg_z/ea_profile.json
* 2023-06-20 03:09:12 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-21 03:08:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-21 03:08:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-21 03:08:40 (4089) [INFO] 
* 2023-06-21 03:08:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-21 03:08:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-21 03:08:40 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-21 03:08:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-21 03:08:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-21 03:08:40 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-21 03:08:40 (4119) [INFO] 
* 2023-06-21 03:08:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-21 03:08:40 (4089) [INFO] 
* 2023-06-21 03:08:55 (4102) [INFO] 
* 2023-06-21 03:08:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-21 03:08:55 (4119) [INFO] 
* 2023-06-21 03:08:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-21 03:08:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-21 03:09:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-21 03:09:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tAR5xvUeUI/ea_profile.json
* 2023-06-21 03:09:15 (2259) [INFO] Backed up EA4 profile to /tmp/tAR5xvUeUI/ea_profile.json
* 2023-06-21 03:09:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-22 03:08:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-22 03:08:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-22 03:08:41 (4089) [INFO] 
* 2023-06-22 03:08:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-22 03:08:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-22 03:08:42 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-22 03:08:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-22 03:08:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-22 03:08:42 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-22 03:08:42 (4119) [INFO] 
* 2023-06-22 03:08:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-22 03:08:42 (4089) [INFO] 
* 2023-06-22 03:08:57 (4102) [INFO] 
* 2023-06-22 03:08:57 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-22 03:08:57 (4119) [INFO] 
* 2023-06-22 03:08:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-22 03:08:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-22 03:09:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-22 03:09:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/as7H_NZqtk/ea_profile.json
* 2023-06-22 03:09:14 (2259) [INFO] Backed up EA4 profile to /tmp/as7H_NZqtk/ea_profile.json
* 2023-06-22 03:09:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-23 03:08:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-23 03:08:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-23 03:08:40 (4089) [INFO] 
* 2023-06-23 03:08:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-23 03:08:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-23 03:08:41 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-23 03:08:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-23 03:08:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-23 03:08:41 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-23 03:08:41 (4119) [INFO] 
* 2023-06-23 03:08:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-23 03:08:41 (4089) [INFO] 
* 2023-06-23 03:08:57 (4102) [INFO] 
* 2023-06-23 03:08:57 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-23 03:08:57 (4119) [INFO] 
* 2023-06-23 03:08:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-23 03:08:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-23 03:09:30 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-23 03:09:30 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/3881dd080c8251b98492160a0bbce000c1dcf0e9405d6fdcf064b66419817933-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-06-23 03:09:30 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-23 03:09:31 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-23 03:09:31 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/x4S0YJwCrE/ea_profile.json
* 2023-06-23 03:09:32 (2259) [INFO] Backed up EA4 profile to /tmp/x4S0YJwCrE/ea_profile.json
* 2023-06-23 03:09:33 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-24 03:09:26 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-24 03:09:26 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-24 03:09:26 (4089) [INFO] 
* 2023-06-24 03:09:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-24 03:09:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-24 03:09:26 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-24 03:09:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-24 03:09:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-24 03:09:26 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-24 03:09:26 (4119) [INFO] 
* 2023-06-24 03:09:26 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-24 03:09:26 (4089) [INFO] 
* 2023-06-24 03:09:40 (4102) [INFO] 
* 2023-06-24 03:09:40 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-24 03:09:40 (4119) [INFO] 
* 2023-06-24 03:09:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-24 03:09:40 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-24 03:09:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-24 03:09:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4QgX7yZS17/ea_profile.json
* 2023-06-24 03:09:55 (2259) [INFO] Backed up EA4 profile to /tmp/4QgX7yZS17/ea_profile.json
* 2023-06-24 03:09:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-25 03:09:14 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-25 03:09:14 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-25 03:09:14 (4089) [INFO] 
* 2023-06-25 03:09:14 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-25 03:09:14 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-25 03:09:14 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-25 03:09:14 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-25 03:09:14 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-25 03:09:14 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-25 03:09:15 (4119) [INFO] 
* 2023-06-25 03:09:15 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-25 03:09:15 (4089) [INFO] 
* 2023-06-25 03:09:31 (4102) [INFO] 
* 2023-06-25 03:09:31 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-25 03:09:32 (4119) [INFO] 
* 2023-06-25 03:09:32 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-25 03:09:32 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-25 03:09:47 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-25 03:09:47 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IywNDcABZK/ea_profile.json
* 2023-06-25 03:09:48 (2259) [INFO] Backed up EA4 profile to /tmp/IywNDcABZK/ea_profile.json
* 2023-06-25 03:09:50 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-26 03:08:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-26 03:08:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-26 03:08:41 (4089) [INFO] 
* 2023-06-26 03:08:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-26 03:08:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-26 03:08:41 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-26 03:08:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-26 03:08:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-26 03:08:41 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-26 03:08:41 (4119) [INFO] 
* 2023-06-26 03:08:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-26 03:08:41 (4089) [INFO] 
* 2023-06-26 03:08:56 (4102) [INFO] 
* 2023-06-26 03:08:56 (4102) [INFO] kernel.x86_64                    3.10.0-1160.90.1.el7                    updates
* 2023-06-26 03:08:56 (4119) [INFO] 
* 2023-06-26 03:08:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-26 03:08:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-26 03:09:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-26 03:09:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yzZRNDLFaL/ea_profile.json
* 2023-06-26 03:09:13 (2259) [INFO] Backed up EA4 profile to /tmp/yzZRNDLFaL/ea_profile.json
* 2023-06-26 03:09:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-27 03:09:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-27 03:09:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-27 03:09:28 (4089) [INFO] 
* 2023-06-27 03:09:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-27 03:09:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-27 03:09:28 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-27 03:09:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-27 03:09:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-27 03:09:28 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-27 03:09:28 (4119) [INFO] 
* 2023-06-27 03:09:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-27 03:09:28 (4089) [INFO] 
* 2023-06-27 03:09:47 (4102) [INFO] 
* 2023-06-27 03:09:47 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-27 03:09:47 (4119) [INFO] 
* 2023-06-27 03:09:47 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-27 03:09:47 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-27 03:10:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-27 03:10:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TmF3myTGDn/ea_profile.json
* 2023-06-27 03:10:03 (2259) [INFO] Backed up EA4 profile to /tmp/TmF3myTGDn/ea_profile.json
* 2023-06-27 03:10:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-28 03:08:53 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-28 03:08:53 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-28 03:08:53 (4089) [INFO] 
* 2023-06-28 03:08:54 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-28 03:08:54 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-28 03:08:54 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-28 03:08:54 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-28 03:08:54 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-28 03:08:54 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-28 03:08:54 (4119) [INFO] 
* 2023-06-28 03:08:54 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-28 03:08:54 (4089) [INFO] 
* 2023-06-28 03:09:17 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:17 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:17 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:17 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:19 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/50508a89c36c0f4f5a14ce4e91781eea2f52f4a6a0dc805f63b86ee1935b1f19-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:19 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:19 (4102) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:19 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:20 (4102) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:20 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:20 (4102) [INFO] http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:20 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:21 (4102) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.4/wp-toolkit/repodata/01f02c80f93b01d457f5ca5238d64188b82f25a55400e564d16bb72db6e920cb-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:21 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:21 (4102) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.4/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:21 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:23 (4102) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:23 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:24 (4102) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:24 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:28 (4102) [INFO] http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:28 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:29 (4102) [INFO] http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:29 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:29 (4102) [INFO] http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/9c9b54f72dae654500c733a1e2c71b246baac88f156b684c7839eda3cc20ed6e-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:29 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:32 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/99b7754be47269d60956e5ccc14888412d79fe7545bdeb8db22450b33b8195f7-primary.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/99b7754be47269d60956e5ccc14888412d79fe7545bdeb8db22450b33b8195f7-primary.sqlite.bz2: (28, 'Connection timed out after 30000 milliseconds')
* 2023-06-28 03:09:32 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:34 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 12] Timeout on https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: (28, 'Operation timed out after 30001 milliseconds with 0 out of 0 bytes received')
* 2023-06-28 03:09:34 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:34 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/99b7754be47269d60956e5ccc14888412d79fe7545bdeb8db22450b33b8195f7-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:34 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:36 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:36 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:39 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/50508a89c36c0f4f5a14ce4e91781eea2f52f4a6a0dc805f63b86ee1935b1f19-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:39 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:49 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:49 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:51 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:51 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:54 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/50508a89c36c0f4f5a14ce4e91781eea2f52f4a6a0dc805f63b86ee1935b1f19-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-28 03:09:54 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:55 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:55 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:09:59 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/50508a89c36c0f4f5a14ce4e91781eea2f52f4a6a0dc805f63b86ee1935b1f19-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:09:59 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:10:00 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-28 03:10:00 (4102) [INFO] Trying other mirror.
* 2023-06-28 03:10:02 (4102) [INFO] 
* 2023-06-28 03:10:02 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-28 03:10:02 (4119) [INFO] 
* 2023-06-28 03:10:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-28 03:10:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-28 03:10:49 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-06-28 03:10:49 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-06-28 03:10:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-06-28 03:10:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-28 03:10:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/13X_ZnnQ6W/ea_profile.json
* 2023-06-28 03:10:50 (2259) [INFO] Backed up EA4 profile to /tmp/13X_ZnnQ6W/ea_profile.json
* 2023-06-28 03:10:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-29 03:08:51 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-29 03:08:51 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-29 03:08:51 (4089) [INFO] 
* 2023-06-29 03:08:51 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-29 03:08:51 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-29 03:08:51 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-29 03:08:51 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-29 03:08:51 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-29 03:08:51 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-29 03:08:51 (4119) [INFO] 
* 2023-06-29 03:08:51 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-29 03:08:51 (4089) [INFO] 
* 2023-06-29 03:09:17 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-06-29 03:09:17 (4102) [INFO] Trying other mirror.
* 2023-06-29 03:09:31 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/99b7754be47269d60956e5ccc14888412d79fe7545bdeb8db22450b33b8195f7-primary.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/99b7754be47269d60956e5ccc14888412d79fe7545bdeb8db22450b33b8195f7-primary.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
* 2023-06-29 03:09:31 (4102) [INFO] Trying other mirror.
* 2023-06-29 03:09:32 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/99b7754be47269d60956e5ccc14888412d79fe7545bdeb8db22450b33b8195f7-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-06-29 03:09:32 (4102) [INFO] Trying other mirror.
* 2023-06-29 03:09:33 (4102) [INFO] 
* 2023-06-29 03:09:33 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-29 03:09:33 (4119) [INFO] 
* 2023-06-29 03:09:33 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-29 03:09:33 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-29 03:09:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-29 03:09:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pLYGT732p4/ea_profile.json
* 2023-06-29 03:09:57 (2259) [INFO] Backed up EA4 profile to /tmp/pLYGT732p4/ea_profile.json
* 2023-06-29 03:09:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-06-30 03:08:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-06-30 03:08:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-06-30 03:08:45 (4089) [INFO] 
* 2023-06-30 03:08:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-06-30 03:08:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-06-30 03:08:46 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-06-30 03:08:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-06-30 03:08:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-06-30 03:08:46 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-06-30 03:08:46 (4119) [INFO] 
* 2023-06-30 03:08:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-06-30 03:08:46 (4089) [INFO] 
* 2023-06-30 03:09:04 (4102) [INFO] 
* 2023-06-30 03:09:04 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-06-30 03:09:04 (4119) [INFO] 
* 2023-06-30 03:09:04 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-06-30 03:09:04 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-06-30 03:09:33 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-06-30 03:09:33 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zXIUUzSeHz/ea_profile.json
* 2023-06-30 03:09:34 (2259) [INFO] Backed up EA4 profile to /tmp/zXIUUzSeHz/ea_profile.json
* 2023-06-30 03:09:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-01 03:09:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-01 03:09:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-01 03:09:37 (4089) [INFO] 
* 2023-07-01 03:09:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-01 03:09:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-01 03:09:37 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-01 03:09:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-01 03:09:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-01 03:09:37 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-01 03:09:37 (4119) [INFO] 
* 2023-07-01 03:09:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-01 03:09:37 (4089) [INFO] 
* 2023-07-01 03:09:52 (4102) [INFO] 
* 2023-07-01 03:09:52 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-01 03:09:53 (4119) [INFO] 
* 2023-07-01 03:09:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-01 03:09:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-01 03:10:08 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-01 03:10:08 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ddKhw5mibt/ea_profile.json
* 2023-07-01 03:10:08 (2259) [INFO] Backed up EA4 profile to /tmp/ddKhw5mibt/ea_profile.json
* 2023-07-01 03:10:10 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-02 03:09:27 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-02 03:09:27 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-02 03:09:27 (4089) [INFO] 
* 2023-07-02 03:09:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-02 03:09:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-02 03:09:28 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-02 03:09:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-02 03:09:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-02 03:09:28 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-02 03:09:28 (4119) [INFO] 
* 2023-07-02 03:09:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-02 03:09:28 (4089) [INFO] 
* 2023-07-02 03:09:44 (4102) [INFO] 
* 2023-07-02 03:09:44 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-02 03:09:44 (4119) [INFO] 
* 2023-07-02 03:09:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-02 03:09:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-02 03:10:00 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-02 03:10:00 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/h_evsUJ8Vq/ea_profile.json
* 2023-07-02 03:10:01 (2259) [INFO] Backed up EA4 profile to /tmp/h_evsUJ8Vq/ea_profile.json
* 2023-07-02 03:10:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-03 03:08:47 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-03 03:08:47 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-03 03:08:47 (4089) [INFO] 
* 2023-07-03 03:08:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-03 03:08:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-03 03:08:47 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-03 03:08:47 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-03 03:08:47 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-03 03:08:47 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-03 03:08:47 (4119) [INFO] 
* 2023-07-03 03:08:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-03 03:08:47 (4089) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-07-03 03:09:25 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-03 03:09:25 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-03 03:09:25 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-03 03:09:25 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-03 03:09:25 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-03 03:09:25 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-03 03:09:25 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-03 03:09:25 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-07-03 03:09:25 (4102) [INFO]         or
* 2023-07-03 03:09:25 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-03 03:09:25 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-03 03:09:25 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-03 03:09:25 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-03 03:09:25 (4102) [INFO]         compromise:
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-07-03 03:09:25 (4102) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-07-03 03:09:25 (4119) [INFO] 
* 2023-07-03 03:09:25 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-03 03:09:25 (1721) [INFO] Checking /scripts/sysup
* 2023-07-03 03:09:25 (4088) [INFO] Running: /scripts/sysup
* 2023-07-03 03:09:25 (4089) [INFO] 
* 2023-07-03 03:09:25 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-07-03 03:09:26 (4102) [INFO]   All Needed Packages are already installed.
* 2023-07-03 03:09:26 (4119) [INFO] 
* 2023-07-03 03:09:52 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-03 03:09:52 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/M9Hfrl_gTt/ea_profile.json
* 2023-07-03 03:09:53 (2259) [INFO] Backed up EA4 profile to /tmp/M9Hfrl_gTt/ea_profile.json
* 2023-07-03 03:09:54 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-07-04 03:08:36 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-04 03:08:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-04 03:08:36 (4089) [INFO] 
* 2023-07-04 03:08:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-04 03:08:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-04 03:08:36 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-04 03:08:36 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-04 03:08:36 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-04 03:08:36 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-04 03:08:36 (4119) [INFO] 
* 2023-07-04 03:08:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-04 03:08:36 (4089) [INFO] 
* 2023-07-04 03:08:51 (4102) [INFO] 
* 2023-07-04 03:08:51 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-04 03:08:51 (4119) [INFO] 
* 2023-07-04 03:08:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-04 03:08:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-04 03:09:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-04 03:09:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UJ9aGzQrv_/ea_profile.json
* 2023-07-04 03:09:05 (2259) [INFO] Backed up EA4 profile to /tmp/UJ9aGzQrv_/ea_profile.json
* 2023-07-04 03:09:06 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-05 03:08:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-05 03:08:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-05 03:08:37 (4089) [INFO] 
* 2023-07-05 03:08:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-05 03:08:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-05 03:08:37 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-05 03:08:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-05 03:08:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-05 03:08:37 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-05 03:08:37 (4119) [INFO] 
* 2023-07-05 03:08:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-05 03:08:37 (4089) [INFO] 
* 2023-07-05 03:08:55 (4102) [INFO] 
* 2023-07-05 03:08:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-05 03:08:55 (4119) [INFO] 
* 2023-07-05 03:08:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-05 03:08:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-05 03:09:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-05 03:09:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jsWrh5xLmg/ea_profile.json
* 2023-07-05 03:09:13 (2259) [INFO] Backed up EA4 profile to /tmp/jsWrh5xLmg/ea_profile.json
* 2023-07-05 03:09:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-06 03:08:51 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-06 03:08:51 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-06 03:08:51 (4089) [INFO] 
* 2023-07-06 03:08:52 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-06 03:08:52 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-06 03:08:52 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-06 03:08:52 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-06 03:08:52 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-06 03:08:52 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-06 03:08:52 (4119) [INFO] 
* 2023-07-06 03:08:52 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-06 03:08:52 (4089) [INFO] 
* 2023-07-06 03:09:08 (4102) [INFO] 
* 2023-07-06 03:09:08 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-06 03:09:08 (4119) [INFO] 
* 2023-07-06 03:09:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-06 03:09:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-06 03:09:26 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-06 03:09:26 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fZxSdANfIu/ea_profile.json
* 2023-07-06 03:09:27 (2259) [INFO] Backed up EA4 profile to /tmp/fZxSdANfIu/ea_profile.json
* 2023-07-06 03:09:28 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-07 03:08:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-07 03:08:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-07 03:08:38 (4089) [INFO] 
* 2023-07-07 03:08:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-07 03:08:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-07 03:08:38 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-07 03:08:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-07 03:08:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-07 03:08:38 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-07 03:08:39 (4119) [INFO] 
* 2023-07-07 03:08:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-07 03:08:39 (4089) [INFO] 
* 2023-07-07 03:08:55 (4102) [INFO] 
* 2023-07-07 03:08:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-07 03:08:55 (4119) [INFO] 
* 2023-07-07 03:08:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-07 03:08:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-07 03:09:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-07 03:09:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HPSvPAQ2sJ/ea_profile.json
* 2023-07-07 03:09:12 (2259) [INFO] Backed up EA4 profile to /tmp/HPSvPAQ2sJ/ea_profile.json
* 2023-07-07 03:09:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-08 03:09:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-08 03:09:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-08 03:09:28 (4089) [INFO] 
* 2023-07-08 03:09:28 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-08 03:09:28 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-08 03:09:28 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-08 03:09:28 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-08 03:09:28 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-08 03:09:28 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-08 03:09:28 (4119) [INFO] 
* 2023-07-08 03:09:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-08 03:09:28 (4089) [INFO] 
* 2023-07-08 03:09:44 (4102) [INFO] 
* 2023-07-08 03:09:44 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-08 03:09:44 (4119) [INFO] 
* 2023-07-08 03:09:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-08 03:09:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-08 03:10:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-08 03:10:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ISjCGj5jXl/ea_profile.json
* 2023-07-08 03:10:03 (2259) [INFO] Backed up EA4 profile to /tmp/ISjCGj5jXl/ea_profile.json
* 2023-07-08 03:10:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-09 03:09:57 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-09 03:09:57 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-09 03:09:57 (4089) [INFO] 
* 2023-07-09 03:09:57 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-09 03:09:57 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-09 03:09:57 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-09 03:09:57 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-09 03:09:57 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-09 03:09:57 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-09 03:09:57 (4119) [INFO] 
* 2023-07-09 03:09:57 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-09 03:09:57 (4089) [INFO] 
* 2023-07-09 03:10:14 (4102) [INFO] 
* 2023-07-09 03:10:14 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-09 03:10:14 (4119) [INFO] 
* 2023-07-09 03:10:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-09 03:10:14 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-09 03:10:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-09 03:10:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zIxbvSgeN6/ea_profile.json
* 2023-07-09 03:10:38 (2259) [INFO] Backed up EA4 profile to /tmp/zIxbvSgeN6/ea_profile.json
* 2023-07-09 03:10:40 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-10 03:08:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-10 03:08:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-10 03:08:34 (4089) [INFO] 
* 2023-07-10 03:08:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-10 03:08:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-10 03:08:35 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-10 03:08:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-10 03:08:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-10 03:08:35 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-10 03:08:35 (4119) [INFO] 
* 2023-07-10 03:08:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-10 03:08:35 (4089) [INFO] 
* 2023-07-10 03:08:48 (4102) [INFO] 
* 2023-07-10 03:08:48 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-10 03:08:48 (4119) [INFO] 
* 2023-07-10 03:08:48 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-10 03:08:48 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-10 03:09:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-10 03:09:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/54X37VAMo0/ea_profile.json
* 2023-07-10 03:09:03 (2259) [INFO] Backed up EA4 profile to /tmp/54X37VAMo0/ea_profile.json
* 2023-07-10 03:09:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-11 03:08:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-11 03:08:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-11 03:08:46 (4089) [INFO] 
* 2023-07-11 03:08:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-11 03:08:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-11 03:08:47 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-11 03:08:47 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-11 03:08:47 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-11 03:08:47 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-11 03:08:47 (4119) [INFO] 
* 2023-07-11 03:08:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-11 03:08:47 (4089) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-07-11 03:09:12 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-11 03:09:12 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-11 03:09:12 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-11 03:09:12 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-11 03:09:12 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-11 03:09:12 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-11 03:09:12 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-11 03:09:12 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-07-11 03:09:12 (4102) [INFO]         or
* 2023-07-11 03:09:12 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-11 03:09:12 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-11 03:09:12 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-11 03:09:12 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-11 03:09:12 (4102) [INFO]         compromise:
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-07-11 03:09:12 (4102) [INFO] 
* 2023-07-11 03:09:12 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-07-11 03:09:12 (4119) [INFO] 
* 2023-07-11 03:09:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-11 03:09:12 (1721) [INFO] Checking /scripts/sysup
* 2023-07-11 03:09:12 (4088) [INFO] Running: /scripts/sysup
* 2023-07-11 03:09:12 (4089) [INFO] 
* 2023-07-11 03:09:13 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-07-11 03:09:13 (4102) [INFO]   All Needed Packages are already installed.
* 2023-07-11 03:09:13 (4119) [INFO] 
* 2023-07-11 03:09:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-11 03:09:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Hfi8sCprLk/ea_profile.json
* 2023-07-11 03:09:40 (2259) [INFO] Backed up EA4 profile to /tmp/Hfi8sCprLk/ea_profile.json
* 2023-07-11 03:09:41 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-07-12 03:08:53 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-12 03:08:53 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-12 03:08:53 (4089) [INFO] 
* 2023-07-12 03:08:53 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-12 03:08:53 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-12 03:08:53 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-12 03:08:53 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-12 03:08:53 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-12 03:08:53 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-12 03:08:53 (4119) [INFO] 
* 2023-07-12 03:08:53 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-12 03:08:53 (4089) [INFO] 
* 2023-07-12 03:09:16 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-07-12 03:09:16 (4102) [INFO] Trying other mirror.
* 2023-07-12 03:09:16 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/895321e655eb254e1b6a6809b589143a51c00c92b64ea36cefb469ec41bc7076-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-07-12 03:09:16 (4102) [INFO] Trying other mirror.
* 2023-07-12 03:09:16 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-07-12 03:09:16 (4102) [INFO] Trying other mirror.
* 2023-07-12 03:09:18 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-07-12 03:09:18 (4102) [INFO] Trying other mirror.
* 2023-07-12 03:09:18 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/895321e655eb254e1b6a6809b589143a51c00c92b64ea36cefb469ec41bc7076-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-07-12 03:09:18 (4102) [INFO] Trying other mirror.
* 2023-07-12 03:09:19 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-07-12 03:09:19 (4102) [INFO] Trying other mirror.
* 2023-07-12 03:09:20 (4102) [INFO] 
* 2023-07-12 03:09:20 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-12 03:09:20 (4119) [INFO] 
* 2023-07-12 03:09:20 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-12 03:09:20 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-12 03:09:39 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-12 03:09:39 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2LR_Xz9nZq/ea_profile.json
* 2023-07-12 03:09:40 (2259) [INFO] Backed up EA4 profile to /tmp/2LR_Xz9nZq/ea_profile.json
* 2023-07-12 03:09:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-13 03:09:29 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-13 03:09:29 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-13 03:09:29 (4089) [INFO] 
* 2023-07-13 03:09:29 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-13 03:09:29 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-13 03:09:29 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-13 03:09:29 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-13 03:09:29 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-13 03:09:29 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-13 03:09:29 (4119) [INFO] 
* 2023-07-13 03:09:29 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-13 03:09:29 (4089) [INFO] 
* 2023-07-13 03:09:49 (4102) [INFO] 
* 2023-07-13 03:09:49 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-13 03:09:49 (4119) [INFO] 
* 2023-07-13 03:09:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-13 03:09:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-13 03:10:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-13 03:10:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b9zXo4Ueqj/ea_profile.json
* 2023-07-13 03:10:07 (2259) [INFO] Backed up EA4 profile to /tmp/b9zXo4Ueqj/ea_profile.json
* 2023-07-13 03:10:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-14 03:09:19 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-14 03:09:19 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-14 03:09:19 (4089) [INFO] 
* 2023-07-14 03:09:19 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-14 03:09:19 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-14 03:09:19 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-14 03:09:19 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-14 03:09:19 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-14 03:09:19 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-14 03:09:19 (4119) [INFO] 
* 2023-07-14 03:09:19 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-14 03:09:19 (4089) [INFO] 
* 2023-07-14 03:09:35 (4102) [INFO] 
* 2023-07-14 03:09:35 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-14 03:09:35 (4119) [INFO] 
* 2023-07-14 03:09:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-14 03:09:35 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-14 03:09:51 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-14 03:09:51 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dpGk4enPtr/ea_profile.json
* 2023-07-14 03:09:52 (2259) [INFO] Backed up EA4 profile to /tmp/dpGk4enPtr/ea_profile.json
* 2023-07-14 03:09:53 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-15 03:09:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-15 03:09:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-15 03:09:23 (4089) [INFO] 
* 2023-07-15 03:09:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-15 03:09:23 (4102) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 17825.
* 2023-07-15 03:09:23 (4102) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-07-15 03:09:23 (4102) [INFO]   The other application is: yum
* 2023-07-15 03:09:23 (4102) [INFO]     Memory :  36 M RSS (3.3 GB VSZ)
* 2023-07-15 03:09:23 (4102) [INFO]     Started: Sat Jul 15 03:09:09 2023 - 00:14 ago
* 2023-07-15 03:09:23 (4102) [INFO]     State  : Running, pid: 17825
* 2023-07-15 03:09:25 (4102) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-07-15 03:09:25 (4102) [INFO]   The other application is: yum
* 2023-07-15 03:09:25 (4102) [INFO]     Memory :  77 M RSS (3.4 GB VSZ)
* 2023-07-15 03:09:25 (4102) [INFO]     Started: Sat Jul 15 03:09:09 2023 - 00:16 ago
* 2023-07-15 03:09:25 (4102) [INFO]     State  : Running, pid: 17825
* 2023-07-15 03:09:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-15 03:09:27 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-15 03:09:27 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-15 03:09:27 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-15 03:09:27 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-15 03:09:28 (4102) [INFO] Cleaning up list of fastest mirrors
* 2023-07-15 03:09:28 (4119) [INFO] 
* 2023-07-15 03:09:28 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-15 03:09:28 (4089) [INFO] 
* 2023-07-15 03:09:41 (4102) [INFO] 
* 2023-07-15 03:09:41 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-15 03:09:41 (4119) [INFO] 
* 2023-07-15 03:09:41 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-15 03:09:41 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-15 03:09:56 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-15 03:09:56 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FIaXwZBad0/ea_profile.json
* 2023-07-15 03:09:57 (2259) [INFO] Backed up EA4 profile to /tmp/FIaXwZBad0/ea_profile.json
* 2023-07-15 03:09:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-16 03:09:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-16 03:09:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-16 03:09:46 (4089) [INFO] 
* 2023-07-16 03:09:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-16 03:09:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-16 03:09:46 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-16 03:09:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-16 03:09:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-16 03:09:46 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-16 03:09:46 (4119) [INFO] 
* 2023-07-16 03:09:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-16 03:09:46 (4089) [INFO] 
* 2023-07-16 03:10:00 (4102) [INFO] 
* 2023-07-16 03:10:00 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-16 03:10:00 (4119) [INFO] 
* 2023-07-16 03:10:00 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-16 03:10:00 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-16 03:10:19 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-16 03:10:19 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OCxrEHHsjf/ea_profile.json
* 2023-07-16 03:10:20 (2259) [INFO] Backed up EA4 profile to /tmp/OCxrEHHsjf/ea_profile.json
* 2023-07-16 03:10:21 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-17 03:09:03 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-17 03:09:03 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-17 03:09:03 (4089) [INFO] 
* 2023-07-17 03:09:03 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-17 03:09:03 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-17 03:09:03 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-17 03:09:03 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-17 03:09:03 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-17 03:09:03 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-17 03:09:03 (4119) [INFO] 
* 2023-07-17 03:09:03 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-17 03:09:03 (4089) [INFO] 
* 2023-07-17 03:09:34 (4102) [INFO] 
* 2023-07-17 03:09:34 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-17 03:09:34 (4119) [INFO] 
* 2023-07-17 03:09:34 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-17 03:09:34 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-17 03:09:53 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-17 03:09:53 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8mwDwsGF64/ea_profile.json
* 2023-07-17 03:09:53 (2259) [INFO] Backed up EA4 profile to /tmp/8mwDwsGF64/ea_profile.json
* 2023-07-17 03:09:54 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-18 03:08:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-18 03:08:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-18 03:08:42 (4089) [INFO] 
* 2023-07-18 03:08:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-18 03:08:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-18 03:08:42 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-18 03:08:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-18 03:08:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-18 03:08:42 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-18 03:08:42 (4119) [INFO] 
* 2023-07-18 03:08:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-18 03:08:42 (4089) [INFO] 
* 2023-07-18 03:08:55 (4102) [INFO] 
* 2023-07-18 03:08:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-18 03:08:55 (4119) [INFO] 
* 2023-07-18 03:08:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-18 03:08:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-18 03:09:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-18 03:09:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Lro7A0wx6q/ea_profile.json
* 2023-07-18 03:09:11 (2259) [INFO] Backed up EA4 profile to /tmp/Lro7A0wx6q/ea_profile.json
* 2023-07-18 03:09:12 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-19 03:08:55 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-19 03:08:55 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-19 03:08:55 (4089) [INFO] 
* 2023-07-19 03:08:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-19 03:08:56 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-19 03:08:56 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-19 03:08:56 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-19 03:08:56 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-19 03:08:56 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-19 03:08:56 (4119) [INFO] 
* 2023-07-19 03:08:56 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-19 03:08:56 (4089) [INFO] 
* 2023-07-19 03:09:05 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/b771e72c0d096137a8289b0e5ef571f0ccf1be8512436b7ae881459d08975c6d-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-07-19 03:09:05 (4102) [INFO] Trying other mirror.
* 2023-07-19 03:09:16 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-07-19 03:09:16 (4102) [INFO] Trying other mirror.
* 2023-07-19 03:09:31 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-07-19 03:09:31 (4102) [INFO] Trying other mirror.
* 2023-07-19 03:09:34 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-07-19 03:09:34 (4102) [INFO] Trying other mirror.
* 2023-07-19 03:09:35 (4102) [INFO] 
* 2023-07-19 03:09:35 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-19 03:09:35 (4119) [INFO] 
* 2023-07-19 03:09:35 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-19 03:09:35 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-19 03:10:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-19 03:10:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4iiSwr6PwD/ea_profile.json
* 2023-07-19 03:10:02 (2259) [INFO] Backed up EA4 profile to /tmp/4iiSwr6PwD/ea_profile.json
* 2023-07-19 03:10:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-20 03:09:20 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-20 03:09:20 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-20 03:09:20 (4089) [INFO] 
* 2023-07-20 03:09:20 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-20 03:09:20 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-20 03:09:20 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-20 03:09:20 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-20 03:09:20 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-20 03:09:20 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-20 03:09:20 (4119) [INFO] 
* 2023-07-20 03:09:20 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-20 03:09:20 (4089) [INFO] 
* 2023-07-20 03:09:31 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-07-20 03:09:31 (4102) [INFO] Trying other mirror.
* 2023-07-20 03:09:36 (4102) [INFO] 
* 2023-07-20 03:09:36 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-20 03:09:36 (4119) [INFO] 
* 2023-07-20 03:09:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-20 03:09:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-20 03:09:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-20 03:09:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/V4kLBz8waF/ea_profile.json
* 2023-07-20 03:09:58 (2259) [INFO] Backed up EA4 profile to /tmp/V4kLBz8waF/ea_profile.json
* 2023-07-20 03:09:59 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-21 03:08:48 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-21 03:08:48 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-21 03:08:48 (4089) [INFO] 
* 2023-07-21 03:08:49 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-21 03:08:49 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-21 03:08:49 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-21 03:08:49 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-21 03:08:49 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-21 03:08:49 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-21 03:08:49 (4119) [INFO] 
* 2023-07-21 03:08:49 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-21 03:08:49 (4089) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-07-21 03:09:16 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-21 03:09:16 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-21 03:09:16 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-21 03:09:16 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-21 03:09:16 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-21 03:09:16 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-21 03:09:16 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-21 03:09:16 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-07-21 03:09:16 (4102) [INFO]         or
* 2023-07-21 03:09:16 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-21 03:09:16 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-21 03:09:16 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-21 03:09:16 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-21 03:09:16 (4102) [INFO]         compromise:
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-07-21 03:09:16 (4102) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-07-21 03:09:16 (4119) [INFO] 
* 2023-07-21 03:09:16 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-21 03:09:16 (1721) [INFO] Checking /scripts/sysup
* 2023-07-21 03:09:16 (4088) [INFO] Running: /scripts/sysup
* 2023-07-21 03:09:16 (4089) [INFO] 
* 2023-07-21 03:09:16 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-07-21 03:09:17 (4102) [INFO]   All Needed Packages are already installed.
* 2023-07-21 03:09:17 (4119) [INFO] 
* 2023-07-21 03:09:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-21 03:09:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pgeFwj8Ji2/ea_profile.json
* 2023-07-21 03:09:45 (2259) [INFO] Backed up EA4 profile to /tmp/pgeFwj8Ji2/ea_profile.json
* 2023-07-21 03:09:46 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-07-22 03:09:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-22 03:09:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-22 03:09:32 (4089) [INFO] 
* 2023-07-22 03:09:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-22 03:09:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-22 03:09:33 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-22 03:09:33 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-22 03:09:33 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-22 03:09:33 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-22 03:09:33 (4119) [INFO] 
* 2023-07-22 03:09:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-22 03:09:33 (4089) [INFO] 
* 2023-07-22 03:09:46 (4102) [INFO] 
* 2023-07-22 03:09:46 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-22 03:09:46 (4119) [INFO] 
* 2023-07-22 03:09:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-22 03:09:46 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-22 03:10:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-22 03:10:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/meJ_vr_RTx/ea_profile.json
* 2023-07-22 03:10:02 (2259) [INFO] Backed up EA4 profile to /tmp/meJ_vr_RTx/ea_profile.json
* 2023-07-22 03:10:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-23 03:09:34 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-23 03:09:34 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-23 03:09:34 (4089) [INFO] 
* 2023-07-23 03:09:34 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-23 03:09:34 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-23 03:09:34 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-23 03:09:34 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-23 03:09:34 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-23 03:09:34 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-23 03:09:34 (4119) [INFO] 
* 2023-07-23 03:09:34 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-23 03:09:34 (4089) [INFO] 
* 2023-07-23 03:09:49 (4102) [INFO] 
* 2023-07-23 03:09:49 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-23 03:09:49 (4119) [INFO] 
* 2023-07-23 03:09:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-23 03:09:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-23 03:10:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-23 03:10:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/k59CabGLxN/ea_profile.json
* 2023-07-23 03:10:05 (2259) [INFO] Backed up EA4 profile to /tmp/k59CabGLxN/ea_profile.json
* 2023-07-23 03:10:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-24 03:08:48 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-24 03:08:48 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-24 03:08:48 (4089) [INFO] 
* 2023-07-24 03:08:48 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-24 03:08:48 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-24 03:08:48 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-24 03:08:48 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-24 03:08:48 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-24 03:08:48 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-24 03:08:48 (4119) [INFO] 
* 2023-07-24 03:08:48 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-24 03:08:48 (4089) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-07-24 03:09:12 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-07-24 03:09:12 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-07-24 03:09:12 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-07-24 03:09:12 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-07-24 03:09:12 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-07-24 03:09:12 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-07-24 03:09:12 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-07-24 03:09:12 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-07-24 03:09:12 (4102) [INFO]         or
* 2023-07-24 03:09:12 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-07-24 03:09:12 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-07-24 03:09:12 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-07-24 03:09:12 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-07-24 03:09:12 (4102) [INFO]         compromise:
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-07-24 03:09:12 (4102) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-07-24 03:09:12 (4119) [INFO] 
* 2023-07-24 03:09:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-24 03:09:12 (1721) [INFO] Checking /scripts/sysup
* 2023-07-24 03:09:12 (4088) [INFO] Running: /scripts/sysup
* 2023-07-24 03:09:12 (4089) [INFO] 
* 2023-07-24 03:09:12 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-07-24 03:09:13 (4102) [INFO]   All Needed Packages are already installed.
* 2023-07-24 03:09:13 (4119) [INFO] 
* 2023-07-24 03:09:42 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-24 03:09:42 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BnFm2Q5WQ5/ea_profile.json
* 2023-07-24 03:09:42 (2259) [INFO] Backed up EA4 profile to /tmp/BnFm2Q5WQ5/ea_profile.json
* 2023-07-24 03:09:43 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-07-25 03:08:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-25 03:08:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-25 03:08:41 (4089) [INFO] 
* 2023-07-25 03:08:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-25 03:08:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-25 03:08:41 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-25 03:08:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-25 03:08:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-25 03:08:41 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-25 03:08:41 (4119) [INFO] 
* 2023-07-25 03:08:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-25 03:08:41 (4089) [INFO] 
* 2023-07-25 03:08:58 (4102) [INFO] 
* 2023-07-25 03:08:58 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-25 03:08:58 (4119) [INFO] 
* 2023-07-25 03:08:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-25 03:08:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-25 03:09:36 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-25 03:09:36 (1567) [ERROR] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-07-25 03:09:36 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-25 03:09:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-25 03:09:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/eJ_Z9u3HU0/ea_profile.json
* 2023-07-25 03:09:37 (2259) [INFO] Backed up EA4 profile to /tmp/eJ_Z9u3HU0/ea_profile.json
* 2023-07-25 03:09:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-26 03:08:51 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-26 03:08:51 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-26 03:08:51 (4089) [INFO] 
* 2023-07-26 03:08:51 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-26 03:08:51 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-26 03:08:51 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-26 03:08:51 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-26 03:08:51 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-26 03:08:51 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-26 03:08:51 (4119) [INFO] 
* 2023-07-26 03:08:51 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-26 03:08:51 (4089) [INFO] 
* 2023-07-26 03:09:08 (4102) [INFO] 
* 2023-07-26 03:09:08 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-26 03:09:08 (4119) [INFO] 
* 2023-07-26 03:09:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-26 03:09:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-26 03:09:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-26 03:09:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PFLp7BLuwM/ea_profile.json
* 2023-07-26 03:09:38 (2259) [INFO] Backed up EA4 profile to /tmp/PFLp7BLuwM/ea_profile.json
* 2023-07-26 03:09:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-27 03:08:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-27 03:08:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-27 03:08:41 (4089) [INFO] 
* 2023-07-27 03:08:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-27 03:08:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-27 03:08:42 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-27 03:08:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-27 03:08:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-27 03:08:42 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-27 03:08:42 (4119) [INFO] 
* 2023-07-27 03:08:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-27 03:08:42 (4089) [INFO] 
* 2023-07-27 03:08:58 (4102) [INFO] 
* 2023-07-27 03:08:58 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-27 03:08:58 (4119) [INFO] 
* 2023-07-27 03:08:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-27 03:08:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-27 03:09:43 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-07-27 03:09:44 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/6985e32a982ba50f9a6935c5bf897b3b3651ba4ba68eb4639e758e4385d15820-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/6985e32a982ba50f9a6935c5bf897b3b3651ba4ba68eb4639e758e4385d15820-other.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2023-07-27 03:09:44 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-07-27 03:09:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-27 03:09:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OAvIM_Xt_0/ea_profile.json
* 2023-07-27 03:09:45 (2259) [INFO] Backed up EA4 profile to /tmp/OAvIM_Xt_0/ea_profile.json
* 2023-07-27 03:09:46 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-28 03:09:07 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-28 03:09:07 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-28 03:09:07 (4089) [INFO] 
* 2023-07-28 03:09:07 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-28 03:09:08 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-28 03:09:08 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-28 03:09:08 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-28 03:09:08 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-28 03:09:08 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-28 03:09:08 (4119) [INFO] 
* 2023-07-28 03:09:08 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-28 03:09:08 (4089) [INFO] 
* 2023-07-28 03:09:29 (4102) [INFO] Traceback (most recent call last):
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-07-28 03:09:29 (4102) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-07-28 03:09:29 (4102) [INFO]     errcode = main(args)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-07-28 03:09:29 (4102) [INFO]     result, resultmsgs = base.doCommands()
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-07-28 03:09:29 (4102) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-07-28 03:09:29 (4102) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-07-28 03:09:29 (4102) [INFO]     ignore_case=True, repoid=repoid)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-07-28 03:09:29 (4102) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-07-28 03:09:29 (4102) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-07-28 03:09:29 (4102) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-07-28 03:09:29 (4102) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-07-28 03:09:29 (4102) [INFO]     self.repos.populateSack(which=repos)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack
* 2023-07-28 03:09:29 (4102) [INFO]     sack.populate(repo, mdtype, callback, cacheonly)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 242, in populate
* 2023-07-28 03:09:29 (4102) [INFO]     mydbtype)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-07-28 03:09:29 (4102) [INFO]     cached=repo.cache)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-07-28 03:09:29 (4102) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-07-28 03:09:29 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-07-28 03:09:29 (4102) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-07-28 03:09:29 (4102) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite'
* 2023-07-28 03:09:29 (4119) [INFO] 
* 2023-07-28 03:09:29 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-28 03:09:29 (1721) [INFO] Checking /scripts/sysup
* 2023-07-28 03:09:29 (4088) [INFO] Running: /scripts/sysup
* 2023-07-28 03:09:29 (4089) [INFO] 
* 2023-07-28 03:09:29 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-07-28 03:09:30 (4102) [INFO]   All Needed Packages are already installed.
* 2023-07-28 03:09:30 (4119) [INFO] 
* 2023-07-28 03:09:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-28 03:09:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/G1A4eFjLfj/ea_profile.json
* 2023-07-28 03:09:50 (2259) [INFO] Backed up EA4 profile to /tmp/G1A4eFjLfj/ea_profile.json
* 2023-07-28 03:09:51 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-07-29 03:09:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-29 03:09:35 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-29 03:09:35 (4089) [INFO] 
* 2023-07-29 03:09:35 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-29 03:09:35 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-29 03:09:35 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-29 03:09:35 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-29 03:09:35 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-29 03:09:35 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-29 03:09:35 (4119) [INFO] 
* 2023-07-29 03:09:35 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-29 03:09:35 (4089) [INFO] 
* 2023-07-29 03:09:49 (4102) [INFO] 
* 2023-07-29 03:09:49 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-29 03:09:49 (4119) [INFO] 
* 2023-07-29 03:09:49 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-29 03:09:49 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-29 03:10:06 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-29 03:10:06 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6qOG2gy7sE/ea_profile.json
* 2023-07-29 03:10:07 (2259) [INFO] Backed up EA4 profile to /tmp/6qOG2gy7sE/ea_profile.json
* 2023-07-29 03:10:08 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-30 03:09:30 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-30 03:09:30 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-30 03:09:30 (4089) [INFO] 
* 2023-07-30 03:09:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-30 03:09:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-30 03:09:31 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-30 03:09:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-30 03:09:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-30 03:09:31 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-30 03:09:31 (4119) [INFO] 
* 2023-07-30 03:09:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-30 03:09:31 (4089) [INFO] 
* 2023-07-30 03:09:45 (4102) [INFO] 
* 2023-07-30 03:09:45 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-30 03:09:45 (4119) [INFO] 
* 2023-07-30 03:09:45 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-30 03:09:45 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-30 03:10:04 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-30 03:10:04 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/X853f6mbyX/ea_profile.json
* 2023-07-30 03:10:05 (2259) [INFO] Backed up EA4 profile to /tmp/X853f6mbyX/ea_profile.json
* 2023-07-30 03:10:06 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-07-31 03:08:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-07-31 03:08:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-07-31 03:08:39 (4089) [INFO] 
* 2023-07-31 03:08:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-07-31 03:08:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-07-31 03:08:39 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-07-31 03:08:39 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-07-31 03:08:39 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-07-31 03:08:39 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-07-31 03:08:39 (4119) [INFO] 
* 2023-07-31 03:08:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-07-31 03:08:39 (4089) [INFO] 
* 2023-07-31 03:08:54 (4102) [INFO] 
* 2023-07-31 03:08:54 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-07-31 03:08:54 (4119) [INFO] 
* 2023-07-31 03:08:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-07-31 03:08:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-07-31 03:09:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-07-31 03:09:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kaDbYM1Hie/ea_profile.json
* 2023-07-31 03:09:12 (2259) [INFO] Backed up EA4 profile to /tmp/kaDbYM1Hie/ea_profile.json
* 2023-07-31 03:09:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-01 03:09:14 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-01 03:09:14 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-01 03:09:14 (4089) [INFO] 
* 2023-08-01 03:09:14 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-01 03:09:14 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-01 03:09:14 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-01 03:09:14 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-01 03:09:14 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-01 03:09:14 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-01 03:09:14 (4119) [INFO] 
* 2023-08-01 03:09:14 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-01 03:09:14 (4089) [INFO] 
* 2023-08-01 03:09:36 (4102) [INFO] 
* 2023-08-01 03:09:36 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-08-01 03:09:36 (4119) [INFO] 
* 2023-08-01 03:09:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-01 03:09:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-01 03:09:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-01 03:09:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GkGUnN9GAs/ea_profile.json
* 2023-08-01 03:09:56 (2259) [INFO] Backed up EA4 profile to /tmp/GkGUnN9GAs/ea_profile.json
* 2023-08-01 03:09:58 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-02 03:08:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-02 03:08:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-02 03:08:45 (4089) [INFO] 
* 2023-08-02 03:08:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-02 03:08:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-02 03:08:46 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-02 03:08:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-02 03:08:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-02 03:08:46 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-02 03:08:46 (4119) [INFO] 
* 2023-08-02 03:08:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-02 03:08:46 (4089) [INFO] 
* 2023-08-02 03:09:01 (4102) [INFO] 
* 2023-08-02 03:09:01 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-08-02 03:09:01 (4119) [INFO] 
* 2023-08-02 03:09:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-02 03:09:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-02 03:09:50 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-02 03:09:50 (1567) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2023-08-02 03:09:50 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-02 03:09:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-02 03:09:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/y4QNHSZLkg/ea_profile.json
* 2023-08-02 03:09:51 (2259) [INFO] Backed up EA4 profile to /tmp/y4QNHSZLkg/ea_profile.json
* 2023-08-02 03:09:52 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-03 03:09:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-03 03:09:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-03 03:09:22 (4089) [INFO] 
* 2023-08-03 03:09:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-03 03:09:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-03 03:09:22 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-03 03:09:22 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-03 03:09:22 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-03 03:09:22 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-03 03:09:22 (4119) [INFO] 
* 2023-08-03 03:09:22 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-03 03:09:22 (4089) [INFO] 
* 2023-08-03 03:09:31 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-08-03 03:09:31 (4102) [INFO] Trying other mirror.
* 2023-08-03 03:09:31 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/9a6a78afd172c238b1fb97f11e281aa09fee8865bec7518c4ad43e95be239a51-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-03 03:09:31 (4102) [INFO] Trying other mirror.
* 2023-08-03 03:09:43 (4102) [INFO] 
* 2023-08-03 03:09:43 (4102) [INFO] kernel.x86_64                    3.10.0-1160.92.1.el7                    updates
* 2023-08-03 03:09:43 (4119) [INFO] 
* 2023-08-03 03:09:43 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-03 03:09:43 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-03 03:10:01 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-03 03:10:01 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iA8vtdzht5/ea_profile.json
* 2023-08-03 03:10:02 (2259) [INFO] Backed up EA4 profile to /tmp/iA8vtdzht5/ea_profile.json
* 2023-08-03 03:10:03 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-04 03:09:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-04 03:09:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-04 03:09:44 (4089) [INFO] 
* 2023-08-04 03:09:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-04 03:09:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-04 03:09:44 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-04 03:09:44 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-04 03:09:44 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-04 03:09:44 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-04 03:09:44 (4119) [INFO] 
* 2023-08-04 03:09:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-04 03:09:44 (4089) [INFO] 
* 2023-08-04 03:10:02 (4102) [INFO] 
* 2023-08-04 03:10:02 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-04 03:10:02 (4119) [INFO] 
* 2023-08-04 03:10:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-04 03:10:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-04 03:10:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-04 03:10:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RPAQmT0YTS/ea_profile.json
* 2023-08-04 03:10:25 (2259) [INFO] Backed up EA4 profile to /tmp/RPAQmT0YTS/ea_profile.json
* 2023-08-04 03:10:26 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-05 03:09:41 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-05 03:09:41 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-05 03:09:41 (4089) [INFO] 
* 2023-08-05 03:09:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-05 03:09:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-05 03:09:41 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-05 03:09:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-05 03:09:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-05 03:09:41 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-05 03:09:41 (4119) [INFO] 
* 2023-08-05 03:09:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-05 03:09:41 (4089) [INFO] 
* 2023-08-05 03:09:56 (4102) [INFO] 
* 2023-08-05 03:09:56 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-05 03:09:56 (4119) [INFO] 
* 2023-08-05 03:09:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-05 03:09:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-05 03:10:20 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-05 03:10:20 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/n7NaZkaexD/ea_profile.json
* 2023-08-05 03:10:22 (2259) [INFO] Backed up EA4 profile to /tmp/n7NaZkaexD/ea_profile.json
* 2023-08-05 03:10:23 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-06 03:09:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-06 03:09:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-06 03:09:38 (4089) [INFO] 
* 2023-08-06 03:09:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-06 03:09:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-06 03:09:38 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-06 03:09:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-06 03:09:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-06 03:09:38 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-06 03:09:39 (4119) [INFO] 
* 2023-08-06 03:09:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-06 03:09:39 (4089) [INFO] 
* 2023-08-06 03:09:53 (4102) [INFO] 
* 2023-08-06 03:09:53 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-06 03:09:53 (4119) [INFO] 
* 2023-08-06 03:09:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-06 03:09:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-06 03:10:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-06 03:10:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/3nVuFiBqAp/ea_profile.json
* 2023-08-06 03:10:13 (2259) [INFO] Backed up EA4 profile to /tmp/3nVuFiBqAp/ea_profile.json
* 2023-08-06 03:10:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-07 03:08:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-07 03:08:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-07 03:08:46 (4089) [INFO] 
* 2023-08-07 03:08:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-07 03:08:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-07 03:08:47 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-07 03:08:47 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-07 03:08:47 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-07 03:08:47 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-07 03:08:47 (4119) [INFO] 
* 2023-08-07 03:08:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-07 03:08:47 (4089) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-08-07 03:09:14 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-07 03:09:14 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-07 03:09:14 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-07 03:09:14 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-07 03:09:14 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-07 03:09:14 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-07 03:09:14 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-07 03:09:14 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-08-07 03:09:14 (4102) [INFO]         or
* 2023-08-07 03:09:14 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-07 03:09:14 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-07 03:09:14 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-07 03:09:14 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-07 03:09:14 (4102) [INFO]         compromise:
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-08-07 03:09:14 (4102) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-08-07 03:09:14 (4119) [INFO] 
* 2023-08-07 03:09:14 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-07 03:09:14 (1721) [INFO] Checking /scripts/sysup
* 2023-08-07 03:09:14 (4088) [INFO] Running: /scripts/sysup
* 2023-08-07 03:09:14 (4089) [INFO] 
* 2023-08-07 03:09:14 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-07 03:09:15 (4102) [INFO]   All Needed Packages are already installed.
* 2023-08-07 03:09:15 (4119) [INFO] 
* 2023-08-07 03:09:44 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-07 03:09:44 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uYA6h2ENwV/ea_profile.json
* 2023-08-07 03:09:45 (2259) [INFO] Backed up EA4 profile to /tmp/uYA6h2ENwV/ea_profile.json
* 2023-08-07 03:09:47 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-08-08 03:08:47 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-08 03:08:47 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-08 03:08:47 (4089) [INFO] 
* 2023-08-08 03:08:47 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-08 03:08:47 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-08 03:08:47 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-08 03:08:47 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-08 03:08:47 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-08 03:08:47 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-08 03:08:47 (4119) [INFO] 
* 2023-08-08 03:08:47 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-08 03:08:47 (4089) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-08-08 03:09:13 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-08 03:09:13 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-08 03:09:13 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-08 03:09:13 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-08 03:09:13 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-08 03:09:13 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-08 03:09:13 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-08 03:09:13 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-08-08 03:09:13 (4102) [INFO]         or
* 2023-08-08 03:09:13 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-08 03:09:13 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-08 03:09:13 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-08 03:09:13 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-08 03:09:13 (4102) [INFO]         compromise:
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-08-08 03:09:13 (4102) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-08-08 03:09:13 (4119) [INFO] 
* 2023-08-08 03:09:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-08 03:09:13 (1721) [INFO] Checking /scripts/sysup
* 2023-08-08 03:09:13 (4088) [INFO] Running: /scripts/sysup
* 2023-08-08 03:09:13 (4089) [INFO] 
* 2023-08-08 03:09:13 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-08 03:09:14 (4102) [INFO]   All Needed Packages are already installed.
* 2023-08-08 03:09:14 (4119) [INFO] 
* 2023-08-08 03:09:41 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-08 03:09:41 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/HynRkOhEv4/ea_profile.json
* 2023-08-08 03:09:42 (2259) [INFO] Backed up EA4 profile to /tmp/HynRkOhEv4/ea_profile.json
* 2023-08-08 03:09:43 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-08-09 03:08:57 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-09 03:08:57 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-09 03:08:57 (4089) [INFO] 
* 2023-08-09 03:08:57 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-09 03:08:57 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-09 03:08:57 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-09 03:08:57 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-09 03:08:57 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-09 03:08:57 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-09 03:08:57 (4119) [INFO] 
* 2023-08-09 03:08:57 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-09 03:08:57 (4089) [INFO] 
* 2023-08-09 03:09:08 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-09 03:09:08 (4102) [INFO] Trying other mirror.
* 2023-08-09 03:09:18 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-09 03:09:18 (4102) [INFO] Trying other mirror.
* 2023-08-09 03:09:19 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-08-09 03:09:19 (4102) [INFO] Trying other mirror.
* 2023-08-09 03:09:27 (4102) [INFO] Traceback (most recent call last):
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-08-09 03:09:27 (4102) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-08-09 03:09:27 (4102) [INFO]     errcode = main(args)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-08-09 03:09:27 (4102) [INFO]     result, resultmsgs = base.doCommands()
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-08-09 03:09:27 (4102) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-08-09 03:09:27 (4102) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-08-09 03:09:27 (4102) [INFO]     ignore_case=True, repoid=repoid)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-08-09 03:09:27 (4102) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-08-09 03:09:27 (4102) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-08-09 03:09:27 (4102) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-08-09 03:09:27 (4102) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-08-09 03:09:27 (4102) [INFO]     self.repos.populateSack(which=repos)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack
* 2023-08-09 03:09:27 (4102) [INFO]     sack.populate(repo, mdtype, callback, cacheonly)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 234, in populate
* 2023-08-09 03:09:27 (4102) [INFO]     db_un_fn = self._check_uncompressed_db_gen(repo, mydbtype)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-08-09 03:09:27 (4102) [INFO]     cached=repo.cache)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-08-09 03:09:27 (4102) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-08-09 03:09:27 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-08-09 03:09:27 (4102) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-08-09 03:09:27 (4102) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite'
* 2023-08-09 03:09:27 (4119) [INFO] 
* 2023-08-09 03:09:27 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-09 03:09:27 (1721) [INFO] Checking /scripts/sysup
* 2023-08-09 03:09:27 (4088) [INFO] Running: /scripts/sysup
* 2023-08-09 03:09:27 (4089) [INFO] 
* 2023-08-09 03:09:27 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-09 03:09:28 (4102) [INFO]   All Needed Packages are already installed.
* 2023-08-09 03:09:28 (4119) [INFO] 
* 2023-08-09 03:09:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-09 03:09:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9iSFm3a8IF/ea_profile.json
* 2023-08-09 03:09:50 (2259) [INFO] Backed up EA4 profile to /tmp/9iSFm3a8IF/ea_profile.json
* 2023-08-09 03:09:52 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-08-10 03:09:22 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-10 03:09:22 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-10 03:09:22 (4089) [INFO] 
* 2023-08-10 03:09:22 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-10 03:09:22 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-10 03:09:22 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-10 03:09:22 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-10 03:09:22 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-10 03:09:22 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-10 03:09:22 (4119) [INFO] 
* 2023-08-10 03:09:22 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-10 03:09:22 (4089) [INFO] 
* 2023-08-10 03:09:48 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-10 03:09:48 (4102) [INFO] Trying other mirror.
* 2023-08-10 03:09:51 (4102) [INFO] 
* 2023-08-10 03:09:51 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-10 03:09:51 (4119) [INFO] 
* 2023-08-10 03:09:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-10 03:09:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-10 03:10:13 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-10 03:10:13 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZCntViZW7e/ea_profile.json
* 2023-08-10 03:10:14 (2259) [INFO] Backed up EA4 profile to /tmp/ZCntViZW7e/ea_profile.json
* 2023-08-10 03:10:15 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-11 03:08:50 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-11 03:08:50 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-11 03:08:50 (4089) [INFO] 
* 2023-08-11 03:08:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-11 03:08:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-11 03:08:50 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-11 03:08:50 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-11 03:08:50 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-11 03:08:50 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-11 03:08:50 (4119) [INFO] 
* 2023-08-11 03:08:50 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-11 03:08:50 (4089) [INFO] 
* 2023-08-11 03:09:10 (4102) [INFO] 
* 2023-08-11 03:09:10 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-11 03:09:10 (4119) [INFO] 
* 2023-08-11 03:09:10 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-11 03:09:10 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-11 03:09:38 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-11 03:09:38 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5z9Kbp0TEE/ea_profile.json
* 2023-08-11 03:09:39 (2259) [INFO] Backed up EA4 profile to /tmp/5z9Kbp0TEE/ea_profile.json
* 2023-08-11 03:09:41 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-12 03:09:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-12 03:09:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-12 03:09:40 (4089) [INFO] 
* 2023-08-12 03:09:41 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-12 03:09:41 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-12 03:09:41 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-12 03:09:41 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-12 03:09:41 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-12 03:09:41 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-12 03:09:41 (4119) [INFO] 
* 2023-08-12 03:09:41 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-12 03:09:41 (4089) [INFO] 
* 2023-08-12 03:09:55 (4102) [INFO] 
* 2023-08-12 03:09:55 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-12 03:09:55 (4119) [INFO] 
* 2023-08-12 03:09:55 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-12 03:09:55 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-12 03:10:11 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-12 03:10:11 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iXEiNGWobg/ea_profile.json
* 2023-08-12 03:10:12 (2259) [INFO] Backed up EA4 profile to /tmp/iXEiNGWobg/ea_profile.json
* 2023-08-12 03:10:14 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-13 03:09:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-13 03:09:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-13 03:09:39 (4089) [INFO] 
* 2023-08-13 03:09:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-13 03:09:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-13 03:09:39 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-13 03:09:39 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-13 03:09:39 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-13 03:09:39 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-13 03:09:39 (4119) [INFO] 
* 2023-08-13 03:09:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-13 03:09:39 (4089) [INFO] 
* 2023-08-13 03:09:54 (4102) [INFO] 
* 2023-08-13 03:09:54 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-13 03:09:54 (4119) [INFO] 
* 2023-08-13 03:09:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-13 03:09:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-13 03:10:17 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-13 03:10:17 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AWDd9GzusL/ea_profile.json
* 2023-08-13 03:10:18 (2259) [INFO] Backed up EA4 profile to /tmp/AWDd9GzusL/ea_profile.json
* 2023-08-13 03:10:20 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-14 03:08:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-14 03:08:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-14 03:08:42 (4089) [INFO] 
* 2023-08-14 03:08:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-14 03:08:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-14 03:08:42 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-14 03:08:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-14 03:08:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-14 03:08:42 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-14 03:08:42 (4119) [INFO] 
* 2023-08-14 03:08:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-14 03:08:42 (4089) [INFO] 
* 2023-08-14 03:08:57 (4102) [INFO] 
* 2023-08-14 03:08:57 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-14 03:08:57 (4119) [INFO] 
* 2023-08-14 03:08:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-14 03:08:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-14 03:09:24 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-14 03:09:24 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/tG4OhnyraB/ea_profile.json
* 2023-08-14 03:09:25 (2259) [INFO] Backed up EA4 profile to /tmp/tG4OhnyraB/ea_profile.json
* 2023-08-14 03:09:27 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-15 03:14:19 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-15 03:14:19 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-15 03:14:19 (4089) [INFO] 
* 2023-08-15 03:14:19 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-15 03:14:19 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-15 03:14:19 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-15 03:14:19 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-15 03:14:19 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-15 03:14:19 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-15 03:14:19 (4119) [INFO] 
* 2023-08-15 03:14:19 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-15 03:14:19 (4089) [INFO] 
* 2023-08-15 03:14:52 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-08-15 03:14:52 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:15:09 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-15 03:15:09 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:15:24 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-15 03:15:24 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:15:39 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-15 03:15:39 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:15:54 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-15 03:15:54 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:16:09 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-15 03:16:09 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:16:11 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/c22ab7592423533974b81fc7aa72aa2c6797aad7a5ab179c22d111ddd9daa65a-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-15 03:16:11 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:16:12 (4102) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-15 03:16:12 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:16:18 (4102) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-15 03:16:18 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:16:35 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/c22ab7592423533974b81fc7aa72aa2c6797aad7a5ab179c22d111ddd9daa65a-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-15 03:16:35 (4102) [INFO] Trying other mirror.
* 2023-08-15 03:16:56 (4102) [INFO] 
* 2023-08-15 03:16:56 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-15 03:16:56 (4119) [INFO] 
* 2023-08-15 03:16:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-15 03:16:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-15 03:21:12 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-15 03:21:12 (1567) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 11871.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  51 M RSS (373 MB VSZ)
    Started: Tue Aug 15 03:15:01 2023 - 01:55 ago
    State  : Running, pid: 11871
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e74cae71b3e0bbb34523b500b865b6410e79cdea5ff7fdeab5e920b00c1f71e8-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/a377019de29a3ca8383a82d1381d5d217e0d260079c98e6c4a7aea03b8b6b1ec-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/d97eacce4c009e97b452a0432170d77e870b3ed72904126687a06426494f9ad5-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/03f1ada6bc515154cb40e044f137d008cdbad754313bf0fa0949cb18e255d65e-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/03f1ada6bc515154cb40e044f137d008cdbad754313bf0fa0949cb18e255d65e-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/da1191f1a2e5a6e63fcdb7f0f12d11d91362f6bb6e51ccc91327226b737db9cd-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e74cae71b3e0bbb34523b500b865b6410e79cdea5ff7fdeab5e920b00c1f71e8-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/e74cae71b3e0bbb34523b500b865b6410e79cdea5ff7fdeab5e920b00c1f71e8-other.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-08-15 03:21:12 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-15 03:21:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-15 03:21:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/B76vZ9QMwz/ea_profile.json
* 2023-08-15 03:22:33 (2259) [INFO] Backed up EA4 profile to /tmp/B76vZ9QMwz/ea_profile.json
* 2023-08-15 03:22:35 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-16 03:08:55 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-16 03:08:55 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-16 03:08:55 (4089) [INFO] 
* 2023-08-16 03:08:55 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-16 03:08:55 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-16 03:08:55 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-16 03:08:55 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-16 03:08:55 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-16 03:08:55 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-16 03:08:55 (4119) [INFO] 
* 2023-08-16 03:08:55 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-16 03:08:55 (4089) [INFO] 
* 2023-08-16 03:09:17 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-16 03:09:17 (4102) [INFO] Trying other mirror.
* 2023-08-16 03:09:24 (4102) [INFO] 
* 2023-08-16 03:09:24 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-16 03:09:24 (4119) [INFO] 
* 2023-08-16 03:09:24 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-16 03:09:24 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-16 03:09:50 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-16 03:09:50 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LWBFGlk5w3/ea_profile.json
* 2023-08-16 03:09:51 (2259) [INFO] Backed up EA4 profile to /tmp/LWBFGlk5w3/ea_profile.json
* 2023-08-16 03:09:52 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-17 03:09:23 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-17 03:09:23 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-17 03:09:23 (4089) [INFO] 
* 2023-08-17 03:09:23 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-17 03:09:23 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-17 03:09:23 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-17 03:09:23 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-17 03:09:23 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-17 03:09:23 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-17 03:09:23 (4119) [INFO] 
* 2023-08-17 03:09:23 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-17 03:09:23 (4089) [INFO] 
* 2023-08-17 03:09:48 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/fd95ae1dce588efa53b0317ac940e43763cb11f794659b91fb7f5a57e1376936-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-17 03:09:48 (4102) [INFO] Trying other mirror.
* 2023-08-17 03:09:50 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f88ceda47e678c950ea724496550a9d7ca2ca22786d618d8d06988d7d8479cc8-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-08-17 03:09:50 (4102) [INFO] Trying other mirror.
* 2023-08-17 03:09:57 (4102) [INFO] 
* 2023-08-17 03:09:57 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-17 03:09:57 (4119) [INFO] 
* 2023-08-17 03:09:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-17 03:09:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-17 03:10:15 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-17 03:10:15 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/u158NbAvWy/ea_profile.json
* 2023-08-17 03:10:16 (2259) [INFO] Backed up EA4 profile to /tmp/u158NbAvWy/ea_profile.json
* 2023-08-17 03:10:17 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-18 03:08:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-18 03:08:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-18 03:08:44 (4089) [INFO] 
* 2023-08-18 03:08:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-18 03:08:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-18 03:08:44 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-18 03:08:44 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-18 03:08:44 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-18 03:08:44 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-18 03:08:44 (4119) [INFO] 
* 2023-08-18 03:08:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-18 03:08:44 (4089) [INFO] 
* 2023-08-18 03:09:01 (4102) [INFO] 
* 2023-08-18 03:09:01 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-18 03:09:01 (4119) [INFO] 
* 2023-08-18 03:09:01 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-18 03:09:01 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-18 03:09:49 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-18 03:09:49 (1567) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2023-08-18 03:09:49 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-18 03:09:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-18 03:09:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2_kyoz6s7r/ea_profile.json
* 2023-08-18 03:09:50 (2259) [INFO] Backed up EA4 profile to /tmp/2_kyoz6s7r/ea_profile.json
* 2023-08-18 03:09:52 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-19 03:09:31 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-19 03:09:31 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-19 03:09:31 (4089) [INFO] 
* 2023-08-19 03:09:31 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-19 03:09:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-19 03:09:31 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-19 03:09:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-19 03:09:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-19 03:09:31 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-19 03:09:31 (4119) [INFO] 
* 2023-08-19 03:09:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-19 03:09:31 (4089) [INFO] 
* 2023-08-19 03:09:46 (4102) [INFO] 
* 2023-08-19 03:09:46 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-19 03:09:46 (4119) [INFO] 
* 2023-08-19 03:09:46 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-19 03:09:46 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-19 03:10:02 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-19 03:10:02 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/BlvGrJsCd3/ea_profile.json
* 2023-08-19 03:10:03 (2259) [INFO] Backed up EA4 profile to /tmp/BlvGrJsCd3/ea_profile.json
* 2023-08-19 03:10:04 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-20 03:09:28 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-20 03:09:28 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-20 03:09:28 (4089) [INFO] 
* 2023-08-20 03:09:30 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-20 03:09:31 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-20 03:09:31 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-20 03:09:31 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-20 03:09:31 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-20 03:09:31 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-20 03:09:31 (4119) [INFO] 
* 2023-08-20 03:09:31 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-20 03:09:31 (4089) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-08-20 03:09:40 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-20 03:09:40 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-20 03:09:40 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-20 03:09:40 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-20 03:09:40 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-20 03:09:40 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-20 03:09:40 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-20 03:09:40 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-08-20 03:09:40 (4102) [INFO]         or
* 2023-08-20 03:09:40 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-20 03:09:40 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-20 03:09:40 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-20 03:09:40 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-20 03:09:40 (4102) [INFO]         compromise:
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-08-20 03:09:40 (4102) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO] imunify360: Check uncompressed DB failed
* 2023-08-20 03:09:40 (4119) [INFO] 
* 2023-08-20 03:09:40 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-20 03:09:40 (1721) [INFO] Checking /scripts/sysup
* 2023-08-20 03:09:40 (4088) [INFO] Running: /scripts/sysup
* 2023-08-20 03:09:40 (4089) [INFO] 
* 2023-08-20 03:09:40 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-20 03:09:41 (4102) [INFO]   All Needed Packages are already installed.
* 2023-08-20 03:09:41 (4119) [INFO] 
* 2023-08-20 03:09:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-20 03:09:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5an_huw630/ea_profile.json
* 2023-08-20 03:09:59 (2259) [INFO] Backed up EA4 profile to /tmp/5an_huw630/ea_profile.json
* 2023-08-20 03:10:00 (269) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-08-21 03:08:35 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-21 03:08:36 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-21 03:08:36 (4089) [INFO] 
* 2023-08-21 03:08:36 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-21 03:08:36 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-21 03:08:36 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-21 03:08:36 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-21 03:08:36 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-21 03:08:36 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-21 03:08:36 (4119) [INFO] 
* 2023-08-21 03:08:36 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-21 03:08:36 (4089) [INFO] 
* 2023-08-21 03:08:51 (4102) [INFO] 
* 2023-08-21 03:08:51 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-21 03:08:51 (4119) [INFO] 
* 2023-08-21 03:08:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-21 03:08:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-21 03:09:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-21 03:09:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/B4r5LUvyQN/ea_profile.json
* 2023-08-21 03:09:07 (2259) [INFO] Backed up EA4 profile to /tmp/B4r5LUvyQN/ea_profile.json
* 2023-08-21 03:09:09 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-22 03:09:57 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-22 03:09:57 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-22 03:09:57 (4089) [INFO] 
* 2023-08-22 03:09:57 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-22 03:09:57 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-22 03:09:57 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-22 03:09:57 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-22 03:09:57 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-22 03:09:57 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-22 03:09:58 (4119) [INFO] 
* 2023-08-22 03:09:58 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-22 03:09:58 (4089) [INFO] 
* 2023-08-22 03:10:11 (4102) [INFO] 
* 2023-08-22 03:10:11 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-22 03:10:11 (4119) [INFO] 
* 2023-08-22 03:10:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-22 03:10:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-22 03:10:37 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-22 03:10:37 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2wtYZwn8Qz/ea_profile.json
* 2023-08-22 03:10:38 (2259) [INFO] Backed up EA4 profile to /tmp/2wtYZwn8Qz/ea_profile.json
* 2023-08-22 03:10:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-23 03:08:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-23 03:08:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-23 03:08:38 (4089) [INFO] 
* 2023-08-23 03:08:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-23 03:08:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-23 03:08:38 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-23 03:08:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-23 03:08:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-23 03:08:38 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-23 03:08:38 (4119) [INFO] 
* 2023-08-23 03:08:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-23 03:08:38 (4089) [INFO] 
* 2023-08-23 03:08:53 (4102) [INFO] 
* 2023-08-23 03:08:53 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-23 03:08:54 (4119) [INFO] 
* 2023-08-23 03:08:54 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-23 03:08:54 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-23 03:09:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-23 03:09:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AwhsRHWEDj/ea_profile.json
* 2023-08-23 03:09:11 (2259) [INFO] Backed up EA4 profile to /tmp/AwhsRHWEDj/ea_profile.json
* 2023-08-23 03:09:13 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-24 03:09:09 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-24 03:09:09 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-24 03:09:09 (4089) [INFO] 
* 2023-08-24 03:09:10 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-24 03:09:10 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-24 03:09:10 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-24 03:09:10 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-24 03:09:10 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-24 03:09:10 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-24 03:09:10 (4119) [INFO] 
* 2023-08-24 03:09:10 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-24 03:09:10 (4089) [INFO] 
* 2023-08-24 03:09:43 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-08-24 03:09:43 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:15 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-24 03:10:15 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:22 (4102) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-24 03:10:22 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:30 (4102) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-24 03:10:30 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:31 (4102) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-24 03:10:31 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:35 (4102) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-24 03:10:35 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:37 (4102) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-24 03:10:37 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:41 (4102) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/8e66e61f4901c9dceed255d4b1d7b3d15df5fc2192700b9905b5450afed7dbd3-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-08-24 03:10:41 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:42 (4102) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-08-24 03:10:42 (4102) [INFO] Trying other mirror.
* 2023-08-24 03:10:59 (4102) [INFO] 
* 2023-08-24 03:10:59 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-24 03:11:00 (4119) [INFO] 
* 2023-08-24 03:11:00 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-24 03:11:00 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-24 03:11:59 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-24 03:11:59 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-08-24 03:11:59 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-24 03:11:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-24 03:11:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/lL2D4pCRUT/ea_profile.json
* 2023-08-24 03:12:00 (2259) [INFO] Backed up EA4 profile to /tmp/lL2D4pCRUT/ea_profile.json
* 2023-08-24 03:12:02 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-25 03:08:53 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-25 03:08:53 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-25 03:08:53 (4089) [INFO] 
* 2023-08-25 03:08:53 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-25 03:08:53 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-25 03:08:53 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-25 03:08:53 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-25 03:08:53 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-25 03:08:53 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-25 03:08:53 (4119) [INFO] 
* 2023-08-25 03:08:53 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-25 03:08:53 (4089) [INFO] 
* 2023-08-25 03:09:08 (4102) [INFO] 
* 2023-08-25 03:09:08 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-25 03:09:08 (4119) [INFO] 
* 2023-08-25 03:09:08 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-25 03:09:08 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-25 03:09:55 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-25 03:09:55 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-08-25 03:09:55 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-25 03:09:55 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-25 03:09:55 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8rRULozf1m/ea_profile.json
* 2023-08-25 03:09:56 (2259) [INFO] Backed up EA4 profile to /tmp/8rRULozf1m/ea_profile.json
* 2023-08-25 03:09:57 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-26 03:10:45 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-26 03:10:45 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-26 03:10:45 (4089) [INFO] 
* 2023-08-26 03:10:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-26 03:10:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-26 03:10:46 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-26 03:10:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-26 03:10:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-26 03:10:46 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-26 03:10:46 (4119) [INFO] 
* 2023-08-26 03:10:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-26 03:10:46 (4089) [INFO] 
* 2023-08-26 03:11:06 (4102) [INFO] 
* 2023-08-26 03:11:06 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-26 03:11:06 (4119) [INFO] 
* 2023-08-26 03:11:06 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-26 03:11:06 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-26 03:11:25 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-26 03:11:25 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/FnDaDHrgLi/ea_profile.json
* 2023-08-26 03:11:26 (2259) [INFO] Backed up EA4 profile to /tmp/FnDaDHrgLi/ea_profile.json
* 2023-08-26 03:11:27 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-27 03:09:33 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-27 03:09:33 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-27 03:09:33 (4089) [INFO] 
* 2023-08-27 03:09:33 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-27 03:09:33 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-27 03:09:33 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-27 03:09:33 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-27 03:09:33 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-27 03:09:33 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-27 03:09:33 (4119) [INFO] 
* 2023-08-27 03:09:33 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-27 03:09:33 (4089) [INFO] 
* 2023-08-27 03:09:38 (4102) [INFO] http://185.15.22.168/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:38 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:38 (4102) [INFO] http://185.15.22.168/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/ebece009140986432869d83a5cf6d94dc1b1f25ee098b06fc6f97afe260bbe26-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:38 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:38 (4102) [INFO] http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/8f564eba3a20f4aa8e22152bfcf277f8488f6fc7a52d11f2ac18a5069a23a65c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:38 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:38 (4102) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/7ba73f54d2f1109c730a30718fd938272da1460f3e7dad0ddf0eb3f161f706be-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:38 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:38 (4102) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:38 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:39 (4102) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:39 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:39 (4102) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:39 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:40 (4102) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/b5077d6261d045cdc925b73138439ef973ef726fad4a2374aee5ef5e2fdac17e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:40 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:41 (4102) [INFO] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/8f564eba3a20f4aa8e22152bfcf277f8488f6fc7a52d11f2ac18a5069a23a65c-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-08-27 03:09:41 (4102) [INFO] Trying other mirror.
* 2023-08-27 03:09:42 (4102) [INFO] Traceback (most recent call last):
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-08-27 03:09:42 (4102) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-08-27 03:09:42 (4102) [INFO]     errcode = main(args)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-08-27 03:09:42 (4102) [INFO]     result, resultmsgs = base.doCommands()
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-08-27 03:09:42 (4102) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-08-27 03:09:42 (4102) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-08-27 03:09:42 (4102) [INFO]     ignore_case=True, repoid=repoid)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-08-27 03:09:42 (4102) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-08-27 03:09:42 (4102) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-08-27 03:09:42 (4102) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-08-27 03:09:42 (4102) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-08-27 03:09:42 (4102) [INFO]     self.repos.populateSack(which=repos)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2023-08-27 03:09:42 (4102) [INFO]     sack._retrieve_async(repo, data)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2023-08-27 03:09:42 (4102) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-08-27 03:09:42 (4102) [INFO]     cached=repo.cache)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-08-27 03:09:42 (4102) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-08-27 03:09:42 (4102) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-08-27 03:09:42 (4102) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-08-27 03:09:42 (4102) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/EA4/gen/primary_db.sqlite'
* 2023-08-27 03:09:42 (4119) [INFO] 
* 2023-08-27 03:09:42 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-27 03:09:42 (1721) [INFO] Checking /scripts/sysup
* 2023-08-27 03:09:42 (4088) [INFO] Running: /scripts/sysup
* 2023-08-27 03:09:42 (4089) [INFO] 
* 2023-08-27 03:09:42 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-27 03:09:43 (4102) [INFO]   All Needed Packages are already installed.
* 2023-08-27 03:09:43 (4119) [INFO] 
* 2023-08-27 03:10:04 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-27 03:10:04 (1567) [ERROR] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2023-08-27 03:10:04 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-27 03:10:05 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-27 03:10:05 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/B6X_hJwSwl/ea_profile.json
* 2023-08-27 03:10:06 (2259) [INFO] Backed up EA4 profile to /tmp/B6X_hJwSwl/ea_profile.json
* 2023-08-27 03:10:07 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-28 03:08:39 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-28 03:08:39 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-28 03:08:39 (4089) [INFO] 
* 2023-08-28 03:08:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-28 03:08:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-28 03:08:39 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-28 03:08:39 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-28 03:08:39 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-28 03:08:39 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-28 03:08:39 (4119) [INFO] 
* 2023-08-28 03:08:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-28 03:08:39 (4089) [INFO] 
* 2023-08-28 03:08:56 (4102) [INFO] 
* 2023-08-28 03:08:56 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-28 03:08:56 (4119) [INFO] 
* 2023-08-28 03:08:56 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-28 03:08:56 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-28 03:09:14 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-28 03:09:14 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hlJPz4Eorm/ea_profile.json
* 2023-08-28 03:09:15 (2259) [INFO] Backed up EA4 profile to /tmp/hlJPz4Eorm/ea_profile.json
* 2023-08-28 03:09:16 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-29 03:08:44 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-29 03:08:44 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-29 03:08:44 (4089) [INFO] 
* 2023-08-29 03:08:44 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-29 03:08:44 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-29 03:08:44 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-29 03:08:44 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-29 03:08:44 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-29 03:08:44 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-29 03:08:44 (4119) [INFO] 
* 2023-08-29 03:08:44 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-29 03:08:44 (4089) [INFO] 
* 2023-08-29 03:09:02 (4102) [INFO] 
* 2023-08-29 03:09:02 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-29 03:09:02 (4119) [INFO] 
* 2023-08-29 03:09:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-29 03:09:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-29 03:09:36 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-29 03:09:36 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XLxBnCkbJh/ea_profile.json
* 2023-08-29 03:09:37 (2259) [INFO] Backed up EA4 profile to /tmp/XLxBnCkbJh/ea_profile.json
* 2023-08-29 03:09:39 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-30 03:08:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-30 03:08:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-30 03:08:38 (4089) [INFO] 
* 2023-08-30 03:08:38 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-30 03:08:38 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-30 03:08:38 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-30 03:08:38 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-30 03:08:38 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-30 03:08:38 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-30 03:08:38 (4119) [INFO] 
* 2023-08-30 03:08:38 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-30 03:08:38 (4089) [INFO] 
* 2023-08-30 03:08:53 (4102) [INFO] 
* 2023-08-30 03:08:53 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-08-30 03:08:53 (4119) [INFO] 
* 2023-08-30 03:08:53 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-30 03:08:53 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-08-30 03:09:10 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-30 03:09:10 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NjdY3ZH4NE/ea_profile.json
* 2023-08-30 03:09:11 (2259) [INFO] Backed up EA4 profile to /tmp/NjdY3ZH4NE/ea_profile.json
* 2023-08-30 03:09:12 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-08-31 03:08:49 (1700) [INFO] Checking if your system is up to date: 
* 2023-08-31 03:08:49 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-08-31 03:08:49 (4089) [INFO] 
* 2023-08-31 03:08:49 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-08-31 03:08:49 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-08-31 03:08:49 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-08-31 03:08:49 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-08-31 03:08:49 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-08-31 03:08:49 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-08-31 03:08:49 (4119) [INFO] 
* 2023-08-31 03:08:49 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-08-31 03:08:49 (4089) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]  One of the configured repositories failed (Unknown),
* 2023-08-31 03:09:13 (4102) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-08-31 03:09:13 (4102) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-08-31 03:09:13 (4102) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-08-31 03:09:13 (4102) [INFO]         distribution release than is supported by the repository (and the
* 2023-08-31 03:09:13 (4102) [INFO]         packages for the previous distribution release still work).
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-08-31 03:09:13 (4102) [INFO]             yum --disablerepo=<repoid> ...
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-08-31 03:09:13 (4102) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-08-31 03:09:13 (4102) [INFO]         again or use --enablerepo for temporary usage:
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]             yum-config-manager --disable <repoid>
* 2023-08-31 03:09:13 (4102) [INFO]         or
* 2023-08-31 03:09:13 (4102) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-08-31 03:09:13 (4102) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-08-31 03:09:13 (4102) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-08-31 03:09:13 (4102) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-08-31 03:09:13 (4102) [INFO]         compromise:
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-08-31 03:09:13 (4102) [INFO] 
* 2023-08-31 03:09:13 (4102) [INFO] updates: Check uncompressed DB failed
* 2023-08-31 03:09:13 (4119) [INFO] 
* 2023-08-31 03:09:13 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-08-31 03:09:13 (1721) [INFO] Checking /scripts/sysup
* 2023-08-31 03:09:13 (4088) [INFO] Running: /scripts/sysup
* 2023-08-31 03:09:13 (4089) [INFO] 
* 2023-08-31 03:09:14 (4102) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-08-31 03:09:14 (4102) [INFO]   All Needed Packages are already installed.
* 2023-08-31 03:09:14 (4119) [INFO] 
* 2023-08-31 03:09:58 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-08-31 03:09:58 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-08-31 03:09:58 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-08-31 03:09:59 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-08-31 03:09:59 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gIvDhVpPBZ/ea_profile.json
* 2023-08-31 03:10:00 (2259) [INFO] Backed up EA4 profile to /tmp/gIvDhVpPBZ/ea_profile.json
* 2023-08-31 03:10:01 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-01 03:08:50 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-01 03:08:50 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-01 03:08:50 (4089) [INFO] 
* 2023-09-01 03:08:50 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-01 03:08:50 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-01 03:08:50 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-01 03:08:50 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-01 03:08:50 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-01 03:08:50 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-01 03:08:50 (4119) [INFO] 
* 2023-09-01 03:08:50 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-01 03:08:50 (4089) [INFO] 
* 2023-09-01 03:09:11 (4102) [INFO] 
* 2023-09-01 03:09:11 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-01 03:09:11 (4119) [INFO] 
* 2023-09-01 03:09:11 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-01 03:09:11 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-01 03:09:48 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-01 03:09:48 (1567) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-09-01 03:09:48 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-01 03:09:48 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-01 03:09:48 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fYy1CZPJPN/ea_profile.json
* 2023-09-01 03:09:49 (2259) [INFO] Backed up EA4 profile to /tmp/fYy1CZPJPN/ea_profile.json
* 2023-09-01 03:09:50 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-02 03:09:26 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-02 03:09:26 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-02 03:09:26 (4089) [INFO] 
* 2023-09-02 03:09:26 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-02 03:09:27 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-02 03:09:27 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-02 03:09:27 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-02 03:09:27 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-02 03:09:27 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-02 03:09:27 (4119) [INFO] 
* 2023-09-02 03:09:27 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-02 03:09:27 (4089) [INFO] 
* 2023-09-02 03:09:36 (4102) [INFO] 
* 2023-09-02 03:09:36 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-02 03:09:36 (4119) [INFO] 
* 2023-09-02 03:09:36 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-02 03:09:36 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-02 03:09:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-02 03:09:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NglQaURgCF/ea_profile.json
* 2023-09-02 03:09:56 (2259) [INFO] Backed up EA4 profile to /tmp/NglQaURgCF/ea_profile.json
* 2023-09-02 03:09:57 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-03 03:09:25 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-03 03:09:25 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-03 03:09:25 (4089) [INFO] 
* 2023-09-03 03:09:25 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-03 03:09:26 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-03 03:09:26 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-03 03:09:26 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-03 03:09:26 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-03 03:09:26 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-03 03:09:26 (4119) [INFO] 
* 2023-09-03 03:09:26 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-03 03:09:26 (4089) [INFO] 
* 2023-09-03 03:09:39 (4102) [INFO] 
* 2023-09-03 03:09:39 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-03 03:09:39 (4119) [INFO] 
* 2023-09-03 03:09:39 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-03 03:09:39 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-03 03:09:57 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-03 03:09:57 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IANDeD9D9_/ea_profile.json
* 2023-09-03 03:09:58 (2259) [INFO] Backed up EA4 profile to /tmp/IANDeD9D9_/ea_profile.json
* 2023-09-03 03:09:59 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-04 03:08:37 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-04 03:08:37 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-04 03:08:37 (4089) [INFO] 
* 2023-09-04 03:08:37 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-04 03:08:37 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-04 03:08:37 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-04 03:08:37 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-04 03:08:37 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-04 03:08:37 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-04 03:08:37 (4119) [INFO] 
* 2023-09-04 03:08:37 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-04 03:08:37 (4089) [INFO] 
* 2023-09-04 03:08:51 (4102) [INFO] 
* 2023-09-04 03:08:51 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-04 03:08:51 (4119) [INFO] 
* 2023-09-04 03:08:51 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-04 03:08:51 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-04 03:09:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-04 03:09:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yUcHR0rYk1/ea_profile.json
* 2023-09-04 03:09:08 (2259) [INFO] Backed up EA4 profile to /tmp/yUcHR0rYk1/ea_profile.json
* 2023-09-04 03:09:09 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-05 03:08:40 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-05 03:08:40 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-05 03:08:40 (4089) [INFO] 
* 2023-09-05 03:08:40 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-05 03:08:40 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-05 03:08:40 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-05 03:08:40 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-05 03:08:40 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-05 03:08:40 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-05 03:08:40 (4119) [INFO] 
* 2023-09-05 03:08:40 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-05 03:08:40 (4089) [INFO] 
* 2023-09-05 03:08:56 (4102) [INFO] 
* 2023-09-05 03:08:56 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-05 03:08:57 (4119) [INFO] 
* 2023-09-05 03:08:57 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-05 03:08:57 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-05 03:09:29 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-05 03:09:29 (1567) [ERROR] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-09-05 03:09:29 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-05 03:09:29 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-05 03:09:29 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LONz4DJLQF/ea_profile.json
* 2023-09-05 03:09:30 (2259) [INFO] Backed up EA4 profile to /tmp/LONz4DJLQF/ea_profile.json
* 2023-09-05 03:09:32 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-06 03:08:38 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-06 03:08:38 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-06 03:08:38 (4089) [INFO] 
* 2023-09-06 03:08:39 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-06 03:08:39 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-06 03:08:39 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-06 03:08:39 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-06 03:08:39 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-06 03:08:39 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-06 03:08:39 (4119) [INFO] 
* 2023-09-06 03:08:39 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-06 03:08:39 (4089) [INFO] 
* 2023-09-06 03:08:52 (4102) [INFO] 
* 2023-09-06 03:08:52 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-06 03:08:52 (4119) [INFO] 
* 2023-09-06 03:08:52 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-06 03:08:52 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-06 03:09:07 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-06 03:09:07 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RsXmGrilgx/ea_profile.json
* 2023-09-06 03:09:07 (2259) [INFO] Backed up EA4 profile to /tmp/RsXmGrilgx/ea_profile.json
* 2023-09-06 03:09:09 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-07 03:08:51 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-07 03:08:51 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-07 03:08:51 (4089) [INFO] 
* 2023-09-07 03:08:51 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-07 03:08:51 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-07 03:08:51 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-07 03:08:51 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-07 03:08:51 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-07 03:08:51 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-07 03:08:51 (4119) [INFO] 
* 2023-09-07 03:08:51 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-07 03:08:51 (4089) [INFO] 
* 2023-09-07 03:09:12 (4102) [INFO] 
* 2023-09-07 03:09:12 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-07 03:09:12 (4119) [INFO] 
* 2023-09-07 03:09:12 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-07 03:09:12 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-07 03:09:45 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-07 03:09:45 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_Zm3Uhyx8I/ea_profile.json
* 2023-09-07 03:09:46 (2259) [INFO] Backed up EA4 profile to /tmp/_Zm3Uhyx8I/ea_profile.json
* 2023-09-07 03:09:47 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-08 03:08:46 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-08 03:08:46 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-08 03:08:46 (4089) [INFO] 
* 2023-09-08 03:08:46 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-08 03:08:46 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-08 03:08:46 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-08 03:08:46 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-08 03:08:46 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-08 03:08:46 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-08 03:08:46 (4119) [INFO] 
* 2023-09-08 03:08:46 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-08 03:08:46 (4089) [INFO] 
* 2023-09-08 03:09:02 (4102) [INFO] 
* 2023-09-08 03:09:02 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-08 03:09:02 (4119) [INFO] 
* 2023-09-08 03:09:02 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-08 03:09:02 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-08 03:09:32 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-08 03:09:32 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NsKSNOYMp0/ea_profile.json
* 2023-09-08 03:09:33 (2259) [INFO] Backed up EA4 profile to /tmp/NsKSNOYMp0/ea_profile.json
* 2023-09-08 03:09:34 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-09 03:09:32 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-09 03:09:32 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-09 03:09:32 (4089) [INFO] 
* 2023-09-09 03:09:32 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-09 03:09:32 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-09 03:09:32 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-09 03:09:32 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-09 03:09:32 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-09 03:09:32 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-09 03:09:32 (4119) [INFO] 
* 2023-09-09 03:09:32 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-09 03:09:32 (4089) [INFO] 
* 2023-09-09 03:09:44 (4102) [INFO] 
* 2023-09-09 03:09:44 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-09 03:09:44 (4119) [INFO] 
* 2023-09-09 03:09:44 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-09 03:09:44 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-09 03:09:58 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-09 03:09:58 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/zcuBvkYRY2/ea_profile.json
* 2023-09-09 03:09:59 (2259) [INFO] Backed up EA4 profile to /tmp/zcuBvkYRY2/ea_profile.json
* 2023-09-09 03:10:00 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-10 03:09:24 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-10 03:09:24 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-10 03:09:24 (4089) [INFO] 
* 2023-09-10 03:09:24 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-10 03:09:24 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-10 03:09:24 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-10 03:09:24 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-10 03:09:24 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-10 03:09:24 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-10 03:09:24 (4119) [INFO] 
* 2023-09-10 03:09:24 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-10 03:09:24 (4089) [INFO] 
* 2023-09-10 03:09:38 (4102) [INFO] 
* 2023-09-10 03:09:38 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-10 03:09:38 (4119) [INFO] 
* 2023-09-10 03:09:38 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-10 03:09:38 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-10 03:09:54 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-10 03:09:54 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/W4PPDosjOK/ea_profile.json
* 2023-09-10 03:09:55 (2259) [INFO] Backed up EA4 profile to /tmp/W4PPDosjOK/ea_profile.json
* 2023-09-10 03:09:56 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-11 03:08:42 (1700) [INFO] Checking if your system is up to date: 
* 2023-09-11 03:08:42 (4088) [INFO] Running: /usr/bin/yum clean all
* 2023-09-11 03:08:42 (4089) [INFO] 
* 2023-09-11 03:08:42 (4102) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-11 03:08:42 (4102) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-11 03:08:42 (4102) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-11 03:08:42 (4102) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-11 03:08:42 (4102) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-11 03:08:42 (4102) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-11 03:08:42 (4119) [INFO] 
* 2023-09-11 03:08:42 (4088) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-11 03:08:42 (4089) [INFO] 
* 2023-09-11 03:08:58 (4102) [INFO] 
* 2023-09-11 03:08:58 (4102) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-11 03:08:58 (4119) [INFO] 
* 2023-09-11 03:08:58 (1707) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-11 03:08:58 (153) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-11 03:09:48 (1566) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-11 03:09:48 (1567) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/dcd9eb66aec573ff85664352309afde6a4e668bfd59ed6b9ce435add7d252740-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/dcd9eb66aec573ff85664352309afde6a4e668bfd59ed6b9ce435add7d252740-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/979955943a6278d821f7648dd532f03e3330b3c2569cf417889970cdad69a9c9-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/979955943a6278d821f7648dd532f03e3330b3c2569cf417889970cdad69a9c9-other.sqlite.bz2: (28, 'Connection timed out after 30002 milliseconds')
Trying other mirror.
* 2023-09-11 03:09:48 (153) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-11 03:09:49 (778) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-11 03:09:49 (2236) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UehRS5u3AS/ea_profile.json
* 2023-09-11 03:09:50 (2259) [INFO] Backed up EA4 profile to /tmp/UehRS5u3AS/ea_profile.json
* 2023-09-11 03:09:51 (258) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-12 03:08:48 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-12 03:08:48 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-12 03:08:48 (4229) [INFO] 
* 2023-09-12 03:08:48 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-12 03:08:48 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-12 03:08:48 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-12 03:08:48 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-12 03:08:48 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-12 03:08:48 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-12 03:08:48 (4259) [INFO] 
* 2023-09-12 03:08:48 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-12 03:08:48 (4229) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]  One of the configured repositories failed (Unknown),
* 2023-09-12 03:09:16 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-09-12 03:09:16 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-09-12 03:09:16 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-09-12 03:09:16 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-09-12 03:09:16 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-09-12 03:09:16 (4242) [INFO]             yum --disablerepo=<repoid> ...
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-09-12 03:09:16 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-09-12 03:09:16 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]             yum-config-manager --disable <repoid>
* 2023-09-12 03:09:16 (4242) [INFO]         or
* 2023-09-12 03:09:16 (4242) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-09-12 03:09:16 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-09-12 03:09:16 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-09-12 03:09:16 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-09-12 03:09:16 (4242) [INFO]         compromise:
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-09-12 03:09:16 (4242) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO] updates: Check uncompressed DB failed
* 2023-09-12 03:09:16 (4259) [INFO] 
* 2023-09-12 03:09:16 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-12 03:09:16 (1773) [INFO] Checking /scripts/sysup
* 2023-09-12 03:09:16 (4228) [INFO] Running: /scripts/sysup
* 2023-09-12 03:09:16 (4229) [INFO] 
* 2023-09-12 03:09:16 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-09-12 03:09:17 (4242) [INFO]   All Needed Packages are already installed.
* 2023-09-12 03:09:17 (4259) [INFO] 
* 2023-09-12 03:09:44 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-12 03:09:44 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2Er3ufWqJI/ea_profile.json
* 2023-09-12 03:09:45 (2293) [INFO] Backed up EA4 profile to /tmp/2Er3ufWqJI/ea_profile.json
* 2023-09-12 03:09:46 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-09-13 03:08:44 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-13 03:08:44 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-13 03:08:44 (4229) [INFO] 
* 2023-09-13 03:08:44 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-13 03:08:44 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-13 03:08:44 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-13 03:08:44 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-13 03:08:44 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-13 03:08:44 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-13 03:08:44 (4259) [INFO] 
* 2023-09-13 03:08:44 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-13 03:08:44 (4229) [INFO] 
* 2023-09-13 03:09:00 (4242) [INFO] 
* 2023-09-13 03:09:00 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-13 03:09:00 (4259) [INFO] 
* 2023-09-13 03:09:00 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-13 03:09:00 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-13 03:09:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-13 03:09:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/u4dewZcrMW/ea_profile.json
* 2023-09-13 03:09:33 (2293) [INFO] Backed up EA4 profile to /tmp/u4dewZcrMW/ea_profile.json
* 2023-09-13 03:09:34 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-14 03:09:26 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-14 03:09:26 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-14 03:09:26 (4229) [INFO] 
* 2023-09-14 03:09:26 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-14 03:09:26 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-14 03:09:26 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-14 03:09:26 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-14 03:09:26 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-14 03:09:26 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-14 03:09:26 (4259) [INFO] 
* 2023-09-14 03:09:26 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-14 03:09:26 (4229) [INFO] 
* 2023-09-14 03:09:56 (4242) [INFO] 
* 2023-09-14 03:09:56 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-14 03:09:56 (4259) [INFO] 
* 2023-09-14 03:09:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-14 03:09:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-14 03:10:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-14 03:10:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QtvQyuOMsa/ea_profile.json
* 2023-09-14 03:10:13 (2293) [INFO] Backed up EA4 profile to /tmp/QtvQyuOMsa/ea_profile.json
* 2023-09-14 03:10:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-15 03:09:08 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-15 03:09:08 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-15 03:09:08 (4229) [INFO] 
* 2023-09-15 03:09:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-15 03:09:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-15 03:09:09 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-15 03:09:09 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-15 03:09:09 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-15 03:09:09 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-15 03:09:09 (4259) [INFO] 
* 2023-09-15 03:09:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-15 03:09:09 (4229) [INFO] 
* 2023-09-15 03:09:35 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-09-15 03:09:35 (4242) [INFO] Trying other mirror.
* 2023-09-15 03:09:40 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-15 03:09:40 (4242) [INFO] Trying other mirror.
* 2023-09-15 03:09:48 (4242) [INFO] 
* 2023-09-15 03:09:48 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-15 03:09:48 (4259) [INFO] 
* 2023-09-15 03:09:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-15 03:09:48 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-15 03:10:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-15 03:10:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wk0zl5e83M/ea_profile.json
* 2023-09-15 03:10:11 (2293) [INFO] Backed up EA4 profile to /tmp/Wk0zl5e83M/ea_profile.json
* 2023-09-15 03:10:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-16 03:09:50 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-16 03:09:50 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-16 03:09:50 (4229) [INFO] 
* 2023-09-16 03:09:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-16 03:09:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-16 03:09:50 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-16 03:09:50 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-16 03:09:50 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-16 03:09:50 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-16 03:09:50 (4259) [INFO] 
* 2023-09-16 03:09:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-16 03:09:50 (4229) [INFO] 
* 2023-09-16 03:10:14 (4242) [INFO] 
* 2023-09-16 03:10:14 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-16 03:10:14 (4259) [INFO] 
* 2023-09-16 03:10:14 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-16 03:10:14 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-16 03:10:34 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-16 03:10:34 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/EpVoBNJdoA/ea_profile.json
* 2023-09-16 03:10:35 (2293) [INFO] Backed up EA4 profile to /tmp/EpVoBNJdoA/ea_profile.json
* 2023-09-16 03:10:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-17 03:09:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-17 03:09:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-17 03:09:28 (4229) [INFO] 
* 2023-09-17 03:09:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-17 03:09:29 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-17 03:09:29 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-17 03:09:29 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-17 03:09:29 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-17 03:09:29 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-17 03:09:29 (4259) [INFO] 
* 2023-09-17 03:09:29 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-17 03:09:29 (4229) [INFO] 
* 2023-09-17 03:09:36 (4242) [INFO] http://84.95.247.234/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:36 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:37 (4242) [INFO] http://84.95.247.234/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/ebece009140986432869d83a5cf6d94dc1b1f25ee098b06fc6f97afe260bbe26-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:37 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:37 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/eeac54525c92c09a80d28e3dc821204f0c0968d6f9f2c81b7a4975220258d903-updateinfo.xml.gz: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:37 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/7ba73f54d2f1109c730a30718fd938272da1460f3e7dad0ddf0eb3f161f706be-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:37 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:37 (4242) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:38 (4242) [INFO] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/5e7ca351efa3a8a68abb93672e9b1d69d5a481a47a612cf6fdce4ed1069ebb13-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:38 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:38 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:38 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/wp-toolkit/repodata/33dffe0c141862083d3f947d53e1092b4b9f3f0540671175a9cfb0ba617bf213-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.8/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/5e7ca351efa3a8a68abb93672e9b1d69d5a481a47a612cf6fdce4ed1069ebb13-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:39 (4242) [INFO] http://artfiles.org/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:39 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:40 (4242) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:40 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:40 (4242) [INFO] http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:40 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:40 (4242) [INFO] http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:40 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:40 (4242) [INFO] http://centos.bio.lmu.de/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:40 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:41 (4242) [INFO] http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:41 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:41 (4242) [INFO] http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:41 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:41 (4242) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:41 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:41 (4242) [INFO] http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:41 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:42 (4242) [INFO] http://mirror.netcologne.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:42 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:42 (4242) [INFO] http://mirror.softaculous.com/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:42 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:42 (4242) [INFO] http://mirror.imt-systems.com/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:42 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:42 (4242) [INFO] http://mirrors.xtom.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:42 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:42 (4242) [INFO] http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:42 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:42 (4242) [INFO] http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:42 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://mirror.23m.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://centos.mirror.iphh.net/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://185.15.22.168/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/ebece009140986432869d83a5cf6d94dc1b1f25ee098b06fc6f97afe260bbe26-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://centos.mirrors.psw.services/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://centosmirror.netcup.net/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:09:43 (4242) [INFO] http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/20fed44d0064e4e52de2083efa2ac06588083a724c1bded6b9fb552ee74135ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-17 03:09:43 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:10:20 (4242) [INFO] http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/5e7ca351efa3a8a68abb93672e9b1d69d5a481a47a612cf6fdce4ed1069ebb13-primary.sqlite.bz2: [Errno 12] Timeout on http://185.157.208.252/cpanelsync/repos/CentOS/7/EA4/repodata/5e7ca351efa3a8a68abb93672e9b1d69d5a481a47a612cf6fdce4ed1069ebb13-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
* 2023-09-17 03:10:20 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:10:21 (4242) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/5e7ca351efa3a8a68abb93672e9b1d69d5a481a47a612cf6fdce4ed1069ebb13-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-17 03:10:21 (4242) [INFO] Trying other mirror.
* 2023-09-17 03:10:23 (4242) [INFO] 
* 2023-09-17 03:10:23 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-17 03:10:23 (4259) [INFO] 
* 2023-09-17 03:10:23 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-17 03:10:23 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-17 03:11:15 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-17 03:11:15 (1619) [ERROR] http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/a550ab8ddb750d6cd796f4995a54b3bc5640dd2da9ed5b0af670f5b14f2a4140-filelists.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/EA4/repodata/a550ab8ddb750d6cd796f4995a54b3bc5640dd2da9ed5b0af670f5b14f2a4140-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/d813c27fae98618fbbba4e613c3ee0f1b341074ee8670428abdf8fb6a6f3535b-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
http://185.15.22.168/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/9a912f5cac0090cc50da8e83a9ccf900e0b13c787331f4cefb4147d247d6dc68-filelists.sqlite.bz2: [Errno 12] Timeout on http://185.15.22.168/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/9a912f5cac0090cc50da8e83a9ccf900e0b13c787331f4cefb4147d247d6dc68-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2023-09-17 03:11:15 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-17 03:11:16 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-17 03:11:16 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WqFZztwNpE/ea_profile.json
* 2023-09-17 03:11:17 (2293) [INFO] Backed up EA4 profile to /tmp/WqFZztwNpE/ea_profile.json
* 2023-09-17 03:11:18 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-18 03:08:53 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-18 03:08:53 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-18 03:08:53 (4229) [INFO] 
* 2023-09-18 03:08:53 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-18 03:08:53 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-18 03:08:53 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-18 03:08:53 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-18 03:08:53 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-18 03:08:53 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-18 03:08:53 (4259) [INFO] 
* 2023-09-18 03:08:53 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-18 03:08:53 (4229) [INFO] 
* 2023-09-18 03:09:11 (4242) [INFO] 
* 2023-09-18 03:09:11 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-18 03:09:11 (4259) [INFO] 
* 2023-09-18 03:09:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-18 03:09:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-18 03:09:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-18 03:09:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ns87hol8O5/ea_profile.json
* 2023-09-18 03:09:38 (2293) [INFO] Backed up EA4 profile to /tmp/ns87hol8O5/ea_profile.json
* 2023-09-18 03:09:39 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-19 03:08:51 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-19 03:08:51 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-19 03:08:51 (4229) [INFO] 
* 2023-09-19 03:08:51 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-19 03:08:51 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-19 03:08:51 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-19 03:08:51 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-19 03:08:51 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-19 03:08:51 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-19 03:08:51 (4259) [INFO] 
* 2023-09-19 03:08:51 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-19 03:08:51 (4229) [INFO] 
* 2023-09-19 03:09:10 (4242) [INFO] 
* 2023-09-19 03:09:10 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-19 03:09:10 (4259) [INFO] 
* 2023-09-19 03:09:10 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-19 03:09:10 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-19 03:09:39 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-19 03:09:39 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kxVQ96DHLV/ea_profile.json
* 2023-09-19 03:09:40 (2293) [INFO] Backed up EA4 profile to /tmp/kxVQ96DHLV/ea_profile.json
* 2023-09-19 03:09:42 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-20 03:08:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-20 03:08:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-20 03:08:36 (4229) [INFO] 
* 2023-09-20 03:08:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-20 03:08:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-20 03:08:36 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-20 03:08:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-20 03:08:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-20 03:08:36 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-20 03:08:36 (4259) [INFO] 
* 2023-09-20 03:08:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-20 03:08:36 (4229) [INFO] 
* 2023-09-20 03:08:49 (4242) [INFO] 
* 2023-09-20 03:08:49 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-20 03:08:49 (4259) [INFO] 
* 2023-09-20 03:08:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-20 03:08:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-20 03:09:05 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-20 03:09:05 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/U1cUUcobKB/ea_profile.json
* 2023-09-20 03:09:06 (2293) [INFO] Backed up EA4 profile to /tmp/U1cUUcobKB/ea_profile.json
* 2023-09-20 03:09:07 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-21 03:09:12 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-21 03:09:12 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-21 03:09:12 (4229) [INFO] 
* 2023-09-21 03:09:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-21 03:09:13 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-21 03:09:13 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-21 03:09:13 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-21 03:09:13 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-21 03:09:13 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-21 03:09:13 (4259) [INFO] 
* 2023-09-21 03:09:13 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-21 03:09:13 (4229) [INFO] 
* 2023-09-21 03:09:23 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/ad15c9f2d04fb1901f035337111d7a6f781093adb017f2fdcd25895fb99d7551-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-09-21 03:09:23 (4242) [INFO] Trying other mirror.
* 2023-09-21 03:09:26 (4242) [INFO] 
* 2023-09-21 03:09:26 (4242) [INFO] kernel.x86_64                    3.10.0-1160.95.1.el7                    updates
* 2023-09-21 03:09:26 (4259) [INFO] 
* 2023-09-21 03:09:26 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-21 03:09:26 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-21 03:09:43 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-21 03:09:43 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/inrL_avDgz/ea_profile.json
* 2023-09-21 03:09:44 (2293) [INFO] Backed up EA4 profile to /tmp/inrL_avDgz/ea_profile.json
* 2023-09-21 03:09:45 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-22 03:09:19 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-22 03:09:19 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-22 03:09:19 (4229) [INFO] 
* 2023-09-22 03:09:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-22 03:09:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-22 03:09:19 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-22 03:09:19 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-22 03:09:19 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-22 03:09:19 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-22 03:09:20 (4259) [INFO] 
* 2023-09-22 03:09:20 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-22 03:09:20 (4229) [INFO] 
* 2023-09-22 03:09:40 (4242) [INFO] 
* 2023-09-22 03:09:40 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-22 03:09:40 (4259) [INFO] 
* 2023-09-22 03:09:40 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-22 03:09:40 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-22 03:10:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-22 03:10:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/hgxmzpMSXA/ea_profile.json
* 2023-09-22 03:10:02 (2293) [INFO] Backed up EA4 profile to /tmp/hgxmzpMSXA/ea_profile.json
* 2023-09-22 03:10:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-23 03:09:23 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-23 03:09:23 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-23 03:09:23 (4229) [INFO] 
* 2023-09-23 03:09:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-23 03:09:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-23 03:09:23 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-23 03:09:23 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-23 03:09:23 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-23 03:09:23 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-23 03:09:23 (4259) [INFO] 
* 2023-09-23 03:09:23 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-23 03:09:23 (4229) [INFO] 
* 2023-09-23 03:09:37 (4242) [INFO] 
* 2023-09-23 03:09:37 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-23 03:09:37 (4259) [INFO] 
* 2023-09-23 03:09:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-23 03:09:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-23 03:09:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-23 03:09:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8CCBbvHBD9/ea_profile.json
* 2023-09-23 03:09:54 (2293) [INFO] Backed up EA4 profile to /tmp/8CCBbvHBD9/ea_profile.json
* 2023-09-23 03:09:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-24 03:09:25 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-24 03:09:25 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-24 03:09:25 (4229) [INFO] 
* 2023-09-24 03:09:25 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-24 03:09:25 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-24 03:09:25 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-24 03:09:25 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-24 03:09:25 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-24 03:09:25 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-24 03:09:25 (4259) [INFO] 
* 2023-09-24 03:09:25 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-24 03:09:25 (4229) [INFO] 
* 2023-09-24 03:09:44 (4242) [INFO] 
* 2023-09-24 03:09:44 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-24 03:09:44 (4259) [INFO] 
* 2023-09-24 03:09:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-24 03:09:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-24 03:10:01 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-24 03:10:01 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mZY26cSd4C/ea_profile.json
* 2023-09-24 03:10:02 (2293) [INFO] Backed up EA4 profile to /tmp/mZY26cSd4C/ea_profile.json
* 2023-09-24 03:10:03 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-25 03:08:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-25 03:08:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-25 03:08:40 (4229) [INFO] 
* 2023-09-25 03:08:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-25 03:08:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-25 03:08:40 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-25 03:08:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-25 03:08:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-25 03:08:40 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-25 03:08:40 (4259) [INFO] 
* 2023-09-25 03:08:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-25 03:08:40 (4229) [INFO] 
* 2023-09-25 03:09:02 (4242) [INFO] 
* 2023-09-25 03:09:02 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-25 03:09:02 (4259) [INFO] 
* 2023-09-25 03:09:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-25 03:09:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-25 03:09:30 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-25 03:09:30 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/H6XDS7U5YC/ea_profile.json
* 2023-09-25 03:09:31 (2293) [INFO] Backed up EA4 profile to /tmp/H6XDS7U5YC/ea_profile.json
* 2023-09-25 03:09:32 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-26 03:09:16 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-26 03:09:16 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-26 03:09:16 (4229) [INFO] 
* 2023-09-26 03:09:16 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-26 03:09:16 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-26 03:09:16 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-26 03:09:16 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-26 03:09:16 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-26 03:09:16 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-26 03:09:16 (4259) [INFO] 
* 2023-09-26 03:09:16 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-26 03:09:16 (4229) [INFO] 
* 2023-09-26 03:09:35 (4242) [INFO] 
* 2023-09-26 03:09:35 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-26 03:09:35 (4259) [INFO] 
* 2023-09-26 03:09:35 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-26 03:09:35 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-26 03:10:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-26 03:10:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7uwhaVeT96/ea_profile.json
* 2023-09-26 03:10:08 (2293) [INFO] Backed up EA4 profile to /tmp/7uwhaVeT96/ea_profile.json
* 2023-09-26 03:10:10 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-27 03:08:51 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-27 03:08:51 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-27 03:08:51 (4229) [INFO] 
* 2023-09-27 03:08:51 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-27 03:08:52 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-27 03:08:52 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-27 03:08:52 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-27 03:08:52 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-27 03:08:52 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-27 03:08:52 (4259) [INFO] 
* 2023-09-27 03:08:52 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-27 03:08:52 (4229) [INFO] 
* 2023-09-27 03:09:11 (4242) [INFO] 
* 2023-09-27 03:09:11 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-27 03:09:11 (4259) [INFO] 
* 2023-09-27 03:09:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-27 03:09:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-27 03:09:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-27 03:09:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/T3Umn81Kgz/ea_profile.json
* 2023-09-27 03:09:37 (2293) [INFO] Backed up EA4 profile to /tmp/T3Umn81Kgz/ea_profile.json
* 2023-09-27 03:09:38 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-28 03:08:57 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-28 03:08:57 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-28 03:08:57 (4229) [INFO] 
* 2023-09-28 03:08:57 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-28 03:08:57 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-28 03:08:57 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-28 03:08:57 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-28 03:08:57 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-28 03:08:57 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-28 03:08:57 (4259) [INFO] 
* 2023-09-28 03:08:57 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-28 03:08:57 (4229) [INFO] 
* 2023-09-28 03:09:02 (4242) [INFO] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/867c42cdb4e8fb1d93198a3fadbb62d665117aa2ac17eacf64e4a397a39edcd5-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-28 03:09:02 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:02 (4242) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:02 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:04 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-09-28 03:09:04 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:06 (4242) [INFO] http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:06 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:06 (4242) [INFO] http://ftp.plusline.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:06 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:06 (4242) [INFO] http://mirror.netcologne.de/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:06 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:07 (4242) [INFO] http://centos.intergenia.de/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:07 (4242) [INFO] http://centos.mirrors.psw.services/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:07 (4242) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:07 (4242) [INFO] http://centosmirror.netcup.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:07 (4242) [INFO] http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:08 (4242) [INFO] http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:17 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-09-28 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:19 (4242) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-09-28 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:20 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:34 (4242) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-09-28 03:09:34 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:37 (4242) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-09-28 03:09:37 (4242) [INFO] Trying other mirror.
* 2023-09-28 03:09:38 (4242) [INFO] 
* 2023-09-28 03:09:38 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-28 03:09:38 (4259) [INFO] 
* 2023-09-28 03:09:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-28 03:09:38 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-28 03:09:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-28 03:09:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/waQXU7m3TJ/ea_profile.json
* 2023-09-28 03:09:59 (2293) [INFO] Backed up EA4 profile to /tmp/waQXU7m3TJ/ea_profile.json
* 2023-09-28 03:10:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-29 03:08:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-29 03:08:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-29 03:08:40 (4229) [INFO] 
* 2023-09-29 03:08:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-29 03:08:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-29 03:08:40 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-29 03:08:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-29 03:08:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-29 03:08:40 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-29 03:08:40 (4259) [INFO] 
* 2023-09-29 03:08:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-29 03:08:40 (4229) [INFO] 
* 2023-09-29 03:08:57 (4242) [INFO] 
* 2023-09-29 03:08:57 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-29 03:08:57 (4259) [INFO] 
* 2023-09-29 03:08:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-29 03:08:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-29 03:09:33 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-09-29 03:09:33 (1619) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-09-29 03:09:33 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-09-29 03:09:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-29 03:09:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8vOMX2WTqX/ea_profile.json
* 2023-09-29 03:09:34 (2293) [INFO] Backed up EA4 profile to /tmp/8vOMX2WTqX/ea_profile.json
* 2023-09-29 03:09:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-09-30 03:09:31 (1752) [INFO] Checking if your system is up to date: 
* 2023-09-30 03:09:31 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-09-30 03:09:31 (4229) [INFO] 
* 2023-09-30 03:09:31 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-09-30 03:09:31 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-09-30 03:09:31 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-09-30 03:09:31 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-09-30 03:09:31 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-09-30 03:09:31 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-09-30 03:09:31 (4259) [INFO] 
* 2023-09-30 03:09:31 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-09-30 03:09:31 (4229) [INFO] 
* 2023-09-30 03:09:44 (4242) [INFO] 
* 2023-09-30 03:09:44 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-09-30 03:09:44 (4259) [INFO] 
* 2023-09-30 03:09:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-09-30 03:09:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-09-30 03:10:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-09-30 03:10:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DHeth0WcsM/ea_profile.json
* 2023-09-30 03:10:05 (2293) [INFO] Backed up EA4 profile to /tmp/DHeth0WcsM/ea_profile.json
* 2023-09-30 03:10:06 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-01 03:09:28 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-01 03:09:28 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-01 03:09:28 (4229) [INFO] 
* 2023-10-01 03:09:28 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-01 03:09:28 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-01 03:09:28 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-01 03:09:28 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-01 03:09:28 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-01 03:09:28 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-01 03:09:28 (4259) [INFO] 
* 2023-10-01 03:09:28 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-01 03:09:28 (4229) [INFO] 
* 2023-10-01 03:09:41 (4242) [INFO] 
* 2023-10-01 03:09:41 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-01 03:09:41 (4259) [INFO] 
* 2023-10-01 03:09:41 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-01 03:09:41 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-01 03:09:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-01 03:09:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/GfxPZzKMUc/ea_profile.json
* 2023-10-01 03:09:58 (2293) [INFO] Backed up EA4 profile to /tmp/GfxPZzKMUc/ea_profile.json
* 2023-10-01 03:09:59 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-02 03:08:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-02 03:08:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-02 03:08:35 (4229) [INFO] 
* 2023-10-02 03:08:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-02 03:08:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-02 03:08:35 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-02 03:08:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-02 03:08:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-02 03:08:35 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-02 03:08:35 (4259) [INFO] 
* 2023-10-02 03:08:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-02 03:08:35 (4229) [INFO] 
* 2023-10-02 03:08:49 (4242) [INFO] 
* 2023-10-02 03:08:49 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-02 03:08:49 (4259) [INFO] 
* 2023-10-02 03:08:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-02 03:08:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-02 03:09:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-02 03:09:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YGew7NvBus/ea_profile.json
* 2023-10-02 03:09:04 (2293) [INFO] Backed up EA4 profile to /tmp/YGew7NvBus/ea_profile.json
* 2023-10-02 03:09:06 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-03 03:10:09 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-03 03:10:09 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-03 03:10:09 (4229) [INFO] 
* 2023-10-03 03:10:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-03 03:10:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-03 03:10:09 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-03 03:10:09 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-03 03:10:09 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-03 03:10:09 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-03 03:10:09 (4259) [INFO] 
* 2023-10-03 03:10:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-03 03:10:09 (4229) [INFO] 
* 2023-10-03 03:10:24 (4242) [INFO] 
* 2023-10-03 03:10:24 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-03 03:10:24 (4259) [INFO] 
* 2023-10-03 03:10:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-03 03:10:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-03 03:10:41 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-03 03:10:41 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Q3xLEw77CS/ea_profile.json
* 2023-10-03 03:10:42 (2293) [INFO] Backed up EA4 profile to /tmp/Q3xLEw77CS/ea_profile.json
* 2023-10-03 03:10:43 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-04 03:09:09 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-04 03:09:09 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-04 03:09:09 (4229) [INFO] 
* 2023-10-04 03:09:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-04 03:09:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-04 03:09:09 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-04 03:09:09 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-04 03:09:09 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-04 03:09:09 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-04 03:09:09 (4259) [INFO] 
* 2023-10-04 03:09:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-04 03:09:09 (4229) [INFO] 
* 2023-10-04 03:09:32 (4242) [INFO] 
* 2023-10-04 03:09:32 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-04 03:09:32 (4259) [INFO] 
* 2023-10-04 03:09:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-04 03:09:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-04 03:09:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-04 03:09:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/x169p4cGH4/ea_profile.json
* 2023-10-04 03:09:50 (2293) [INFO] Backed up EA4 profile to /tmp/x169p4cGH4/ea_profile.json
* 2023-10-04 03:09:52 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-05 03:08:58 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-05 03:08:58 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-05 03:08:58 (4229) [INFO] 
* 2023-10-05 03:08:58 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-05 03:08:58 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-05 03:08:58 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-05 03:08:58 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-05 03:08:58 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-05 03:08:58 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-05 03:08:58 (4259) [INFO] 
* 2023-10-05 03:08:58 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-05 03:08:58 (4229) [INFO] 
* 2023-10-05 03:09:05 (4242) [INFO] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:05 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:07 (4242) [INFO] https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:07 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:07 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/wp-toolkit/repodata/a83fed44c9a0c43597f384a9ef5c71f4f028eeb4994f8b16c67622525d957b48-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:07 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.10/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:07 (4242) [INFO] http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:07 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] http://mirror.junda.nl/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] http://mirror.checkdomain.de/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:08 (4242) [INFO] http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:08 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:09 (4242) [INFO] http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:09 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:09 (4242) [INFO] http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:09 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:09 (4242) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/28404c45013d637a17160a5cbc7b6fd35b3c5d85260c70efd28ea3d23c389a85-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:09 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:14 (4242) [INFO] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-10-05 03:09:14 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:15 (4242) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-10-05 03:09:15 (4242) [INFO] Trying other mirror.
* 2023-10-05 03:09:22 (4242) [INFO] 
* 2023-10-05 03:09:22 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-05 03:09:22 (4259) [INFO] 
* 2023-10-05 03:09:22 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-05 03:09:22 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-05 03:09:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-05 03:09:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UcXNNATH9s/ea_profile.json
* 2023-10-05 03:09:41 (2293) [INFO] Backed up EA4 profile to /tmp/UcXNNATH9s/ea_profile.json
* 2023-10-05 03:09:42 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-06 03:08:42 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-06 03:08:42 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-06 03:08:42 (4229) [INFO] 
* 2023-10-06 03:08:42 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-06 03:08:42 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-06 03:08:42 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-06 03:08:42 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-06 03:08:42 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-06 03:08:42 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-06 03:08:42 (4259) [INFO] 
* 2023-10-06 03:08:42 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-06 03:08:42 (4229) [INFO] 
* 2023-10-06 03:08:57 (4242) [INFO] 
* 2023-10-06 03:08:57 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-06 03:08:57 (4259) [INFO] 
* 2023-10-06 03:08:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-06 03:08:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-06 03:09:36 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-06 03:09:36 (1619) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/d94547f51b1f5921d263724db0a646b3a9e297d687603a8fbdf9d03e4904f7bc-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-10-06 03:09:36 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-06 03:09:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-06 03:09:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0KHkqGB_Vg/ea_profile.json
* 2023-10-06 03:09:48 (2293) [INFO] Backed up EA4 profile to /tmp/0KHkqGB_Vg/ea_profile.json
* 2023-10-06 03:09:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-07 03:09:19 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-07 03:09:19 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-07 03:09:19 (4229) [INFO] 
* 2023-10-07 03:09:19 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-07 03:09:19 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-07 03:09:19 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-07 03:09:19 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-07 03:09:19 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-07 03:09:19 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-07 03:09:19 (4259) [INFO] 
* 2023-10-07 03:09:19 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-07 03:09:19 (4229) [INFO] 
* 2023-10-07 03:09:33 (4242) [INFO] 
* 2023-10-07 03:09:33 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-07 03:09:33 (4259) [INFO] 
* 2023-10-07 03:09:33 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-07 03:09:33 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-07 03:09:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-07 03:09:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sz1tQkg5lG/ea_profile.json
* 2023-10-07 03:09:49 (2293) [INFO] Backed up EA4 profile to /tmp/sz1tQkg5lG/ea_profile.json
* 2023-10-07 03:09:50 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-08 03:09:17 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-08 03:09:17 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-08 03:09:17 (4229) [INFO] 
* 2023-10-08 03:09:17 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-08 03:09:17 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-08 03:09:17 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-08 03:09:17 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-08 03:09:17 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-08 03:09:17 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-08 03:09:17 (4259) [INFO] 
* 2023-10-08 03:09:17 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-08 03:09:17 (4229) [INFO] 
* 2023-10-08 03:09:36 (4242) [INFO] 
* 2023-10-08 03:09:36 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-08 03:09:36 (4259) [INFO] 
* 2023-10-08 03:09:36 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-08 03:09:36 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-08 03:09:52 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-08 03:09:52 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/q3LxHoCkBv/ea_profile.json
* 2023-10-08 03:09:53 (2293) [INFO] Backed up EA4 profile to /tmp/q3LxHoCkBv/ea_profile.json
* 2023-10-08 03:09:54 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-09 03:08:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-09 03:08:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-09 03:08:36 (4229) [INFO] 
* 2023-10-09 03:08:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-09 03:08:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-09 03:08:36 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-09 03:08:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-09 03:08:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-09 03:08:36 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-09 03:08:36 (4259) [INFO] 
* 2023-10-09 03:08:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-09 03:08:36 (4229) [INFO] 
* 2023-10-09 03:08:49 (4242) [INFO] 
* 2023-10-09 03:08:49 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-09 03:08:49 (4259) [INFO] 
* 2023-10-09 03:08:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-09 03:08:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-09 03:09:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-09 03:09:10 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/QCHEdJt_on/ea_profile.json
* 2023-10-09 03:09:11 (2293) [INFO] Backed up EA4 profile to /tmp/QCHEdJt_on/ea_profile.json
* 2023-10-09 03:09:12 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-10 03:09:58 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-10 03:09:58 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-10 03:09:58 (4229) [INFO] 
* 2023-10-10 03:09:59 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-10 03:09:59 (4242) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 25260.
* 2023-10-10 03:09:59 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:09:59 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:09:59 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:09:59 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 00:51 ago
* 2023-10-10 03:09:59 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:01 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:01 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:01 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:01 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 00:53 ago
* 2023-10-10 03:10:01 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:03 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:03 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:03 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:03 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 00:55 ago
* 2023-10-10 03:10:03 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:05 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:05 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:05 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:05 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 00:57 ago
* 2023-10-10 03:10:05 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:07 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:07 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:07 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:07 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 00:59 ago
* 2023-10-10 03:10:07 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:09 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:09 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:09 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:09 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:01 ago
* 2023-10-10 03:10:09 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:11 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:11 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:11 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:11 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:03 ago
* 2023-10-10 03:10:11 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:13 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:13 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:13 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:13 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:05 ago
* 2023-10-10 03:10:13 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:15 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:15 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:15 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:15 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:07 ago
* 2023-10-10 03:10:15 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:17 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:17 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:17 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:17 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:09 ago
* 2023-10-10 03:10:17 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:19 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:19 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:19 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:19 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:11 ago
* 2023-10-10 03:10:19 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:21 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:21 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:21 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:21 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:13 ago
* 2023-10-10 03:10:21 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:23 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:23 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:23 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:23 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:15 ago
* 2023-10-10 03:10:23 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:25 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:25 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:25 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:25 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:17 ago
* 2023-10-10 03:10:25 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:27 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:27 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:27 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:27 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:19 ago
* 2023-10-10 03:10:27 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:29 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:29 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:29 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:29 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:21 ago
* 2023-10-10 03:10:29 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:31 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:31 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:31 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:31 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:23 ago
* 2023-10-10 03:10:31 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:33 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:33 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:33 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:33 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:25 ago
* 2023-10-10 03:10:33 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:35 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:35 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:35 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:35 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:27 ago
* 2023-10-10 03:10:35 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:37 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:37 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:37 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:37 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:29 ago
* 2023-10-10 03:10:37 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:39 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:39 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:39 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:39 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:31 ago
* 2023-10-10 03:10:39 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:41 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:41 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:41 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:41 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:33 ago
* 2023-10-10 03:10:41 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:43 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:43 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:43 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:43 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:35 ago
* 2023-10-10 03:10:43 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:45 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:45 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:45 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:45 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:37 ago
* 2023-10-10 03:10:45 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:47 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:47 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:47 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:47 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:39 ago
* 2023-10-10 03:10:47 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:49 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:49 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:49 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:49 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:41 ago
* 2023-10-10 03:10:49 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:51 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:51 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:51 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:51 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:43 ago
* 2023-10-10 03:10:51 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:53 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:53 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:53 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:53 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:45 ago
* 2023-10-10 03:10:53 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:55 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:55 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:55 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:55 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:47 ago
* 2023-10-10 03:10:55 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:57 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:57 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:57 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:57 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:49 ago
* 2023-10-10 03:10:57 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:10:59 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:10:59 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:10:59 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:10:59 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:51 ago
* 2023-10-10 03:10:59 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:01 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:01 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:01 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:01 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:53 ago
* 2023-10-10 03:11:01 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:03 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:03 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:03 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:03 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:55 ago
* 2023-10-10 03:11:03 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:05 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:05 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:05 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:05 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:57 ago
* 2023-10-10 03:11:05 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:07 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:07 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:07 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:07 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 01:59 ago
* 2023-10-10 03:11:07 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:09 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:09 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:09 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:09 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 02:01 ago
* 2023-10-10 03:11:09 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:11 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:11 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:11 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:11 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 02:03 ago
* 2023-10-10 03:11:11 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:13 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:13 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:13 (4242) [INFO]     Memory :  29 M RSS (3.3 GB VSZ)
* 2023-10-10 03:11:13 (4242) [INFO]     Started: Tue Oct 10 03:09:08 2023 - 02:05 ago
* 2023-10-10 03:11:13 (4242) [INFO]     State  : Sleeping, pid: 25260
* 2023-10-10 03:11:15 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-10 03:11:15 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-10 03:11:15 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-10 03:11:15 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-10 03:11:15 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-10 03:11:15 (4242) [INFO] Cleaning up list of fastest mirrors
* 2023-10-10 03:11:15 (4259) [INFO] 
* 2023-10-10 03:11:15 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-10 03:11:15 (4229) [INFO] 
* 2023-10-10 03:11:15 (4242) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 25925.
* 2023-10-10 03:11:15 (4242) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2023-10-10 03:11:15 (4242) [INFO]   The other application is: yum
* 2023-10-10 03:11:15 (4242) [INFO]     Memory :  43 M RSS (366 MB VSZ)
* 2023-10-10 03:11:15 (4242) [INFO]     Started: Tue Oct 10 03:10:01 2023 - 01:14 ago
* 2023-10-10 03:11:15 (4242) [INFO]     State  : Running, pid: 25925
* 2023-10-10 03:11:25 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-10-10 03:11:25 (4242) [INFO] Trying other mirror.
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]  One of the configured repositories failed (EL-7 - Imunify360),
* 2023-10-10 03:11:25 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-10 03:11:25 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-10 03:11:25 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-10 03:11:25 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-10 03:11:25 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-10 03:11:25 (4242) [INFO]             yum --disablerepo=imunify360 ...
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-10 03:11:25 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-10 03:11:25 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]             yum-config-manager --disable imunify360
* 2023-10-10 03:11:25 (4242) [INFO]         or
* 2023-10-10 03:11:25 (4242) [INFO]             subscription-manager repos --disable=imunify360
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-10 03:11:25 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-10 03:11:25 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-10 03:11:25 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-10 03:11:25 (4242) [INFO]         compromise:
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO]             yum-config-manager --save --setopt=imunify360.skip_if_unavailable=true
* 2023-10-10 03:11:25 (4242) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO] failure: repodata/repomd.xml from imunify360: [Errno 256] No more mirrors to try.
* 2023-10-10 03:11:25 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-10-10 03:11:25 (4259) [INFO] 
* 2023-10-10 03:11:25 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-10 03:11:25 (1773) [INFO] Checking /scripts/sysup
* 2023-10-10 03:11:25 (4228) [INFO] Running: /scripts/sysup
* 2023-10-10 03:11:25 (4229) [INFO] 
* 2023-10-10 03:11:25 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-10-10 03:11:25 (4242) [INFO]   All Needed Packages are already installed.
* 2023-10-10 03:11:25 (4259) [INFO] 
* 2023-10-10 03:14:33 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-10 03:14:33 (1619) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f123ea06834675570ffbe22edff4a2ac6d0fae0ceeed79c4cfa98746d2e30d79-filelists.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/f123ea06834675570ffbe22edff4a2ac6d0fae0ceeed79c4cfa98746d2e30d79-filelists.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-10-10 03:14:33 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-10 03:14:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-10 03:14:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/yHQPpcYPae/ea_profile.json
* 2023-10-10 03:14:34 (2293) [INFO] Backed up EA4 profile to /tmp/yHQPpcYPae/ea_profile.json
* 2023-10-10 03:14:35 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-11 03:08:45 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-11 03:08:45 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-11 03:08:45 (4229) [INFO] 
* 2023-10-11 03:08:45 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-11 03:08:45 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-11 03:08:45 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-11 03:08:45 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-11 03:08:45 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-11 03:08:45 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-11 03:08:45 (4259) [INFO] 
* 2023-10-11 03:08:45 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-11 03:08:45 (4229) [INFO] 
* 2023-10-11 03:09:01 (4242) [INFO] 
* 2023-10-11 03:09:01 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-11 03:09:01 (4259) [INFO] 
* 2023-10-11 03:09:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-11 03:09:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-11 03:10:00 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-11 03:10:00 (1619) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/20954a0a68c3b47970e23e6af58cf553f2bf2c73e859b05838cecb1369457606-other.sqlite.bz2: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/20954a0a68c3b47970e23e6af58cf553f2bf2c73e859b05838cecb1369457606-other.sqlite.bz2: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2023-10-11 03:10:00 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-11 03:10:00 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-11 03:10:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0nu8zPN6nj/ea_profile.json
* 2023-10-11 03:10:01 (2293) [INFO] Backed up EA4 profile to /tmp/0nu8zPN6nj/ea_profile.json
* 2023-10-11 03:10:02 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-12 03:08:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-12 03:08:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-12 03:08:37 (4229) [INFO] 
* 2023-10-12 03:08:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-12 03:08:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-12 03:08:37 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-12 03:08:37 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-12 03:08:37 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-12 03:08:37 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-12 03:08:37 (4259) [INFO] 
* 2023-10-12 03:08:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-12 03:08:37 (4229) [INFO] 
* 2023-10-12 03:08:53 (4242) [INFO] 
* 2023-10-12 03:08:53 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-12 03:08:53 (4259) [INFO] 
* 2023-10-12 03:08:53 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-12 03:08:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-12 03:09:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-12 03:09:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_wa1ENeKZ0/ea_profile.json
* 2023-10-12 03:09:12 (2293) [INFO] Backed up EA4 profile to /tmp/_wa1ENeKZ0/ea_profile.json
* 2023-10-12 03:09:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-13 03:09:04 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-13 03:09:04 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-13 03:09:04 (4229) [INFO] 
* 2023-10-13 03:09:04 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-13 03:09:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-13 03:09:05 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-13 03:09:05 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-13 03:09:05 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-13 03:09:05 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-13 03:09:05 (4259) [INFO] 
* 2023-10-13 03:09:05 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-13 03:09:05 (4229) [INFO] 
* 2023-10-13 03:09:37 (4242) [INFO] 
* 2023-10-13 03:09:37 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-13 03:09:37 (4259) [INFO] 
* 2023-10-13 03:09:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-13 03:09:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-13 03:09:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-13 03:09:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/K8wy5qcAIm/ea_profile.json
* 2023-10-13 03:09:58 (2293) [INFO] Backed up EA4 profile to /tmp/K8wy5qcAIm/ea_profile.json
* 2023-10-13 03:09:59 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-14 03:09:23 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-14 03:09:23 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-14 03:09:23 (4229) [INFO] 
* 2023-10-14 03:09:23 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-14 03:09:23 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-14 03:09:23 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-14 03:09:23 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-14 03:09:23 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-14 03:09:23 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-14 03:09:23 (4259) [INFO] 
* 2023-10-14 03:09:23 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-14 03:09:23 (4229) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]  One of the configured repositories failed (Unknown),
* 2023-10-14 03:09:32 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-14 03:09:32 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-14 03:09:32 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-14 03:09:32 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-14 03:09:32 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-14 03:09:32 (4242) [INFO]             yum --disablerepo=<repoid> ...
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-14 03:09:32 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-14 03:09:32 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]             yum-config-manager --disable <repoid>
* 2023-10-14 03:09:32 (4242) [INFO]         or
* 2023-10-14 03:09:32 (4242) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-14 03:09:32 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-14 03:09:32 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-14 03:09:32 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-14 03:09:32 (4242) [INFO]         compromise:
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-10-14 03:09:32 (4242) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO] file is encrypted or is not a database
* 2023-10-14 03:09:32 (4259) [INFO] 
* 2023-10-14 03:09:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-14 03:09:32 (1773) [INFO] Checking /scripts/sysup
* 2023-10-14 03:09:32 (4228) [INFO] Running: /scripts/sysup
* 2023-10-14 03:09:32 (4229) [INFO] 
* 2023-10-14 03:09:32 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-10-14 03:09:32 (4242) [INFO]   All Needed Packages are already installed.
* 2023-10-14 03:09:32 (4259) [INFO] 
* 2023-10-14 03:09:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-14 03:09:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JlYrlOCBQ0/ea_profile.json
* 2023-10-14 03:09:49 (2293) [INFO] Backed up EA4 profile to /tmp/JlYrlOCBQ0/ea_profile.json
* 2023-10-14 03:09:50 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-10-15 03:09:23 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-15 03:09:23 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-15 03:09:23 (4229) [INFO] 
* 2023-10-15 03:09:24 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-15 03:09:24 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-15 03:09:24 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-15 03:09:24 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-15 03:09:24 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-15 03:09:24 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-15 03:09:24 (4259) [INFO] 
* 2023-10-15 03:09:24 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-15 03:09:24 (4229) [INFO] 
* 2023-10-15 03:09:38 (4242) [INFO] 
* 2023-10-15 03:09:38 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-15 03:09:38 (4259) [INFO] 
* 2023-10-15 03:09:38 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-15 03:09:38 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-15 03:09:55 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-15 03:09:55 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d_eG6poRz1/ea_profile.json
* 2023-10-15 03:09:56 (2293) [INFO] Backed up EA4 profile to /tmp/d_eG6poRz1/ea_profile.json
* 2023-10-15 03:09:57 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-16 03:08:34 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-16 03:08:34 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-16 03:08:34 (4229) [INFO] 
* 2023-10-16 03:08:34 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-16 03:08:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-16 03:08:35 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-16 03:08:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-16 03:08:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-16 03:08:35 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-16 03:08:35 (4259) [INFO] 
* 2023-10-16 03:08:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-16 03:08:35 (4229) [INFO] 
* 2023-10-16 03:08:48 (4242) [INFO] 
* 2023-10-16 03:08:48 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-16 03:08:48 (4259) [INFO] 
* 2023-10-16 03:08:48 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-16 03:08:48 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-16 03:09:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-16 03:09:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R9_uyFMMW8/ea_profile.json
* 2023-10-16 03:09:03 (2293) [INFO] Backed up EA4 profile to /tmp/R9_uyFMMW8/ea_profile.json
* 2023-10-16 03:09:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-17 03:08:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-17 03:08:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-17 03:08:38 (4229) [INFO] 
* 2023-10-17 03:08:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-17 03:08:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-17 03:08:39 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-17 03:08:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-17 03:08:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-17 03:08:39 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-17 03:08:39 (4259) [INFO] 
* 2023-10-17 03:08:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-17 03:08:39 (4229) [INFO] 
* 2023-10-17 03:08:56 (4242) [INFO] 
* 2023-10-17 03:08:56 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-17 03:08:56 (4259) [INFO] 
* 2023-10-17 03:08:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-17 03:08:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-17 03:09:32 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-17 03:09:32 (1619) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-10-17 03:09:32 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-17 03:09:33 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-17 03:09:33 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pS9nBJbJWg/ea_profile.json
* 2023-10-17 03:09:33 (2293) [INFO] Backed up EA4 profile to /tmp/pS9nBJbJWg/ea_profile.json
* 2023-10-17 03:09:34 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-18 03:08:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-18 03:08:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-18 03:08:36 (4229) [INFO] 
* 2023-10-18 03:08:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-18 03:08:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-18 03:08:37 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-18 03:08:37 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-18 03:08:37 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-18 03:08:37 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-18 03:08:37 (4259) [INFO] 
* 2023-10-18 03:08:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-18 03:08:37 (4229) [INFO] 
* 2023-10-18 03:08:55 (4242) [INFO] 
* 2023-10-18 03:08:55 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-18 03:08:55 (4259) [INFO] 
* 2023-10-18 03:08:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-18 03:08:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-18 03:09:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-18 03:09:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pc7QqC1GVF/ea_profile.json
* 2023-10-18 03:09:14 (2293) [INFO] Backed up EA4 profile to /tmp/pc7QqC1GVF/ea_profile.json
* 2023-10-18 03:09:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-19 03:09:13 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-19 03:09:13 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-19 03:09:13 (4229) [INFO] 
* 2023-10-19 03:09:13 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-19 03:09:13 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-19 03:09:13 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-19 03:09:13 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-19 03:09:13 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-19 03:09:13 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-19 03:09:13 (4259) [INFO] 
* 2023-10-19 03:09:13 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-19 03:09:13 (4229) [INFO] 
* 2023-10-19 03:09:23 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-10-19 03:09:23 (4242) [INFO] Trying other mirror.
* 2023-10-19 03:09:23 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-10-19 03:09:23 (4242) [INFO] Trying other mirror.
* 2023-10-19 03:09:23 (4242) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-10-19 03:09:23 (4242) [INFO] Trying other mirror.
* 2023-10-19 03:09:24 (4242) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-10-19 03:09:24 (4242) [INFO] Trying other mirror.
* 2023-10-19 03:09:24 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/1a7a805d418bc96c3e2c0937acd622c8da22353bc8676f902bdca8b16d106542-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-10-19 03:09:24 (4242) [INFO] Trying other mirror.
* 2023-10-19 03:09:28 (4242) [INFO] 
* 2023-10-19 03:09:28 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-19 03:09:28 (4259) [INFO] 
* 2023-10-19 03:09:28 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-19 03:09:28 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-19 03:09:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-19 03:09:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Fv5qCKwMe_/ea_profile.json
* 2023-10-19 03:09:42 (2293) [INFO] Backed up EA4 profile to /tmp/Fv5qCKwMe_/ea_profile.json
* 2023-10-19 03:09:44 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-20 03:15:54 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-20 03:15:54 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-20 03:15:54 (4229) [INFO] 
* 2023-10-20 03:15:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-20 03:15:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-20 03:15:54 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-20 03:15:54 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-20 03:15:54 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-20 03:15:54 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-20 03:15:54 (4259) [INFO] 
* 2023-10-20 03:15:54 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-20 03:15:54 (4229) [INFO] 
* 2023-10-20 03:17:37 (4242) [INFO] 
* 2023-10-20 03:17:37 (4242) [INFO] kernel.x86_64                    3.10.0-1160.99.1.el7                    updates
* 2023-10-20 03:17:37 (4259) [INFO] 
* 2023-10-20 03:17:37 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-20 03:17:37 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-20 03:19:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-20 03:19:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iQmJ0ph_T8/ea_profile.json
* 2023-10-20 03:19:54 (2293) [INFO] Backed up EA4 profile to /tmp/iQmJ0ph_T8/ea_profile.json
* 2023-10-20 03:19:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-21 03:10:18 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-21 03:10:18 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-21 03:10:18 (4229) [INFO] 
* 2023-10-21 03:10:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-21 03:10:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-21 03:10:18 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-21 03:10:18 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-21 03:10:18 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-21 03:10:18 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-21 03:10:18 (4259) [INFO] 
* 2023-10-21 03:10:18 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-21 03:10:18 (4229) [INFO] 
* 2023-10-21 03:10:32 (4242) [INFO] 
* 2023-10-21 03:10:32 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-21 03:10:32 (4259) [INFO] 
* 2023-10-21 03:10:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-21 03:10:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-21 03:10:48 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-21 03:10:48 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PRCtz4LLuv/ea_profile.json
* 2023-10-21 03:10:49 (2293) [INFO] Backed up EA4 profile to /tmp/PRCtz4LLuv/ea_profile.json
* 2023-10-21 03:10:50 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-22 03:09:12 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-22 03:09:12 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-22 03:09:12 (4229) [INFO] 
* 2023-10-22 03:09:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-22 03:09:12 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-22 03:09:12 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-22 03:09:12 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-22 03:09:12 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-22 03:09:12 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-22 03:09:12 (4259) [INFO] 
* 2023-10-22 03:09:12 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-22 03:09:12 (4229) [INFO] 
* 2023-10-22 03:09:32 (4242) [INFO] Traceback (most recent call last):
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-10-22 03:09:32 (4242) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-10-22 03:09:32 (4242) [INFO]     errcode = main(args)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-10-22 03:09:32 (4242) [INFO]     result, resultmsgs = base.doCommands()
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-10-22 03:09:32 (4242) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-10-22 03:09:32 (4242) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-10-22 03:09:32 (4242) [INFO]     ignore_case=True, repoid=repoid)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-10-22 03:09:32 (4242) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-10-22 03:09:32 (4242) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-10-22 03:09:32 (4242) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-10-22 03:09:32 (4242) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-10-22 03:09:32 (4242) [INFO]     self.repos.populateSack(which=repos)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack
* 2023-10-22 03:09:32 (4242) [INFO]     sack.populate(repo, mdtype, callback, cacheonly)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 242, in populate
* 2023-10-22 03:09:32 (4242) [INFO]     mydbtype)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-10-22 03:09:32 (4242) [INFO]     cached=repo.cache)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-10-22 03:09:32 (4242) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-10-22 03:09:32 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-10-22 03:09:32 (4242) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-10-22 03:09:32 (4242) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite'
* 2023-10-22 03:09:32 (4259) [INFO] 
* 2023-10-22 03:09:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-22 03:09:32 (1773) [INFO] Checking /scripts/sysup
* 2023-10-22 03:09:32 (4228) [INFO] Running: /scripts/sysup
* 2023-10-22 03:09:32 (4229) [INFO] 
* 2023-10-22 03:09:32 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-10-22 03:09:33 (4242) [INFO]   All Needed Packages are already installed.
* 2023-10-22 03:09:33 (4259) [INFO] 
* 2023-10-22 03:09:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-22 03:09:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YfVGZnCWHx/ea_profile.json
* 2023-10-22 03:09:52 (2293) [INFO] Backed up EA4 profile to /tmp/YfVGZnCWHx/ea_profile.json
* 2023-10-22 03:09:53 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-10-23 03:08:39 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-23 03:08:39 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-23 03:08:39 (4229) [INFO] 
* 2023-10-23 03:08:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-23 03:08:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-23 03:08:39 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-23 03:08:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-23 03:08:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-23 03:08:39 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-23 03:08:39 (4259) [INFO] 
* 2023-10-23 03:08:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-23 03:08:39 (4229) [INFO] 
* 2023-10-23 03:08:52 (4242) [INFO] 
* 2023-10-23 03:08:52 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-23 03:08:52 (4259) [INFO] 
* 2023-10-23 03:08:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-23 03:08:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-23 03:09:06 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-23 03:09:06 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dhZaAl3sS_/ea_profile.json
* 2023-10-23 03:09:07 (2293) [INFO] Backed up EA4 profile to /tmp/dhZaAl3sS_/ea_profile.json
* 2023-10-23 03:09:08 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-24 03:08:39 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-24 03:08:39 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-24 03:08:39 (4229) [INFO] 
* 2023-10-24 03:08:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-24 03:08:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-24 03:08:39 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-24 03:08:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-24 03:08:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-24 03:08:39 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-24 03:08:39 (4259) [INFO] 
* 2023-10-24 03:08:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-24 03:08:39 (4229) [INFO] 
* 2023-10-24 03:08:54 (4242) [INFO] 
* 2023-10-24 03:08:54 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-24 03:08:55 (4259) [INFO] 
* 2023-10-24 03:08:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-24 03:08:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-24 03:09:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-24 03:09:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fAVh3Jredp/ea_profile.json
* 2023-10-24 03:09:10 (2293) [INFO] Backed up EA4 profile to /tmp/fAVh3Jredp/ea_profile.json
* 2023-10-24 03:09:11 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-25 03:08:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-25 03:08:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-25 03:08:36 (4229) [INFO] 
* 2023-10-25 03:08:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-25 03:08:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-25 03:08:36 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-25 03:08:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-25 03:08:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-25 03:08:36 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-25 03:08:36 (4259) [INFO] 
* 2023-10-25 03:08:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-25 03:08:36 (4229) [INFO] 
* 2023-10-25 03:08:52 (4242) [INFO] 
* 2023-10-25 03:08:52 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-25 03:08:52 (4259) [INFO] 
* 2023-10-25 03:08:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-25 03:08:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-25 03:09:08 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-25 03:09:08 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jm3NXrToW5/ea_profile.json
* 2023-10-25 03:09:08 (2293) [INFO] Backed up EA4 profile to /tmp/jm3NXrToW5/ea_profile.json
* 2023-10-25 03:09:10 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-26 03:09:05 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-26 03:09:05 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-26 03:09:05 (4229) [INFO] 
* 2023-10-26 03:09:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-26 03:09:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-26 03:09:06 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-26 03:09:06 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-26 03:09:06 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-26 03:09:06 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-26 03:09:06 (4259) [INFO] 
* 2023-10-26 03:09:06 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-26 03:09:06 (4229) [INFO] 
* 2023-10-26 03:09:34 (4242) [INFO] 
* 2023-10-26 03:09:34 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-26 03:09:34 (4259) [INFO] 
* 2023-10-26 03:09:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-26 03:09:34 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-26 03:09:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-26 03:09:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/91bFeIuwyR/ea_profile.json
* 2023-10-26 03:09:54 (2293) [INFO] Backed up EA4 profile to /tmp/91bFeIuwyR/ea_profile.json
* 2023-10-26 03:09:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-27 03:08:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-27 03:08:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-27 03:08:49 (4229) [INFO] 
* 2023-10-27 03:08:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-27 03:08:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-27 03:08:49 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-27 03:08:49 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-27 03:08:49 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-27 03:08:49 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-27 03:08:49 (4259) [INFO] 
* 2023-10-27 03:08:49 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-27 03:08:49 (4229) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]  One of the configured repositories failed (Unknown),
* 2023-10-27 03:09:11 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-10-27 03:09:11 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-10-27 03:09:11 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-10-27 03:09:11 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-10-27 03:09:11 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-10-27 03:09:11 (4242) [INFO]             yum --disablerepo=<repoid> ...
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-10-27 03:09:11 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-10-27 03:09:11 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]             yum-config-manager --disable <repoid>
* 2023-10-27 03:09:11 (4242) [INFO]         or
* 2023-10-27 03:09:11 (4242) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-10-27 03:09:11 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-10-27 03:09:11 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-10-27 03:09:11 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-10-27 03:09:11 (4242) [INFO]         compromise:
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-10-27 03:09:11 (4242) [INFO] 
* 2023-10-27 03:09:11 (4242) [INFO] updates: Check uncompressed DB failed
* 2023-10-27 03:09:11 (4259) [INFO] 
* 2023-10-27 03:09:11 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-27 03:09:11 (1773) [INFO] Checking /scripts/sysup
* 2023-10-27 03:09:11 (4228) [INFO] Running: /scripts/sysup
* 2023-10-27 03:09:11 (4229) [INFO] 
* 2023-10-27 03:09:12 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-10-27 03:09:12 (4242) [INFO]   All Needed Packages are already installed.
* 2023-10-27 03:09:12 (4259) [INFO] 
* 2023-10-27 03:09:53 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-27 03:09:53 (1619) [ERROR] Existing lock /var/run/yum.pid: another copy is running as pid 17095.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  26 M RSS (420 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:06 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  29 M RSS (427 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:08 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  30 M RSS (427 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:10 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  30 M RSS (427 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:12 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  30 M RSS (427 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:14 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  30 M RSS (427 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:16 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  30 M RSS (427 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:18 ago
    State  : Sleeping, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (433 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:20 ago
    State  : Running, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  35 M RSS (433 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:22 ago
    State  : Running, pid: 17095
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  77 M RSS (473 MB VSZ)
    Started: Fri Oct 27 03:09:06 2023 - 00:24 ago
    State  : Running, pid: 17095
* 2023-10-27 03:09:53 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-27 03:09:53 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-27 03:09:53 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AgswBs491h/ea_profile.json
* 2023-10-27 03:09:54 (2293) [INFO] Backed up EA4 profile to /tmp/AgswBs491h/ea_profile.json
* 2023-10-27 03:09:55 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-28 03:09:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-28 03:09:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-28 03:09:49 (4229) [INFO] 
* 2023-10-28 03:09:50 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-28 03:09:50 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-28 03:09:50 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-28 03:09:50 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-28 03:09:50 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-28 03:09:50 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-28 03:09:50 (4259) [INFO] 
* 2023-10-28 03:09:50 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-28 03:09:50 (4229) [INFO] 
* 2023-10-28 03:10:03 (4242) [INFO] 
* 2023-10-28 03:10:03 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-28 03:10:03 (4259) [INFO] 
* 2023-10-28 03:10:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-28 03:10:03 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-28 03:10:18 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-28 03:10:18 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JkdCJxxCc3/ea_profile.json
* 2023-10-28 03:10:19 (2293) [INFO] Backed up EA4 profile to /tmp/JkdCJxxCc3/ea_profile.json
* 2023-10-28 03:10:20 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-29 03:09:06 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-29 03:09:06 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-29 03:09:06 (4229) [INFO] 
* 2023-10-29 03:09:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-29 03:09:07 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-29 03:09:07 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-29 03:09:07 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-29 03:09:07 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-29 03:09:07 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-29 03:09:07 (4259) [INFO] 
* 2023-10-29 03:09:07 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-29 03:09:07 (4229) [INFO] 
* 2023-10-29 03:09:23 (4242) [INFO] 
* 2023-10-29 03:09:23 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-29 03:09:24 (4259) [INFO] 
* 2023-10-29 03:09:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-29 03:09:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-29 03:09:44 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-29 03:09:44 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/xSfUT5rTs_/ea_profile.json
* 2023-10-29 03:09:45 (2293) [INFO] Backed up EA4 profile to /tmp/xSfUT5rTs_/ea_profile.json
* 2023-10-29 03:09:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-30 03:08:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-30 03:08:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-30 03:08:37 (4229) [INFO] 
* 2023-10-30 03:08:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-30 03:08:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-30 03:08:37 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-30 03:08:37 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-30 03:08:37 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-30 03:08:37 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-30 03:08:37 (4259) [INFO] 
* 2023-10-30 03:08:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-30 03:08:37 (4229) [INFO] 
* 2023-10-30 03:08:50 (4242) [INFO] 
* 2023-10-30 03:08:50 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-30 03:08:50 (4259) [INFO] 
* 2023-10-30 03:08:50 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-30 03:08:50 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-30 03:09:05 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-30 03:09:05 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/sL3Ys9MUtg/ea_profile.json
* 2023-10-30 03:09:05 (2293) [INFO] Backed up EA4 profile to /tmp/sL3Ys9MUtg/ea_profile.json
* 2023-10-30 03:09:07 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-10-31 03:09:05 (1752) [INFO] Checking if your system is up to date: 
* 2023-10-31 03:09:05 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-10-31 03:09:05 (4229) [INFO] 
* 2023-10-31 03:09:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-10-31 03:09:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-10-31 03:09:05 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-10-31 03:09:05 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-10-31 03:09:05 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-10-31 03:09:05 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-10-31 03:09:05 (4259) [INFO] 
* 2023-10-31 03:09:05 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-10-31 03:09:05 (4229) [INFO] 
* 2023-10-31 03:09:34 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-10-31 03:09:34 (4242) [INFO] Trying other mirror.
* 2023-10-31 03:09:53 (4242) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-10-31 03:09:53 (4242) [INFO] Trying other mirror.
* 2023-10-31 03:10:02 (4242) [INFO] 
* 2023-10-31 03:10:02 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-10-31 03:10:03 (4259) [INFO] 
* 2023-10-31 03:10:03 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-10-31 03:10:03 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-10-31 03:10:49 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-10-31 03:10:49 (1619) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-10-31 03:10:49 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-10-31 03:10:50 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-10-31 03:10:50 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/JPkL0FXUCY/ea_profile.json
* 2023-10-31 03:10:51 (2293) [INFO] Backed up EA4 profile to /tmp/JPkL0FXUCY/ea_profile.json
* 2023-10-31 03:10:52 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-01 03:08:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-01 03:08:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-01 03:08:40 (4229) [INFO] 
* 2023-11-01 03:08:41 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-01 03:08:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-01 03:08:41 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-01 03:08:41 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-01 03:08:41 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-01 03:08:41 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-01 03:08:41 (4259) [INFO] 
* 2023-11-01 03:08:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-01 03:08:41 (4229) [INFO] 
* 2023-11-01 03:08:56 (4242) [INFO] 
* 2023-11-01 03:08:56 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-01 03:08:56 (4259) [INFO] 
* 2023-11-01 03:08:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-01 03:08:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-01 03:09:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-01 03:09:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TNb9rD0Qmp/ea_profile.json
* 2023-11-01 03:09:12 (2293) [INFO] Backed up EA4 profile to /tmp/TNb9rD0Qmp/ea_profile.json
* 2023-11-01 03:09:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-02 03:08:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-02 03:08:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-02 03:08:38 (4229) [INFO] 
* 2023-11-02 03:08:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-02 03:08:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-02 03:08:38 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-02 03:08:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-02 03:08:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-02 03:08:38 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-02 03:08:38 (4259) [INFO] 
* 2023-11-02 03:08:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-02 03:08:38 (4229) [INFO] 
* 2023-11-02 03:08:52 (4242) [INFO] 
* 2023-11-02 03:08:52 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-02 03:08:52 (4259) [INFO] 
* 2023-11-02 03:08:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-02 03:08:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-02 03:09:06 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-02 03:09:06 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/t6cS1tNP9_/ea_profile.json
* 2023-11-02 03:09:07 (2293) [INFO] Backed up EA4 profile to /tmp/t6cS1tNP9_/ea_profile.json
* 2023-11-02 03:09:08 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-03 03:08:54 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-03 03:08:54 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-03 03:08:54 (4229) [INFO] 
* 2023-11-03 03:08:54 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-03 03:08:54 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-03 03:08:54 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-03 03:08:54 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-03 03:08:54 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-03 03:08:54 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-03 03:08:54 (4259) [INFO] 
* 2023-11-03 03:08:54 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-03 03:08:54 (4229) [INFO] 
* 2023-11-03 03:09:09 (4242) [INFO] 
* 2023-11-03 03:09:09 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-03 03:09:09 (4259) [INFO] 
* 2023-11-03 03:09:09 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-03 03:09:09 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-03 03:09:44 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-03 03:09:44 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/bHs2jwudC1/ea_profile.json
* 2023-11-03 03:09:45 (2293) [INFO] Backed up EA4 profile to /tmp/bHs2jwudC1/ea_profile.json
* 2023-11-03 03:09:46 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-04 03:09:27 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-04 03:09:27 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-04 03:09:27 (4229) [INFO] 
* 2023-11-04 03:09:27 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-04 03:09:27 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-04 03:09:27 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-04 03:09:27 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-04 03:09:27 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-04 03:09:27 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-04 03:09:27 (4242) [INFO] Other repos take up 356 k of disk space (use --verbose for details)
* 2023-11-04 03:09:27 (4259) [INFO] 
* 2023-11-04 03:09:27 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-04 03:09:27 (4229) [INFO] 
* 2023-11-04 03:09:42 (4242) [INFO] 
* 2023-11-04 03:09:42 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-04 03:09:43 (4259) [INFO] 
* 2023-11-04 03:09:43 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-04 03:09:43 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-04 03:09:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-04 03:09:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vpVlGbiPBp/ea_profile.json
* 2023-11-04 03:09:59 (2293) [INFO] Backed up EA4 profile to /tmp/vpVlGbiPBp/ea_profile.json
* 2023-11-04 03:10:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-05 03:09:05 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-05 03:09:05 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-05 03:09:05 (4229) [INFO] 
* 2023-11-05 03:09:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-05 03:09:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-05 03:09:05 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-05 03:09:05 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-05 03:09:05 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-05 03:09:05 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-05 03:09:05 (4259) [INFO] 
* 2023-11-05 03:09:05 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-05 03:09:05 (4229) [INFO] 
* 2023-11-05 03:09:24 (4242) [INFO] 
* 2023-11-05 03:09:24 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-05 03:09:24 (4259) [INFO] 
* 2023-11-05 03:09:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-05 03:09:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-05 03:09:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-05 03:09:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jvt8huseLs/ea_profile.json
* 2023-11-05 03:09:39 (2293) [INFO] Backed up EA4 profile to /tmp/jvt8huseLs/ea_profile.json
* 2023-11-05 03:09:40 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-06 03:08:36 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-06 03:08:36 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-06 03:08:36 (4229) [INFO] 
* 2023-11-06 03:08:36 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-06 03:08:36 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-06 03:08:36 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-06 03:08:36 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-06 03:08:36 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-06 03:08:36 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-06 03:08:36 (4259) [INFO] 
* 2023-11-06 03:08:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-06 03:08:36 (4229) [INFO] 
* 2023-11-06 03:08:51 (4242) [INFO] 
* 2023-11-06 03:08:51 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-06 03:08:51 (4259) [INFO] 
* 2023-11-06 03:08:51 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-06 03:08:51 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-06 03:09:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-06 03:09:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/KVo1UznKCR/ea_profile.json
* 2023-11-06 03:09:05 (2293) [INFO] Backed up EA4 profile to /tmp/KVo1UznKCR/ea_profile.json
* 2023-11-06 03:09:06 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-09 03:09:12 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-09 03:09:12 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-09 03:09:12 (4229) [INFO] 
* 2023-11-09 03:09:12 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-09 03:09:12 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-09 03:09:12 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-09 03:09:12 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-09 03:09:12 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-09 03:09:12 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-09 03:09:12 (4259) [INFO] 
* 2023-11-09 03:09:12 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-09 03:09:12 (4229) [INFO] 
* 2023-11-09 03:09:46 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
* 2023-11-09 03:09:46 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:10:07 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:10:07 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:10:22 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:10:22 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:10:49 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:10:49 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:10:49 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:10:49 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:10:55 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-11-09 03:10:55 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:11:04 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:11:04 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:11:19 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:11:19 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:11:34 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:11:34 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:12:09 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:12:09 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:12:15 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2023-11-09 03:12:15 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:12:30 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-11-09 03:12:30 (4242) [INFO] Trying other mirror.
* 2023-11-09 03:12:45 (4242) [INFO] 
* 2023-11-09 03:12:45 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-09 03:12:45 (4259) [INFO] 
* 2023-11-09 03:12:45 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-09 03:12:45 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-09 03:14:08 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-09 03:14:08 (1619) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
* 2023-11-09 03:14:08 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-09 03:14:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-09 03:14:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/z274MJqGA9/ea_profile.json
* 2023-11-09 03:14:09 (2293) [INFO] Backed up EA4 profile to /tmp/z274MJqGA9/ea_profile.json
* 2023-11-09 03:14:10 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-10 03:08:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-10 03:08:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-10 03:08:40 (4229) [INFO] 
* 2023-11-10 03:08:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-10 03:08:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-10 03:08:40 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-10 03:08:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-10 03:08:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-10 03:08:40 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-10 03:08:40 (4259) [INFO] 
* 2023-11-10 03:08:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-10 03:08:40 (4229) [INFO] 
* 2023-11-10 03:08:55 (4242) [INFO] 
* 2023-11-10 03:08:55 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-10 03:08:55 (4259) [INFO] 
* 2023-11-10 03:08:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-10 03:08:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-10 03:09:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-10 03:09:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uylYqmukPG/ea_profile.json
* 2023-11-10 03:09:09 (2293) [INFO] Backed up EA4 profile to /tmp/uylYqmukPG/ea_profile.json
* 2023-11-10 03:09:10 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-11 03:09:00 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-11 03:09:00 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-11 03:09:00 (4229) [INFO] 
* 2023-11-11 03:09:00 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-11 03:09:00 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-11 03:09:00 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-11 03:09:00 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-11 03:09:00 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-11 03:09:00 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-11 03:09:00 (4259) [INFO] 
* 2023-11-11 03:09:00 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-11 03:09:00 (4229) [INFO] 
* 2023-11-11 03:09:24 (4242) [INFO] 
* 2023-11-11 03:09:24 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-11 03:09:24 (4259) [INFO] 
* 2023-11-11 03:09:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-11 03:09:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-11 03:09:38 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-11 03:09:38 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/2x1skbdMDF/ea_profile.json
* 2023-11-11 03:09:38 (2293) [INFO] Backed up EA4 profile to /tmp/2x1skbdMDF/ea_profile.json
* 2023-11-11 03:09:39 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-12 03:09:05 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-12 03:09:05 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-12 03:09:05 (4229) [INFO] 
* 2023-11-12 03:09:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-12 03:09:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-12 03:09:06 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-12 03:09:06 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-12 03:09:06 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-12 03:09:06 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-12 03:09:06 (4259) [INFO] 
* 2023-11-12 03:09:06 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-12 03:09:06 (4229) [INFO] 
* 2023-11-12 03:09:24 (4242) [INFO] 
* 2023-11-12 03:09:24 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-12 03:09:24 (4259) [INFO] 
* 2023-11-12 03:09:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-12 03:09:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-12 03:09:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-12 03:09:40 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/huXn7Y8E5Y/ea_profile.json
* 2023-11-12 03:09:40 (2293) [INFO] Backed up EA4 profile to /tmp/huXn7Y8E5Y/ea_profile.json
* 2023-11-12 03:09:41 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-13 03:08:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-13 03:08:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-13 03:08:33 (4229) [INFO] 
* 2023-11-13 03:08:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-13 03:08:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-13 03:08:33 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-13 03:08:33 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-13 03:08:33 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-13 03:08:33 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-13 03:08:34 (4259) [INFO] 
* 2023-11-13 03:08:34 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-13 03:08:34 (4229) [INFO] 
* 2023-11-13 03:08:47 (4242) [INFO] 
* 2023-11-13 03:08:47 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-13 03:08:47 (4259) [INFO] 
* 2023-11-13 03:08:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-13 03:08:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-13 03:09:01 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-13 03:09:01 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/NphG7C6mle/ea_profile.json
* 2023-11-13 03:09:01 (2293) [INFO] Backed up EA4 profile to /tmp/NphG7C6mle/ea_profile.json
* 2023-11-13 03:09:03 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-14 03:22:55 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-14 03:22:55 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-14 03:22:55 (4229) [INFO] 
* 2023-11-14 03:22:55 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-14 03:22:55 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-14 03:22:55 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-14 03:22:55 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-14 03:22:55 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-14 03:22:55 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-14 03:22:55 (4259) [INFO] 
* 2023-11-14 03:22:55 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-14 03:22:55 (4229) [INFO] 
* 2023-11-14 03:23:12 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:23:12 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:23:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:23:27 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:23:42 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:23:42 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:23:57 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:23:57 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:24:12 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:24:12 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:24:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:24:27 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:24:42 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:24:42 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:24:57 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:24:57 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:25:12 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:12 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] Trying other mirror.
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]  One of the configured repositories failed (MariaDB106),
* 2023-11-14 03:25:27 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-11-14 03:25:27 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-11-14 03:25:27 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-11-14 03:25:27 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-11-14 03:25:27 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-11-14 03:25:27 (4242) [INFO]             yum --disablerepo=MariaDB106 ...
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-11-14 03:25:27 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-11-14 03:25:27 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]             yum-config-manager --disable MariaDB106
* 2023-11-14 03:25:27 (4242) [INFO]         or
* 2023-11-14 03:25:27 (4242) [INFO]             subscription-manager repos --disable=MariaDB106
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-11-14 03:25:27 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-11-14 03:25:27 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-11-14 03:25:27 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-11-14 03:25:27 (4242) [INFO]         compromise:
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO]             yum-config-manager --save --setopt=MariaDB106.skip_if_unavailable=true
* 2023-11-14 03:25:27 (4242) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO] failure: repodata/repomd.xml from MariaDB106: [Errno 256] No more mirrors to try.
* 2023-11-14 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/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 03:25:27 (4259) [INFO] 
* 2023-11-14 03:25:27 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-14 03:25:27 (1773) [INFO] Checking /scripts/sysup
* 2023-11-14 03:25:27 (4228) [INFO] Running: /scripts/sysup
* 2023-11-14 03:25:27 (4229) [INFO] 
* 2023-11-14 03:25:27 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-11-14 03:25:27 (4242) [INFO]   All Needed Packages are already installed.
* 2023-11-14 03:25:27 (4259) [INFO] 
* 2023-11-14 03:27:59 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-14 03:27:59 (1619) [ERROR] https://archive.mariadb.org/mariadb-10.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/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.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.


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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from MariaDB106: [Errno 256] No more mirrors to try.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
https://archive.mariadb.org/mariadb-10.6/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 03:27:59 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-14 03:27:59 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-14 03:27:59 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UZUZMWetaC/ea_profile.json
* 2023-11-14 03:30:30 (299) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UZUZMWetaC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2272.
* 2023-11-14 03:30:30 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-15 03:08:49 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-15 03:08:49 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-15 03:08:49 (4229) [INFO] 
* 2023-11-15 03:08:49 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-15 03:08:49 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-15 03:08:49 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-15 03:08:49 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-15 03:08:49 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-15 03:08:49 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-15 03:08:49 (4259) [INFO] 
* 2023-11-15 03:08:49 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-15 03:08:49 (4229) [INFO] 
* 2023-11-15 03:09:42 (4242) [INFO] 
* 2023-11-15 03:09:42 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-15 03:09:42 (4259) [INFO] 
* 2023-11-15 03:09:42 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-15 03:09:42 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-15 03:11:14 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-15 03:11:14 (1619) [ERROR] https://archive.mariadb.org/mariadb-10.6/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.6/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.6/yum/centos/7/x86_64/repodata/9ce1fd866bf08a4ab35ba6766422f4b75e9c0fa965dd8f311c2aec17594b75fc-filelists.sqlite.bz2: [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.6/yum/centos/7/x86_64/repodata/ebf57f7214bccdefb0526df6b9c76368ceeab7cea1801649ef99b1ad1fd8de75-other.sqlite.bz2: [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.6/yum/centos/7/x86_64/repodata/9ce1fd866bf08a4ab35ba6766422f4b75e9c0fa965dd8f311c2aec17594b75fc-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
* 2023-11-15 03:11:14 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-15 03:11:14 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-15 03:11:14 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4Drzf1f8Qq/ea_profile.json
* 2023-11-15 03:11:15 (2293) [INFO] Backed up EA4 profile to /tmp/4Drzf1f8Qq/ea_profile.json
* 2023-11-15 03:11:16 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-16 03:09:20 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-16 03:09:20 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-16 03:09:20 (4229) [INFO] 
* 2023-11-16 03:09:21 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-16 03:09:21 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-16 03:09:21 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-16 03:09:21 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-16 03:09:21 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-16 03:09:21 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-16 03:09:21 (4259) [INFO] 
* 2023-11-16 03:09:21 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-16 03:09:21 (4229) [INFO] 
* 2023-11-16 03:09:40 (4242) [INFO] Traceback (most recent call last):
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-11-16 03:09:40 (4242) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-11-16 03:09:40 (4242) [INFO]     errcode = main(args)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-11-16 03:09:40 (4242) [INFO]     result, resultmsgs = base.doCommands()
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-11-16 03:09:40 (4242) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-11-16 03:09:40 (4242) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-11-16 03:09:40 (4242) [INFO]     ignore_case=True, repoid=repoid)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-11-16 03:09:40 (4242) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-11-16 03:09:40 (4242) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-11-16 03:09:40 (4242) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-11-16 03:09:40 (4242) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-11-16 03:09:40 (4242) [INFO]     self.repos.populateSack(which=repos)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack
* 2023-11-16 03:09:40 (4242) [INFO]     sack.populate(repo, mdtype, callback, cacheonly)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 242, in populate
* 2023-11-16 03:09:40 (4242) [INFO]     mydbtype)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-11-16 03:09:40 (4242) [INFO]     cached=repo.cache)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-11-16 03:09:40 (4242) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-11-16 03:09:40 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-11-16 03:09:40 (4242) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-11-16 03:09:40 (4242) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite'
* 2023-11-16 03:09:40 (4259) [INFO] 
* 2023-11-16 03:09:40 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-16 03:09:40 (1773) [INFO] Checking /scripts/sysup
* 2023-11-16 03:09:40 (4228) [INFO] Running: /scripts/sysup
* 2023-11-16 03:09:40 (4229) [INFO] 
* 2023-11-16 03:09:40 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-11-16 03:09:40 (4242) [INFO]   All Needed Packages are already installed.
* 2023-11-16 03:09:40 (4259) [INFO] 
* 2023-11-16 03:09:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-16 03:09:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fEDT96f9wE/ea_profile.json
* 2023-11-16 03:09:58 (2293) [INFO] Backed up EA4 profile to /tmp/fEDT96f9wE/ea_profile.json
* 2023-11-16 03:09:59 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-11-17 03:08:45 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-17 03:08:45 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-17 03:08:45 (4229) [INFO] 
* 2023-11-17 03:08:46 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-17 03:08:46 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-17 03:08:46 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-17 03:08:46 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-17 03:08:46 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-17 03:08:46 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-17 03:08:46 (4259) [INFO] 
* 2023-11-17 03:08:46 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-17 03:08:46 (4229) [INFO] 
* 2023-11-17 03:09:01 (4242) [INFO] 
* 2023-11-17 03:09:01 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-17 03:09:01 (4259) [INFO] 
* 2023-11-17 03:09:01 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-17 03:09:01 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-17 03:09:34 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-17 03:09:34 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Z_apV2goaX/ea_profile.json
* 2023-11-17 03:09:35 (2293) [INFO] Backed up EA4 profile to /tmp/Z_apV2goaX/ea_profile.json
* 2023-11-17 03:09:36 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-18 03:09:05 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-18 03:09:05 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-18 03:09:05 (4229) [INFO] 
* 2023-11-18 03:09:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-18 03:09:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-18 03:09:05 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-18 03:09:05 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-18 03:09:05 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-18 03:09:05 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-18 03:09:05 (4259) [INFO] 
* 2023-11-18 03:09:05 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-18 03:09:05 (4229) [INFO] 
* 2023-11-18 03:09:28 (4242) [INFO] 
* 2023-11-18 03:09:28 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-18 03:09:29 (4259) [INFO] 
* 2023-11-18 03:09:29 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-18 03:09:29 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-18 03:09:42 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-18 03:09:42 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/flC9a0_2IJ/ea_profile.json
* 2023-11-18 03:09:42 (2293) [INFO] Backed up EA4 profile to /tmp/flC9a0_2IJ/ea_profile.json
* 2023-11-18 03:09:43 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-19 03:09:06 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-19 03:09:06 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-19 03:09:06 (4229) [INFO] 
* 2023-11-19 03:09:06 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-19 03:09:06 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-19 03:09:06 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-19 03:09:06 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-19 03:09:06 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-19 03:09:06 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-19 03:09:06 (4259) [INFO] 
* 2023-11-19 03:09:06 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-19 03:09:06 (4229) [INFO] 
* 2023-11-19 03:09:21 (4242) [INFO] 
* 2023-11-19 03:09:21 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-19 03:09:21 (4259) [INFO] 
* 2023-11-19 03:09:21 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-19 03:09:21 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-19 03:09:36 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-19 03:09:36 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5joPOmMyOm/ea_profile.json
* 2023-11-19 03:09:37 (2293) [INFO] Backed up EA4 profile to /tmp/5joPOmMyOm/ea_profile.json
* 2023-11-19 03:09:38 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-20 03:08:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-20 03:08:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-20 03:08:32 (4229) [INFO] 
* 2023-11-20 03:08:32 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-20 03:08:32 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-20 03:08:32 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-20 03:08:32 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-20 03:08:32 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-20 03:08:32 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-20 03:08:32 (4259) [INFO] 
* 2023-11-20 03:08:32 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-20 03:08:32 (4229) [INFO] 
* 2023-11-20 03:08:44 (4242) [INFO] 
* 2023-11-20 03:08:44 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-20 03:08:44 (4259) [INFO] 
* 2023-11-20 03:08:44 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-20 03:08:44 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-20 03:08:57 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-20 03:08:57 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0z75fiIxSI/ea_profile.json
* 2023-11-20 03:08:58 (2293) [INFO] Backed up EA4 profile to /tmp/0z75fiIxSI/ea_profile.json
* 2023-11-20 03:08:59 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-21 03:08:47 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-21 03:08:47 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-21 03:08:47 (4229) [INFO] 
* 2023-11-21 03:08:48 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-21 03:08:48 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-21 03:08:48 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-21 03:08:48 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-21 03:08:48 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-21 03:08:48 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-21 03:08:48 (4259) [INFO] 
* 2023-11-21 03:08:48 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-21 03:08:48 (4229) [INFO] 
* 2023-11-21 03:09:02 (4242) [INFO] 
* 2023-11-21 03:09:02 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-21 03:09:02 (4259) [INFO] 
* 2023-11-21 03:09:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-21 03:09:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-21 03:10:22 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-11-21 03:10:22 (1619) [ERROR] https://archive.mariadb.org/mariadb-10.6/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.6/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.6/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.6/yum/centos/7/x86_64/repodata/ebf57f7214bccdefb0526df6b9c76368ceeab7cea1801649ef99b1ad1fd8de75-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2a01:4f8:c17:cad6::1: Network is unreachable"
Trying other mirror.
* 2023-11-21 03:10:22 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-11-21 03:10:22 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-21 03:10:22 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ACapXHo_2Q/ea_profile.json
* 2023-11-21 03:10:23 (2293) [INFO] Backed up EA4 profile to /tmp/ACapXHo_2Q/ea_profile.json
* 2023-11-21 03:10:24 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-22 03:08:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-22 03:08:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-22 03:08:35 (4229) [INFO] 
* 2023-11-22 03:08:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-22 03:08:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-22 03:08:35 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-22 03:08:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-22 03:08:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-22 03:08:35 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-22 03:08:35 (4259) [INFO] 
* 2023-11-22 03:08:35 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-22 03:08:35 (4229) [INFO] 
* 2023-11-22 03:08:49 (4242) [INFO] 
* 2023-11-22 03:08:49 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-22 03:08:49 (4259) [INFO] 
* 2023-11-22 03:08:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-22 03:08:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-22 03:09:04 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-22 03:09:04 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8h9tw5z3P3/ea_profile.json
* 2023-11-22 03:09:05 (2293) [INFO] Backed up EA4 profile to /tmp/8h9tw5z3P3/ea_profile.json
* 2023-11-22 03:09:06 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-23 03:08:33 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-23 03:08:33 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-23 03:08:33 (4229) [INFO] 
* 2023-11-23 03:08:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-23 03:08:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-23 03:08:33 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-23 03:08:33 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-23 03:08:33 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-23 03:08:33 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-23 03:08:33 (4259) [INFO] 
* 2023-11-23 03:08:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-23 03:08:33 (4229) [INFO] 
* 2023-11-23 03:08:47 (4242) [INFO] 
* 2023-11-23 03:08:47 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-23 03:08:47 (4259) [INFO] 
* 2023-11-23 03:08:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-23 03:08:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-23 03:09:01 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-23 03:09:01 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/exKcWgeKUJ/ea_profile.json
* 2023-11-23 03:09:01 (2293) [INFO] Backed up EA4 profile to /tmp/exKcWgeKUJ/ea_profile.json
* 2023-11-23 03:09:03 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-24 03:08:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-24 03:08:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-24 03:08:37 (4229) [INFO] 
* 2023-11-24 03:08:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-24 03:08:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-24 03:08:37 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-24 03:08:37 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-24 03:08:37 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-24 03:08:37 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-24 03:08:37 (4259) [INFO] 
* 2023-11-24 03:08:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-24 03:08:37 (4229) [INFO] 
* 2023-11-24 03:08:52 (4242) [INFO] 
* 2023-11-24 03:08:52 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-24 03:08:52 (4259) [INFO] 
* 2023-11-24 03:08:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-24 03:08:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-24 03:09:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-24 03:09:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uJ6NLpAedh/ea_profile.json
* 2023-11-24 03:09:13 (2293) [INFO] Backed up EA4 profile to /tmp/uJ6NLpAedh/ea_profile.json
* 2023-11-24 03:09:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-25 03:09:14 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-25 03:09:14 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-25 03:09:14 (4229) [INFO] 
* 2023-11-25 03:09:14 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-25 03:09:14 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-25 03:09:14 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-25 03:09:14 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-25 03:09:14 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-25 03:09:14 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-25 03:09:14 (4259) [INFO] 
* 2023-11-25 03:09:14 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-25 03:09:14 (4229) [INFO] 
* 2023-11-25 03:09:34 (4242) [INFO] 
* 2023-11-25 03:09:34 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-25 03:09:34 (4259) [INFO] 
* 2023-11-25 03:09:34 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-25 03:09:34 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-25 03:09:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-25 03:09:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dKQHSMBvyW/ea_profile.json
* 2023-11-25 03:09:50 (2293) [INFO] Backed up EA4 profile to /tmp/dKQHSMBvyW/ea_profile.json
* 2023-11-25 03:09:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-26 03:09:11 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-26 03:09:11 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-26 03:09:11 (4229) [INFO] 
* 2023-11-26 03:09:11 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-26 03:09:11 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-26 03:09:11 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-26 03:09:11 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-26 03:09:11 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-26 03:09:11 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-26 03:09:11 (4259) [INFO] 
* 2023-11-26 03:09:11 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-26 03:09:11 (4229) [INFO] 
* 2023-11-26 03:09:17 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/314d8d209393ece5e7cba57f50d15113d3f882d5414fbb191223f5d6ed6f9ac1-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/356e3ccc9c1d3069701db41f31987a9ce8ccfd8432dd58a385e1e95ac8c08170-updateinfo.xml.gz: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://de.mirrors.clouvider.net/CentOS/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/64a84a35fa21c74632d08c540feee458998bf18825ec1265be77285d24b13351-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/76eb18371be274146debd1abc0969d78ee33d0724816ebf7a33c18b768f65343-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:17 (4242) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:18 (4242) [INFO] http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:18 (4242) [INFO] http://ftp.plusline.net/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:18 (4242) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:18 (4242) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:18 (4242) [INFO] http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:18 (4242) [INFO] http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://centos.bio.lmu.de/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://mirror.speedkom.de/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://mirrors.xtom.de/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://mirror.softaculous.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://mirror.junda.nl/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:19 (4242) [INFO] http://centosmirror.netcup.net/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-11-26 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:22 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/7f841e765ee3bce1ed1e4cab3c87704870b0557a14d209f5127c8fc2589f1635-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-11-26 03:09:22 (4242) [INFO] Trying other mirror.
* 2023-11-26 03:09:32 (4242) [INFO] 
* 2023-11-26 03:09:32 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-26 03:09:32 (4259) [INFO] 
* 2023-11-26 03:09:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-26 03:09:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-26 03:09:49 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-26 03:09:49 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R6ZZkdoYd7/ea_profile.json
* 2023-11-26 03:09:50 (2293) [INFO] Backed up EA4 profile to /tmp/R6ZZkdoYd7/ea_profile.json
* 2023-11-26 03:09:51 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-27 03:08:32 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-27 03:08:32 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-27 03:08:32 (4229) [INFO] 
* 2023-11-27 03:08:33 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-27 03:08:33 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-27 03:08:33 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-27 03:08:33 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-27 03:08:33 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-27 03:08:33 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-27 03:08:33 (4259) [INFO] 
* 2023-11-27 03:08:33 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-27 03:08:33 (4229) [INFO] 
* 2023-11-27 03:08:47 (4242) [INFO] 
* 2023-11-27 03:08:47 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-27 03:08:47 (4259) [INFO] 
* 2023-11-27 03:08:47 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-27 03:08:47 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-27 03:09:02 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-27 03:09:02 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/PfScVUag9n/ea_profile.json
* 2023-11-27 03:09:03 (2293) [INFO] Backed up EA4 profile to /tmp/PfScVUag9n/ea_profile.json
* 2023-11-27 03:09:04 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-28 03:08:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-28 03:08:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-28 03:08:38 (4229) [INFO] 
* 2023-11-28 03:08:38 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-28 03:08:38 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-28 03:08:38 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-28 03:08:38 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-28 03:08:38 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-28 03:08:38 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-28 03:08:38 (4259) [INFO] 
* 2023-11-28 03:08:38 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-28 03:08:38 (4229) [INFO] 
* 2023-11-28 03:08:56 (4242) [INFO] 
* 2023-11-28 03:08:56 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-28 03:08:56 (4259) [INFO] 
* 2023-11-28 03:08:56 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-28 03:08:56 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-28 03:09:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-28 03:09:11 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/g_yroMAZxW/ea_profile.json
* 2023-11-28 03:09:12 (2293) [INFO] Backed up EA4 profile to /tmp/g_yroMAZxW/ea_profile.json
* 2023-11-28 03:09:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-29 03:08:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-29 03:08:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-29 03:08:40 (4229) [INFO] 
* 2023-11-29 03:08:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-29 03:08:40 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-29 03:08:40 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-29 03:08:40 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-29 03:08:40 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-29 03:08:40 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-29 03:08:40 (4259) [INFO] 
* 2023-11-29 03:08:40 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-29 03:08:40 (4229) [INFO] 
* 2023-11-29 03:08:57 (4242) [INFO] 
* 2023-11-29 03:08:57 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-29 03:08:57 (4259) [INFO] 
* 2023-11-29 03:08:57 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-29 03:08:57 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-29 03:09:18 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-29 03:09:18 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b9m2hknNhV/ea_profile.json
* 2023-11-29 03:09:18 (2293) [INFO] Backed up EA4 profile to /tmp/b9m2hknNhV/ea_profile.json
* 2023-11-29 03:09:20 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-11-30 03:08:35 (1752) [INFO] Checking if your system is up to date: 
* 2023-11-30 03:08:35 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-11-30 03:08:35 (4229) [INFO] 
* 2023-11-30 03:08:35 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-11-30 03:08:35 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-11-30 03:08:35 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-11-30 03:08:35 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-11-30 03:08:35 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-11-30 03:08:35 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-11-30 03:08:36 (4259) [INFO] 
* 2023-11-30 03:08:36 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-11-30 03:08:36 (4229) [INFO] 
* 2023-11-30 03:08:49 (4242) [INFO] 
* 2023-11-30 03:08:49 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-11-30 03:08:49 (4259) [INFO] 
* 2023-11-30 03:08:49 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-11-30 03:08:49 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-11-30 03:09:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-11-30 03:09:03 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4Td1_TC0Xx/ea_profile.json
* 2023-11-30 03:09:04 (2293) [INFO] Backed up EA4 profile to /tmp/4Td1_TC0Xx/ea_profile.json
* 2023-11-30 03:09:05 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-01 03:09:03 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-01 03:09:03 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-01 03:09:03 (4229) [INFO] 
* 2023-12-01 03:09:03 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-01 03:09:03 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-01 03:09:03 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-01 03:09:03 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-01 03:09:03 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-01 03:09:03 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-01 03:09:03 (4259) [INFO] 
* 2023-12-01 03:09:03 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-01 03:09:03 (4229) [INFO] 
* 2023-12-01 03:09:24 (4242) [INFO] 
* 2023-12-01 03:09:24 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-01 03:09:24 (4259) [INFO] 
* 2023-12-01 03:09:24 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-01 03:09:24 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-01 03:09:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-01 03:09:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZJ3pA1tGfz/ea_profile.json
* 2023-12-01 03:09:48 (2293) [INFO] Backed up EA4 profile to /tmp/ZJ3pA1tGfz/ea_profile.json
* 2023-12-01 03:09:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-02 03:09:09 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-02 03:09:09 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-02 03:09:09 (4229) [INFO] 
* 2023-12-02 03:09:09 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-02 03:09:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-02 03:09:09 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-02 03:09:09 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-02 03:09:09 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-02 03:09:09 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-02 03:09:09 (4259) [INFO] 
* 2023-12-02 03:09:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-02 03:09:09 (4229) [INFO] 
* 2023-12-02 03:09:17 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:17 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/bdfeebdb7396182929eac99fe8d29c7e141f98cdc882dc3a5f80ca70a5c407ab-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:17 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:18 (4242) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/356e3ccc9c1d3069701db41f31987a9ce8ccfd8432dd58a385e1e95ac8c08170-updateinfo.xml.gz: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:18 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/d6f5ce14bb7c54caa2c9b9942c1a324bad2da3ed7acef53e230cf100642cb3b6-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:18 (4242) [INFO] http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:18 (4242) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:19 (4242) [INFO] http://de.mirrors.clouvider.net/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:19 (4242) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:19 (4242) [INFO] http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:19 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/9513cf1a3f13f3c44460f4ef060b1c39394d57d2c6b409296c4b8408b2f15d33-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] http://mirror.checkdomain.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] http://mirror.23m.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] http://mirror.netcologne.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] http://mirror.netzwerge.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:20 (4242) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:20 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:21 (4242) [INFO] http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-02 03:09:21 (4242) [INFO] Trying other mirror.
* 2023-12-02 03:09:32 (4242) [INFO] 
* 2023-12-02 03:09:32 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-02 03:09:32 (4259) [INFO] 
* 2023-12-02 03:09:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-02 03:09:32 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-02 03:09:47 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-02 03:09:47 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ncSu8MYK7J/ea_profile.json
* 2023-12-02 03:09:48 (2293) [INFO] Backed up EA4 profile to /tmp/ncSu8MYK7J/ea_profile.json
* 2023-12-02 03:09:49 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-03 03:09:08 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-03 03:09:08 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-03 03:09:08 (4229) [INFO] 
* 2023-12-03 03:09:08 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-03 03:09:09 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-03 03:09:09 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-03 03:09:09 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-03 03:09:09 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-03 03:09:09 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-03 03:09:09 (4259) [INFO] 
* 2023-12-03 03:09:09 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-03 03:09:09 (4229) [INFO] 
* 2023-12-03 03:09:15 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:15 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:15 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/bdfeebdb7396182929eac99fe8d29c7e141f98cdc882dc3a5f80ca70a5c407ab-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:15 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:16 (4242) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/d6f5ce14bb7c54caa2c9b9942c1a324bad2da3ed7acef53e230cf100642cb3b6-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:16 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:17 (4242) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.12/wp-toolkit/repodata/f6489a31962cb070b7494bc283d6303983e10275d589f623bb4f29067abbc0a0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-12-03 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:17 (4242) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:17 (4242) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/bdfeebdb7396182929eac99fe8d29c7e141f98cdc882dc3a5f80ca70a5c407ab-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:17 (4242) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/9513cf1a3f13f3c44460f4ef060b1c39394d57d2c6b409296c4b8408b2f15d33-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:17 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:18 (4242) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/d6f5ce14bb7c54caa2c9b9942c1a324bad2da3ed7acef53e230cf100642cb3b6-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-03 03:09:18 (4242) [INFO] Trying other mirror.
* 2023-12-03 03:09:20 (4242) [INFO] Traceback (most recent call last):
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-12-03 03:09:20 (4242) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-12-03 03:09:20 (4242) [INFO]     errcode = main(args)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-12-03 03:09:20 (4242) [INFO]     result, resultmsgs = base.doCommands()
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-12-03 03:09:20 (4242) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-12-03 03:09:20 (4242) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-12-03 03:09:20 (4242) [INFO]     ignore_case=True, repoid=repoid)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-12-03 03:09:20 (4242) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-12-03 03:09:20 (4242) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-12-03 03:09:20 (4242) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-12-03 03:09:20 (4242) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-12-03 03:09:20 (4242) [INFO]     self.repos.populateSack(which=repos)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2023-12-03 03:09:20 (4242) [INFO]     sack._retrieve_async(repo, data)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2023-12-03 03:09:20 (4242) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-12-03 03:09:20 (4242) [INFO]     cached=repo.cache)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-12-03 03:09:20 (4242) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-12-03 03:09:20 (4242) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-12-03 03:09:20 (4242) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-12-03 03:09:20 (4242) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2023-12-03 03:09:20 (4259) [INFO] 
* 2023-12-03 03:09:20 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-03 03:09:20 (1773) [INFO] Checking /scripts/sysup
* 2023-12-03 03:09:20 (4228) [INFO] Running: /scripts/sysup
* 2023-12-03 03:09:20 (4229) [INFO] 
* 2023-12-03 03:09:20 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-03 03:09:20 (4242) [INFO]   All Needed Packages are already installed.
* 2023-12-03 03:09:20 (4259) [INFO] 
* 2023-12-03 03:09:37 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-03 03:09:37 (1619) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/9513cf1a3f13f3c44460f4ef060b1c39394d57d2c6b409296c4b8408b2f15d33-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-12-03 03:09:37 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-03 03:09:37 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-03 03:09:37 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ILibECt5as/ea_profile.json
* 2023-12-03 03:09:42 (2293) [INFO] Backed up EA4 profile to /tmp/ILibECt5as/ea_profile.json
* 2023-12-03 03:09:43 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-04 03:08:37 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-04 03:08:37 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-04 03:08:37 (4229) [INFO] 
* 2023-12-04 03:08:37 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-04 03:08:37 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-04 03:08:37 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-04 03:08:37 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-04 03:08:37 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-04 03:08:37 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-04 03:08:37 (4259) [INFO] 
* 2023-12-04 03:08:37 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-04 03:08:37 (4229) [INFO] 
* 2023-12-04 03:08:55 (4242) [INFO] 
* 2023-12-04 03:08:55 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-04 03:08:55 (4259) [INFO] 
* 2023-12-04 03:08:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-04 03:08:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-04 03:09:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-04 03:09:12 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S5fSum57BI/ea_profile.json
* 2023-12-04 03:09:13 (2293) [INFO] Backed up EA4 profile to /tmp/S5fSum57BI/ea_profile.json
* 2023-12-04 03:09:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-05 03:08:40 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-05 03:08:40 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-05 03:08:40 (4229) [INFO] 
* 2023-12-05 03:08:40 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-05 03:08:41 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-05 03:08:41 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-05 03:08:41 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-05 03:08:41 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-05 03:08:41 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-05 03:08:41 (4259) [INFO] 
* 2023-12-05 03:08:41 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-05 03:08:41 (4229) [INFO] 
* 2023-12-05 03:08:55 (4242) [INFO] 
* 2023-12-05 03:08:55 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-05 03:08:55 (4259) [INFO] 
* 2023-12-05 03:08:55 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-05 03:08:55 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-05 03:09:14 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-05 03:09:14 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/TiqgwcVQak/ea_profile.json
* 2023-12-05 03:09:15 (2293) [INFO] Backed up EA4 profile to /tmp/TiqgwcVQak/ea_profile.json
* 2023-12-05 03:09:16 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-06 03:08:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-06 03:08:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-06 03:08:38 (4229) [INFO] 
* 2023-12-06 03:08:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-06 03:08:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-06 03:08:39 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-06 03:08:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-06 03:08:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-06 03:08:39 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-06 03:08:39 (4259) [INFO] 
* 2023-12-06 03:08:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-06 03:08:39 (4229) [INFO] 
* 2023-12-06 03:08:54 (4242) [INFO] 
* 2023-12-06 03:08:54 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-06 03:08:54 (4259) [INFO] 
* 2023-12-06 03:08:54 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-06 03:08:54 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-06 03:09:13 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-06 03:09:13 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/S3gcXkgfn7/ea_profile.json
* 2023-12-06 03:09:14 (2293) [INFO] Backed up EA4 profile to /tmp/S3gcXkgfn7/ea_profile.json
* 2023-12-06 03:09:15 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-07 03:09:05 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-07 03:09:05 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-07 03:09:05 (4229) [INFO] 
* 2023-12-07 03:09:05 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-07 03:09:05 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-07 03:09:05 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-07 03:09:05 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-07 03:09:05 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-07 03:09:05 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-07 03:09:05 (4259) [INFO] 
* 2023-12-07 03:09:05 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-07 03:09:05 (4229) [INFO] 
* 2023-12-07 03:09:27 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-07 03:09:27 (4242) [INFO] Trying other mirror.
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]  One of the configured repositories failed (Unknown),
* 2023-12-07 03:09:32 (4242) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-07 03:09:32 (4242) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-07 03:09:32 (4242) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-07 03:09:32 (4242) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-07 03:09:32 (4242) [INFO]         packages for the previous distribution release still work).
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-07 03:09:32 (4242) [INFO]             yum --disablerepo=<repoid> ...
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-07 03:09:32 (4242) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-07 03:09:32 (4242) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]             yum-config-manager --disable <repoid>
* 2023-12-07 03:09:32 (4242) [INFO]         or
* 2023-12-07 03:09:32 (4242) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-07 03:09:32 (4242) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-07 03:09:32 (4242) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-07 03:09:32 (4242) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-07 03:09:32 (4242) [INFO]         compromise:
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-07 03:09:32 (4242) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO] imunify360: Check uncompressed DB failed
* 2023-12-07 03:09:32 (4259) [INFO] 
* 2023-12-07 03:09:32 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-07 03:09:32 (1773) [INFO] Checking /scripts/sysup
* 2023-12-07 03:09:32 (4228) [INFO] Running: /scripts/sysup
* 2023-12-07 03:09:32 (4229) [INFO] 
* 2023-12-07 03:09:32 (4242) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-07 03:09:33 (4242) [INFO]   All Needed Packages are already installed.
* 2023-12-07 03:09:33 (4259) [INFO] 
* 2023-12-07 03:09:51 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-07 03:09:51 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SUXusg1TF6/ea_profile.json
* 2023-12-07 03:09:52 (2293) [INFO] Backed up EA4 profile to /tmp/SUXusg1TF6/ea_profile.json
* 2023-12-07 03:09:53 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-12-08 03:11:18 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-08 03:11:18 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-08 03:11:18 (4229) [INFO] 
* 2023-12-08 03:11:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-08 03:11:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-08 03:11:18 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-08 03:11:18 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-08 03:11:18 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-08 03:11:18 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-08 03:11:18 (4259) [INFO] 
* 2023-12-08 03:11:18 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-08 03:11:18 (4229) [INFO] 
* 2023-12-08 03:11:49 (4242) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-08 03:11:49 (4242) [INFO] Trying other mirror.
* 2023-12-08 03:11:49 (4242) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-08 03:11:49 (4242) [INFO] Trying other mirror.
* 2023-12-08 03:12:02 (4242) [INFO] 
* 2023-12-08 03:12:02 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-08 03:12:02 (4259) [INFO] 
* 2023-12-08 03:12:02 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-08 03:12:02 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-08 03:12:59 (1618) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-08 03:12:59 (1619) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2023-12-08 03:12:59 (155) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-08 03:13:00 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-08 03:13:00 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AvrSHbU7Gx/ea_profile.json
* 2023-12-08 03:13:01 (2293) [INFO] Backed up EA4 profile to /tmp/AvrSHbU7Gx/ea_profile.json
* 2023-12-08 03:13:02 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-09 02:23:21 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-09 02:23:21 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-09 02:23:21 (4229) [INFO] 
* 2023-12-09 02:23:22 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-09 02:23:22 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-09 02:23:22 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-09 02:23:22 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-09 02:23:22 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-09 02:23:22 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-09 02:23:22 (4259) [INFO] 
* 2023-12-09 02:23:22 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-09 02:23:22 (4229) [INFO] 
* 2023-12-09 02:23:39 (4242) [INFO] 
* 2023-12-09 02:23:39 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-09 02:23:39 (4259) [INFO] 
* 2023-12-09 02:23:39 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-09 02:23:39 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-09 02:23:58 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-09 02:23:58 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/qTu100PovX/ea_profile.json
* 2023-12-09 02:23:59 (2293) [INFO] Backed up EA4 profile to /tmp/qTu100PovX/ea_profile.json
* 2023-12-09 02:24:00 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-10 03:09:18 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-10 03:09:18 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-10 03:09:18 (4229) [INFO] 
* 2023-12-10 03:09:18 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-10 03:09:18 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-10 03:09:18 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-10 03:09:18 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-10 03:09:18 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-10 03:09:18 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-10 03:09:18 (4259) [INFO] 
* 2023-12-10 03:09:18 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-10 03:09:18 (4229) [INFO] 
* 2023-12-10 03:09:39 (4242) [INFO] 
* 2023-12-10 03:09:39 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-10 03:09:39 (4259) [INFO] 
* 2023-12-10 03:09:39 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-10 03:09:39 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-10 03:09:56 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-10 03:09:56 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ftj_K2g_pZ/ea_profile.json
* 2023-12-10 03:09:57 (2293) [INFO] Backed up EA4 profile to /tmp/ftj_K2g_pZ/ea_profile.json
* 2023-12-10 03:09:58 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-11 03:08:38 (1752) [INFO] Checking if your system is up to date: 
* 2023-12-11 03:08:38 (4228) [INFO] Running: /usr/bin/yum clean all
* 2023-12-11 03:08:38 (4229) [INFO] 
* 2023-12-11 03:08:39 (4242) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-11 03:08:39 (4242) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-11 03:08:39 (4242) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-11 03:08:39 (4242) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-11 03:08:39 (4242) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-11 03:08:39 (4242) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-11 03:08:39 (4259) [INFO] 
* 2023-12-11 03:08:39 (4228) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-11 03:08:39 (4229) [INFO] 
* 2023-12-11 03:08:52 (4242) [INFO] 
* 2023-12-11 03:08:52 (4242) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-11 03:08:52 (4259) [INFO] 
* 2023-12-11 03:08:52 (1759) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-11 03:08:52 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-11 03:09:09 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-11 03:09:09 (2270) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/8dmcYxJuaq/ea_profile.json
* 2023-12-11 03:09:10 (2293) [INFO] Backed up EA4 profile to /tmp/8dmcYxJuaq/ea_profile.json
* 2023-12-11 03:09:11 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-12 03:08:37 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-12 03:08:37 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-12 03:08:37 (4230) [INFO] 
* 2023-12-12 03:08:37 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-12 03:08:37 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-12 03:08:37 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-12 03:08:37 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-12 03:08:37 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-12 03:08:37 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-12 03:08:37 (4260) [INFO] 
* 2023-12-12 03:08:37 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-12 03:08:37 (4230) [INFO] 
* 2023-12-12 03:08:53 (4243) [INFO] 
* 2023-12-12 03:08:53 (4243) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-12 03:08:53 (4260) [INFO] 
* 2023-12-12 03:08:53 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-12 03:08:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-12 03:09:11 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-12 03:09:11 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b1xhUe7ARe/ea_profile.json
* 2023-12-12 03:09:12 (2294) [INFO] Backed up EA4 profile to /tmp/b1xhUe7ARe/ea_profile.json
* 2023-12-12 03:09:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-13 03:08:53 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-13 03:08:53 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-13 03:08:53 (4230) [INFO] 
* 2023-12-13 03:08:53 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-13 03:08:53 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-13 03:08:53 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-13 03:08:53 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-13 03:08:53 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-13 03:08:53 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-13 03:08:53 (4260) [INFO] 
* 2023-12-13 03:08:53 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-13 03:08:53 (4230) [INFO] 
* 2023-12-13 03:09:08 (4243) [INFO] 
* 2023-12-13 03:09:08 (4243) [INFO] kernel.x86_64                   3.10.0-1160.102.1.el7                    updates
* 2023-12-13 03:09:08 (4260) [INFO] 
* 2023-12-13 03:09:08 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-13 03:09:08 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-13 03:09:29 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-13 03:09:29 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/e5Q2TSF_6W/ea_profile.json
* 2023-12-13 03:09:30 (2294) [INFO] Backed up EA4 profile to /tmp/e5Q2TSF_6W/ea_profile.json
* 2023-12-13 03:09:31 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-14 03:10:57 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-14 03:10:57 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-14 03:10:57 (4230) [INFO] 
* 2023-12-14 03:10:57 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-14 03:10:57 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-14 03:10:57 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-14 03:10:57 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-14 03:10:57 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-14 03:10:57 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-14 03:10:57 (4260) [INFO] 
* 2023-12-14 03:10:57 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-14 03:10:57 (4230) [INFO] 
* 2023-12-14 03:11:11 (4243) [INFO] 
* 2023-12-14 03:11:11 (4243) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-14 03:11:11 (4260) [INFO] 
* 2023-12-14 03:11:11 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-14 03:11:11 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-14 03:11:27 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-14 03:11:27 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/R7wV83W_4g/ea_profile.json
* 2023-12-14 03:11:28 (2294) [INFO] Backed up EA4 profile to /tmp/R7wV83W_4g/ea_profile.json
* 2023-12-14 03:11:29 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-15 03:08:51 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-15 03:08:51 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-15 03:08:51 (4230) [INFO] 
* 2023-12-15 03:08:51 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-15 03:08:51 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-15 03:08:51 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-15 03:08:51 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-15 03:08:51 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-15 03:08:51 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-15 03:08:51 (4260) [INFO] 
* 2023-12-15 03:08:51 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-15 03:08:51 (4230) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]  One of the configured repositories failed (Unknown),
* 2023-12-15 03:09:16 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-15 03:09:16 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-15 03:09:16 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-15 03:09:16 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-15 03:09:16 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-15 03:09:16 (4243) [INFO]             yum --disablerepo=<repoid> ...
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-15 03:09:16 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-15 03:09:16 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]             yum-config-manager --disable <repoid>
* 2023-12-15 03:09:16 (4243) [INFO]         or
* 2023-12-15 03:09:16 (4243) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-15 03:09:16 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-15 03:09:16 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-15 03:09:16 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-15 03:09:16 (4243) [INFO]         compromise:
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-15 03:09:16 (4243) [INFO] 
* 2023-12-15 03:09:16 (4243) [INFO] updates: Check uncompressed DB failed
* 2023-12-15 03:09:16 (4260) [INFO] 
* 2023-12-15 03:09:16 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-15 03:09:16 (1774) [INFO] Checking /scripts/sysup
* 2023-12-15 03:09:16 (4229) [INFO] Running: /scripts/sysup
* 2023-12-15 03:09:16 (4230) [INFO] 
* 2023-12-15 03:09:17 (4243) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-15 03:09:17 (4243) [INFO]   All Needed Packages are already installed.
* 2023-12-15 03:09:17 (4260) [INFO] 
* 2023-12-15 03:09:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-15 03:09:46 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/nhdon6XrNt/ea_profile.json
* 2023-12-15 03:09:47 (2294) [INFO] Backed up EA4 profile to /tmp/nhdon6XrNt/ea_profile.json
* 2023-12-15 03:09:49 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-12-16 03:09:09 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-16 03:09:09 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-16 03:09:09 (4230) [INFO] 
* 2023-12-16 03:09:09 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-16 03:09:09 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-16 03:09:09 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-16 03:09:09 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-16 03:09:09 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-16 03:09:09 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-16 03:09:10 (4260) [INFO] 
* 2023-12-16 03:09:10 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-16 03:09:10 (4230) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]  One of the configured repositories failed (Unknown),
* 2023-12-16 03:09:22 (4243) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-16 03:09:22 (4243) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-16 03:09:22 (4243) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-16 03:09:22 (4243) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-16 03:09:22 (4243) [INFO]         packages for the previous distribution release still work).
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-16 03:09:22 (4243) [INFO]             yum --disablerepo=<repoid> ...
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-16 03:09:22 (4243) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-16 03:09:22 (4243) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]             yum-config-manager --disable <repoid>
* 2023-12-16 03:09:22 (4243) [INFO]         or
* 2023-12-16 03:09:22 (4243) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-16 03:09:22 (4243) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-16 03:09:22 (4243) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-16 03:09:22 (4243) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-16 03:09:22 (4243) [INFO]         compromise:
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-16 03:09:22 (4243) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO] database disk image is malformed
* 2023-12-16 03:09:22 (4260) [INFO] 
* 2023-12-16 03:09:22 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-16 03:09:22 (1774) [INFO] Checking /scripts/sysup
* 2023-12-16 03:09:22 (4229) [INFO] Running: /scripts/sysup
* 2023-12-16 03:09:22 (4230) [INFO] 
* 2023-12-16 03:09:22 (4243) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-16 03:09:23 (4243) [INFO]   All Needed Packages are already installed.
* 2023-12-16 03:09:23 (4260) [INFO] 
* 2023-12-16 03:09:40 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-16 03:09:40 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/L8nF6KVbGw/ea_profile.json
* 2023-12-16 03:09:41 (2294) [INFO] Backed up EA4 profile to /tmp/L8nF6KVbGw/ea_profile.json
* 2023-12-16 03:09:43 (271) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-12-17 03:09:11 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-17 03:09:11 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-17 03:09:11 (4230) [INFO] 
* 2023-12-17 03:09:11 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-17 03:09:11 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-17 03:09:11 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-17 03:09:11 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-17 03:09:11 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-17 03:09:11 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-17 03:09:11 (4260) [INFO] 
* 2023-12-17 03:09:11 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-17 03:09:11 (4230) [INFO] 
* 2023-12-17 03:09:28 (4243) [INFO] 
* 2023-12-17 03:09:28 (4243) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-17 03:09:28 (4260) [INFO] 
* 2023-12-17 03:09:28 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-17 03:09:28 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-17 03:09:46 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-17 03:09:46 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/0AYVIVoni1/ea_profile.json
* 2023-12-17 03:09:46 (2294) [INFO] Backed up EA4 profile to /tmp/0AYVIVoni1/ea_profile.json
* 2023-12-17 03:09:48 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-18 03:08:38 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-18 03:08:38 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-18 03:08:38 (4230) [INFO] 
* 2023-12-18 03:08:39 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-18 03:08:39 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-18 03:08:39 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-18 03:08:39 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-18 03:08:39 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-18 03:08:39 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-18 03:08:39 (4260) [INFO] 
* 2023-12-18 03:08:39 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-18 03:08:39 (4230) [INFO] 
* 2023-12-18 03:08:53 (4243) [INFO] 
* 2023-12-18 03:08:53 (4243) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-18 03:08:53 (4260) [INFO] 
* 2023-12-18 03:08:53 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-18 03:08:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-18 03:09:12 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-18 03:09:12 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4_qLsnuLj4/ea_profile.json
* 2023-12-18 03:09:13 (2294) [INFO] Backed up EA4 profile to /tmp/4_qLsnuLj4/ea_profile.json
* 2023-12-18 03:09:14 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-19 03:08:34 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-19 03:08:34 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-19 03:08:34 (4230) [INFO] 
* 2023-12-19 03:08:34 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-19 03:08:35 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-19 03:08:35 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-19 03:08:35 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-19 03:08:35 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-19 03:08:35 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-19 03:08:35 (4260) [INFO] 
* 2023-12-19 03:08:35 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-19 03:08:35 (4230) [INFO] 
* 2023-12-19 03:08:48 (4243) [INFO] 
* 2023-12-19 03:08:48 (4243) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-19 03:08:48 (4260) [INFO] 
* 2023-12-19 03:08:48 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-19 03:08:48 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-19 03:09:03 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-19 03:09:03 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fTjzJQZkpI/ea_profile.json
* 2023-12-19 03:09:04 (2294) [INFO] Backed up EA4 profile to /tmp/fTjzJQZkpI/ea_profile.json
* 2023-12-19 03:09:05 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-20 03:08:36 (1753) [INFO] Checking if your system is up to date: 
* 2023-12-20 03:08:36 (4229) [INFO] Running: /usr/bin/yum clean all
* 2023-12-20 03:08:36 (4230) [INFO] 
* 2023-12-20 03:08:36 (4243) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-20 03:08:36 (4243) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-20 03:08:36 (4243) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-20 03:08:36 (4243) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-20 03:08:36 (4243) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-20 03:08:36 (4243) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-20 03:08:36 (4260) [INFO] 
* 2023-12-20 03:08:36 (4229) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-20 03:08:36 (4230) [INFO] 
* 2023-12-20 03:08:53 (4243) [INFO] 
* 2023-12-20 03:08:53 (4243) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-20 03:08:53 (4260) [INFO] 
* 2023-12-20 03:08:53 (1760) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-20 03:08:53 (155) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-20 03:09:10 (815) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-20 03:09:10 (2271) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4ODb94o8OC/ea_profile.json
* 2023-12-20 03:09:11 (2294) [INFO] Backed up EA4 profile to /tmp/4ODb94o8OC/ea_profile.json
* 2023-12-20 03:09:13 (260) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-21 03:09:02 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-21 03:09:02 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-21 03:09:02 (4251) [INFO] 
* 2023-12-21 03:09:02 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-21 03:09:02 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-21 03:09:02 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-21 03:09:02 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-21 03:09:02 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-21 03:09:02 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-21 03:09:03 (4281) [INFO] 
* 2023-12-21 03:09:03 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-21 03:09:03 (4251) [INFO] 
* 2023-12-21 03:09:27 (4264) [INFO] 
* 2023-12-21 03:09:27 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-21 03:09:27 (4281) [INFO] 
* 2023-12-21 03:09:27 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-21 03:09:27 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-21 03:09:45 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-21 03:09:45 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5_OWBGq8s6/ea_profile.json
* 2023-12-21 03:09:46 (2315) [INFO] Backed up EA4 profile to /tmp/5_OWBGq8s6/ea_profile.json
* 2023-12-21 03:09:47 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-22 03:08:56 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-22 03:08:56 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-22 03:08:56 (4251) [INFO] 
* 2023-12-22 03:08:56 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-22 03:08:56 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-22 03:08:56 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-22 03:08:56 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-22 03:08:56 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-22 03:08:56 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-22 03:08:56 (4281) [INFO] 
* 2023-12-22 03:08:56 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-22 03:08:56 (4251) [INFO] 
* 2023-12-22 03:09:16 (4264) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-22 03:09:16 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:16 (4264) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-22 03:09:16 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:17 (4264) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-22 03:09:17 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:26 (4264) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-12-22 03:09:26 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:31 (4264) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-22 03:09:31 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:46 (4264) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2023-12-22 03:09:46 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:50 (4264) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-12-22 03:09:50 (4264) [INFO] Trying other mirror.
* 2023-12-22 03:09:52 (4264) [INFO] 
* 2023-12-22 03:09:52 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-22 03:09:52 (4281) [INFO] 
* 2023-12-22 03:09:52 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-22 03:09:52 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-22 03:10:40 (1633) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2023-12-22 03:10:40 (1634) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/c7713980b53aa9c6ad51c0a722e717e48adcce56052b827bea2971880f50a85d-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2023-12-22 03:10:40 (161) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2023-12-22 03:10:41 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-22 03:10:41 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/vOhf_hSbHo/ea_profile.json
* 2023-12-22 03:10:51 (2315) [INFO] Backed up EA4 profile to /tmp/vOhf_hSbHo/ea_profile.json
* 2023-12-22 03:10:53 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-23 03:09:10 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-23 03:09:10 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-23 03:09:10 (4251) [INFO] 
* 2023-12-23 03:09:10 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-23 03:09:10 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-23 03:09:10 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-23 03:09:10 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-23 03:09:10 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-23 03:09:10 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-23 03:09:10 (4281) [INFO] 
* 2023-12-23 03:09:10 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-23 03:09:10 (4251) [INFO] 
* 2023-12-23 03:09:35 (4264) [INFO] Traceback (most recent call last):
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2023-12-23 03:09:35 (4264) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2023-12-23 03:09:35 (4264) [INFO]     errcode = main(args)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2023-12-23 03:09:35 (4264) [INFO]     result, resultmsgs = base.doCommands()
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2023-12-23 03:09:35 (4264) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2023-12-23 03:09:35 (4264) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2023-12-23 03:09:35 (4264) [INFO]     ignore_case=True, repoid=repoid)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2023-12-23 03:09:35 (4264) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2023-12-23 03:09:35 (4264) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2023-12-23 03:09:35 (4264) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2023-12-23 03:09:35 (4264) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2023-12-23 03:09:35 (4264) [INFO]     self.repos.populateSack(which=repos)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 386, in populateSack
* 2023-12-23 03:09:35 (4264) [INFO]     sack.populate(repo, mdtype, callback, cacheonly)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 242, in populate
* 2023-12-23 03:09:35 (4264) [INFO]     mydbtype)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2023-12-23 03:09:35 (4264) [INFO]     cached=repo.cache)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2023-12-23 03:09:35 (4264) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2023-12-23 03:09:35 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2023-12-23 03:09:35 (4264) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2023-12-23 03:09:35 (4264) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite'
* 2023-12-23 03:09:35 (4281) [INFO] 
* 2023-12-23 03:09:35 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-23 03:09:35 (1795) [INFO] Checking /scripts/sysup
* 2023-12-23 03:09:35 (4250) [INFO] Running: /scripts/sysup
* 2023-12-23 03:09:35 (4251) [INFO] 
* 2023-12-23 03:09:35 (4264) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-23 03:09:35 (4264) [INFO]   All Needed Packages are already installed.
* 2023-12-23 03:09:35 (4281) [INFO] 
* 2023-12-23 03:09:58 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-23 03:09:58 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Q2UY5Ur1Ly/ea_profile.json
* 2023-12-23 03:09:59 (2315) [INFO] Backed up EA4 profile to /tmp/Q2UY5Ur1Ly/ea_profile.json
* 2023-12-23 03:10:00 (279) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-12-24 03:09:11 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-24 03:09:11 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-24 03:09:11 (4251) [INFO] 
* 2023-12-24 03:09:11 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-24 03:09:11 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-24 03:09:11 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-24 03:09:11 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-24 03:09:11 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-24 03:09:11 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-24 03:09:11 (4281) [INFO] 
* 2023-12-24 03:09:11 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-24 03:09:11 (4251) [INFO] 
* 2023-12-24 03:09:23 (4264) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/29bae346a33a3896aed01ddf4cef0cff53f8ecff1c6392c979e7a9ffb133abe0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-24 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-24 03:09:35 (4264) [INFO] 
* 2023-12-24 03:09:35 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-24 03:09:35 (4281) [INFO] 
* 2023-12-24 03:09:35 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-24 03:09:35 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-24 03:09:57 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-24 03:09:57 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/gZogD__xmR/ea_profile.json
* 2023-12-24 03:09:58 (2315) [INFO] Backed up EA4 profile to /tmp/gZogD__xmR/ea_profile.json
* 2023-12-24 03:09:59 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-25 03:08:38 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-25 03:08:38 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-25 03:08:38 (4251) [INFO] 
* 2023-12-25 03:08:38 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-25 03:08:38 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-25 03:08:38 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-25 03:08:38 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-25 03:08:38 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-25 03:08:38 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-25 03:08:38 (4281) [INFO] 
* 2023-12-25 03:08:38 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-25 03:08:38 (4251) [INFO] 
* 2023-12-25 03:08:52 (4264) [INFO] 
* 2023-12-25 03:08:52 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-25 03:08:53 (4281) [INFO] 
* 2023-12-25 03:08:53 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-25 03:08:53 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-25 03:09:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-25 03:09:11 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OMMAe19sBi/ea_profile.json
* 2023-12-25 03:09:12 (2315) [INFO] Backed up EA4 profile to /tmp/OMMAe19sBi/ea_profile.json
* 2023-12-25 03:09:14 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-26 03:08:41 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-26 03:08:41 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-26 03:08:41 (4251) [INFO] 
* 2023-12-26 03:08:41 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-26 03:08:41 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-26 03:08:41 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-26 03:08:41 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-26 03:08:41 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-26 03:08:41 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-26 03:08:41 (4281) [INFO] 
* 2023-12-26 03:08:41 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-26 03:08:41 (4251) [INFO] 
* 2023-12-26 03:09:01 (4264) [INFO] 
* 2023-12-26 03:09:01 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-26 03:09:01 (4281) [INFO] 
* 2023-12-26 03:09:01 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-26 03:09:01 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-26 03:09:27 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-26 03:09:27 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/_lN87CweMZ/ea_profile.json
* 2023-12-26 03:09:28 (2315) [INFO] Backed up EA4 profile to /tmp/_lN87CweMZ/ea_profile.json
* 2023-12-26 03:09:29 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-27 03:08:48 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-27 03:08:48 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-27 03:08:48 (4251) [INFO] 
* 2023-12-27 03:08:48 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-27 03:08:48 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-27 03:08:48 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-27 03:08:48 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-27 03:08:48 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-27 03:08:48 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-27 03:08:48 (4281) [INFO] 
* 2023-12-27 03:08:48 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-27 03:08:48 (4251) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]  One of the configured repositories failed (Unknown),
* 2023-12-27 03:09:11 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2023-12-27 03:09:11 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2023-12-27 03:09:11 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2023-12-27 03:09:11 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2023-12-27 03:09:11 (4264) [INFO]         packages for the previous distribution release still work).
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2023-12-27 03:09:11 (4264) [INFO]             yum --disablerepo=<repoid> ...
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2023-12-27 03:09:11 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2023-12-27 03:09:11 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]             yum-config-manager --disable <repoid>
* 2023-12-27 03:09:11 (4264) [INFO]         or
* 2023-12-27 03:09:11 (4264) [INFO]             subscription-manager repos --disable=<repoid>
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2023-12-27 03:09:11 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2023-12-27 03:09:11 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2023-12-27 03:09:11 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2023-12-27 03:09:11 (4264) [INFO]         compromise:
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2023-12-27 03:09:11 (4264) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO] updates: Check uncompressed DB failed
* 2023-12-27 03:09:11 (4281) [INFO] 
* 2023-12-27 03:09:11 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-27 03:09:11 (1795) [INFO] Checking /scripts/sysup
* 2023-12-27 03:09:11 (4250) [INFO] Running: /scripts/sysup
* 2023-12-27 03:09:11 (4251) [INFO] 
* 2023-12-27 03:09:11 (4264) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2023-12-27 03:09:12 (4264) [INFO]   All Needed Packages are already installed.
* 2023-12-27 03:09:12 (4281) [INFO] 
* 2023-12-27 03:09:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-27 03:09:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Lglgjep6py/ea_profile.json
* 2023-12-27 03:09:39 (2315) [INFO] Backed up EA4 profile to /tmp/Lglgjep6py/ea_profile.json
* 2023-12-27 03:09:40 (279) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2023-12-28 03:08:46 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-28 03:08:46 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-28 03:08:46 (4251) [INFO] 
* 2023-12-28 03:08:46 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-28 03:08:46 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-28 03:08:46 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-28 03:08:46 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-28 03:08:46 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-28 03:08:46 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-28 03:08:47 (4281) [INFO] 
* 2023-12-28 03:08:47 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-28 03:08:47 (4251) [INFO] 
* 2023-12-28 03:09:11 (4264) [INFO] 
* 2023-12-28 03:09:11 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-28 03:09:11 (4281) [INFO] 
* 2023-12-28 03:09:11 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-28 03:09:11 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-28 03:09:42 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-28 03:09:42 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/myHUC9EUbw/ea_profile.json
* 2023-12-28 03:09:43 (2315) [INFO] Backed up EA4 profile to /tmp/myHUC9EUbw/ea_profile.json
* 2023-12-28 03:09:44 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-29 03:08:43 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-29 03:08:43 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-29 03:08:43 (4251) [INFO] 
* 2023-12-29 03:08:43 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-29 03:08:43 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-29 03:08:43 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-29 03:08:43 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-29 03:08:43 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-29 03:08:43 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-29 03:08:43 (4281) [INFO] 
* 2023-12-29 03:08:43 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-29 03:08:43 (4251) [INFO] 
* 2023-12-29 03:09:03 (4264) [INFO] 
* 2023-12-29 03:09:03 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-29 03:09:03 (4281) [INFO] 
* 2023-12-29 03:09:03 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-29 03:09:03 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-29 03:09:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-29 03:09:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IdNNYZovND/ea_profile.json
* 2023-12-29 03:09:39 (2315) [INFO] Backed up EA4 profile to /tmp/IdNNYZovND/ea_profile.json
* 2023-12-29 03:09:40 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-30 03:09:25 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-30 03:09:25 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-30 03:09:25 (4251) [INFO] 
* 2023-12-30 03:09:25 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-30 03:09:25 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-30 03:09:25 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-30 03:09:25 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-30 03:09:25 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-30 03:09:25 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-30 03:09:25 (4281) [INFO] 
* 2023-12-30 03:09:25 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-30 03:09:25 (4251) [INFO] 
* 2023-12-30 03:09:39 (4264) [INFO] 
* 2023-12-30 03:09:39 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-30 03:09:39 (4281) [INFO] 
* 2023-12-30 03:09:39 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-30 03:09:39 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-30 03:09:59 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-30 03:09:59 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/iA7BipnWNm/ea_profile.json
* 2023-12-30 03:10:00 (2315) [INFO] Backed up EA4 profile to /tmp/iA7BipnWNm/ea_profile.json
* 2023-12-30 03:10:02 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2023-12-31 03:09:16 (1774) [INFO] Checking if your system is up to date: 
* 2023-12-31 03:09:16 (4250) [INFO] Running: /usr/bin/yum clean all
* 2023-12-31 03:09:16 (4251) [INFO] 
* 2023-12-31 03:09:16 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2023-12-31 03:09:16 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2023-12-31 03:09:16 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2023-12-31 03:09:16 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2023-12-31 03:09:16 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2023-12-31 03:09:16 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2023-12-31 03:09:16 (4281) [INFO] 
* 2023-12-31 03:09:16 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2023-12-31 03:09:16 (4251) [INFO] 
* 2023-12-31 03:09:23 (4264) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/1c30388951df9fcfe1df20751d3575d58b9b23d93912a59bfe5e08860dfae5bd-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/356e3ccc9c1d3069701db41f31987a9ce8ccfd8432dd58a385e1e95ac8c08170-updateinfo.xml.gz: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/64a84a35fa21c74632d08c540feee458998bf18825ec1265be77285d24b13351-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/a19e56639c1623ad052b69b8f7483fd4938f388a0328617a2b4571bef20cccfb-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] http://178.18.193.52/cpanelsync/repos/CentOS/7/EA4/repodata/0d1ce7b04cbcf856d0734837626eac3392d719c21b54b10f23e80190dc22eac4-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:23 (4264) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:23 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.13/wp-toolkit/repodata/69c3d9cd3c88bbf364bb0876a71e7c43c4703f8abb92cb9540240fefe80c6998-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.13/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:24 (4264) [INFO] http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:24 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/29bae346a33a3896aed01ddf4cef0cff53f8ecff1c6392c979e7a9ffb133abe0-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://31.22.112.31/cpanelsync/repos/CentOS/7/EA4/repodata/0d1ce7b04cbcf856d0734837626eac3392d719c21b54b10f23e80190dc22eac4-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://mirror.softaculous.com/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://centosmirror.netcup.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://centosmirror.netcup.net/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://centos.bio.lmu.de/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://mirror.netcologne.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://ftp.agdsn.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://84.95.247.234/cpanelsync/repos/CentOS/7/EA4/repodata/0d1ce7b04cbcf856d0734837626eac3392d719c21b54b10f23e80190dc22eac4-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:25 (4264) [INFO] http://mirror.rackspeed.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2023-12-31 03:09:25 (4264) [INFO] Trying other mirror.
* 2023-12-31 03:09:36 (4264) [INFO] 
* 2023-12-31 03:09:36 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2023-12-31 03:09:36 (4281) [INFO] 
* 2023-12-31 03:09:36 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2023-12-31 03:09:36 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2023-12-31 03:09:56 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2023-12-31 03:09:56 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/uLMI9Pb6oA/ea_profile.json
* 2023-12-31 03:09:57 (2315) [INFO] Backed up EA4 profile to /tmp/uLMI9Pb6oA/ea_profile.json
* 2023-12-31 03:09:58 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-01 03:08:43 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-01 03:08:43 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-01 03:08:43 (4251) [INFO] 
* 2024-01-01 03:08:43 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-01 03:08:43 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-01 03:08:43 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-01 03:08:43 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-01 03:08:43 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-01 03:08:43 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-01 03:08:43 (4281) [INFO] 
* 2024-01-01 03:08:43 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-01 03:08:43 (4251) [INFO] 
* 2024-01-01 03:09:00 (4264) [INFO] 
* 2024-01-01 03:09:00 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-01 03:09:00 (4281) [INFO] 
* 2024-01-01 03:09:00 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-01 03:09:00 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-01 03:09:29 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-01 03:09:29 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IB57RB5qGR/ea_profile.json
* 2024-01-01 03:09:29 (2315) [INFO] Backed up EA4 profile to /tmp/IB57RB5qGR/ea_profile.json
* 2024-01-01 03:09:31 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-02 03:08:38 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-02 03:08:38 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-02 03:08:38 (4251) [INFO] 
* 2024-01-02 03:08:38 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-02 03:08:38 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-02 03:08:38 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-02 03:08:38 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-02 03:08:38 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-02 03:08:38 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-02 03:08:38 (4281) [INFO] 
* 2024-01-02 03:08:38 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-02 03:08:38 (4251) [INFO] 
* 2024-01-02 03:08:54 (4264) [INFO] 
* 2024-01-02 03:08:54 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-02 03:08:54 (4281) [INFO] 
* 2024-01-02 03:08:54 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-02 03:08:54 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-02 03:09:13 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-02 03:09:13 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/SY2pB3OWtZ/ea_profile.json
* 2024-01-02 03:09:14 (2315) [INFO] Backed up EA4 profile to /tmp/SY2pB3OWtZ/ea_profile.json
* 2024-01-02 03:09:16 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-03 03:08:42 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-03 03:08:42 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-03 03:08:42 (4251) [INFO] 
* 2024-01-03 03:08:42 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-03 03:08:42 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-03 03:08:42 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-03 03:08:42 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-03 03:08:42 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-03 03:08:42 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-03 03:08:42 (4281) [INFO] 
* 2024-01-03 03:08:42 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-03 03:08:42 (4251) [INFO] 
* 2024-01-03 03:09:13 (4264) [INFO] 
* 2024-01-03 03:09:13 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-03 03:09:13 (4281) [INFO] 
* 2024-01-03 03:09:13 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-03 03:09:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-03 03:09:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-03 03:09:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XFGWLjLHCm/ea_profile.json
* 2024-01-03 03:09:39 (2315) [INFO] Backed up EA4 profile to /tmp/XFGWLjLHCm/ea_profile.json
* 2024-01-03 03:09:41 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-04 03:08:59 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-04 03:08:59 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-04 03:08:59 (4251) [INFO] 
* 2024-01-04 03:08:59 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-04 03:08:59 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-04 03:08:59 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-04 03:08:59 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-04 03:08:59 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-04 03:08:59 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-04 03:08:59 (4281) [INFO] 
* 2024-01-04 03:08:59 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-04 03:08:59 (4251) [INFO] 
* 2024-01-04 03:09:10 (4264) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2024-01-04 03:09:10 (4264) [INFO] Trying other mirror.
* 2024-01-04 03:09:28 (4264) [INFO] 
* 2024-01-04 03:09:28 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-04 03:09:28 (4281) [INFO] 
* 2024-01-04 03:09:28 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-04 03:09:28 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-04 03:09:51 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-04 03:09:51 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d3O63qsX2o/ea_profile.json
* 2024-01-04 03:09:52 (2315) [INFO] Backed up EA4 profile to /tmp/d3O63qsX2o/ea_profile.json
* 2024-01-04 03:09:53 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-05 03:08:43 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-05 03:08:43 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-05 03:08:43 (4251) [INFO] 
* 2024-01-05 03:08:44 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-05 03:08:44 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-05 03:08:44 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-05 03:08:44 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-05 03:08:44 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-05 03:08:44 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-05 03:08:44 (4281) [INFO] 
* 2024-01-05 03:08:44 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-05 03:08:44 (4251) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]  One of the configured repositories failed (Unknown),
* 2024-01-05 03:09:17 (4264) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-05 03:09:17 (4264) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-05 03:09:17 (4264) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-05 03:09:17 (4264) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-05 03:09:17 (4264) [INFO]         packages for the previous distribution release still work).
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-05 03:09:17 (4264) [INFO]             yum --disablerepo=<repoid> ...
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-05 03:09:17 (4264) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-05 03:09:17 (4264) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]             yum-config-manager --disable <repoid>
* 2024-01-05 03:09:17 (4264) [INFO]         or
* 2024-01-05 03:09:17 (4264) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-05 03:09:17 (4264) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-05 03:09:17 (4264) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-05 03:09:17 (4264) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-05 03:09:17 (4264) [INFO]         compromise:
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-05 03:09:17 (4264) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO] updates: Check uncompressed DB failed
* 2024-01-05 03:09:17 (4281) [INFO] 
* 2024-01-05 03:09:17 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-05 03:09:17 (1795) [INFO] Checking /scripts/sysup
* 2024-01-05 03:09:17 (4250) [INFO] Running: /scripts/sysup
* 2024-01-05 03:09:17 (4251) [INFO] 
* 2024-01-05 03:09:17 (4264) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-05 03:09:18 (4264) [INFO]   All Needed Packages are already installed.
* 2024-01-05 03:09:18 (4281) [INFO] 
* 2024-01-05 03:09:53 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-05 03:09:53 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/IRai1saTE4/ea_profile.json
* 2024-01-05 03:09:54 (2315) [INFO] Backed up EA4 profile to /tmp/IRai1saTE4/ea_profile.json
* 2024-01-05 03:09:56 (279) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2024-01-06 03:09:26 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-06 03:09:26 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-06 03:09:26 (4251) [INFO] 
* 2024-01-06 03:09:26 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-06 03:09:27 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-06 03:09:27 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-06 03:09:27 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-06 03:09:27 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-06 03:09:27 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-06 03:09:27 (4281) [INFO] 
* 2024-01-06 03:09:27 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-06 03:09:27 (4251) [INFO] 
* 2024-01-06 03:09:43 (4264) [INFO] 
* 2024-01-06 03:09:43 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-06 03:09:44 (4281) [INFO] 
* 2024-01-06 03:09:44 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-06 03:09:44 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-06 03:10:08 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-06 03:10:08 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/j8Ken_cX7B/ea_profile.json
* 2024-01-06 03:10:09 (2315) [INFO] Backed up EA4 profile to /tmp/j8Ken_cX7B/ea_profile.json
* 2024-01-06 03:10:10 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-07 03:09:25 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-07 03:09:25 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-07 03:09:25 (4251) [INFO] 
* 2024-01-07 03:09:25 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-07 03:09:25 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-07 03:09:25 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-07 03:09:25 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-07 03:09:25 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-07 03:09:25 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-07 03:09:25 (4281) [INFO] 
* 2024-01-07 03:09:25 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-07 03:09:25 (4251) [INFO] 
* 2024-01-07 03:09:40 (4264) [INFO] 
* 2024-01-07 03:09:40 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-07 03:09:40 (4281) [INFO] 
* 2024-01-07 03:09:40 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-07 03:09:40 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-07 03:09:58 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-07 03:09:58 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Dn5YdgVf4N/ea_profile.json
* 2024-01-07 03:09:59 (2315) [INFO] Backed up EA4 profile to /tmp/Dn5YdgVf4N/ea_profile.json
* 2024-01-07 03:10:00 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-08 03:08:42 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-08 03:08:42 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-08 03:08:42 (4251) [INFO] 
* 2024-01-08 03:08:43 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-08 03:08:43 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-08 03:08:43 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-08 03:08:43 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-08 03:08:43 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-08 03:08:43 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-08 03:08:43 (4281) [INFO] 
* 2024-01-08 03:08:43 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-08 03:08:43 (4251) [INFO] 
* 2024-01-08 03:09:11 (4264) [INFO] 
* 2024-01-08 03:09:11 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-08 03:09:11 (4281) [INFO] 
* 2024-01-08 03:09:11 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-08 03:09:11 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-08 03:09:45 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-08 03:09:45 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/AligcNFPi8/ea_profile.json
* 2024-01-08 03:09:46 (2315) [INFO] Backed up EA4 profile to /tmp/AligcNFPi8/ea_profile.json
* 2024-01-08 03:09:47 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-09 03:08:51 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-09 03:08:51 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-09 03:08:51 (4251) [INFO] 
* 2024-01-09 03:08:51 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-09 03:08:52 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-09 03:08:52 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-09 03:08:52 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-09 03:08:52 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-09 03:08:52 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-09 03:08:52 (4281) [INFO] 
* 2024-01-09 03:08:52 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-09 03:08:52 (4251) [INFO] 
* 2024-01-09 03:09:02 (4264) [INFO] Traceback (most recent call last):
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2024-01-09 03:09:02 (4264) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2024-01-09 03:09:02 (4264) [INFO]     errcode = main(args)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2024-01-09 03:09:02 (4264) [INFO]     result, resultmsgs = base.doCommands()
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2024-01-09 03:09:02 (4264) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2024-01-09 03:09:02 (4264) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2024-01-09 03:09:02 (4264) [INFO]     ignore_case=True, repoid=repoid)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2024-01-09 03:09:02 (4264) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2024-01-09 03:09:02 (4264) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2024-01-09 03:09:02 (4264) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2024-01-09 03:09:02 (4264) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2024-01-09 03:09:02 (4264) [INFO]     self.repos.populateSack(which=repos)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2024-01-09 03:09:02 (4264) [INFO]     sack._retrieve_async(repo, data)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2024-01-09 03:09:02 (4264) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2024-01-09 03:09:02 (4264) [INFO]     cached=repo.cache)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2024-01-09 03:09:02 (4264) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2024-01-09 03:09:02 (4264) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2024-01-09 03:09:02 (4264) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2024-01-09 03:09:02 (4264) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/EA4/gen/primary_db.sqlite'
* 2024-01-09 03:09:02 (4281) [INFO] 
* 2024-01-09 03:09:02 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-09 03:09:02 (1795) [INFO] Checking /scripts/sysup
* 2024-01-09 03:09:02 (4250) [INFO] Running: /scripts/sysup
* 2024-01-09 03:09:02 (4251) [INFO] 
* 2024-01-09 03:09:03 (4264) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-09 03:09:03 (4264) [INFO]   All Needed Packages are already installed.
* 2024-01-09 03:09:03 (4281) [INFO] 
* 2024-01-09 03:09:32 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-09 03:09:32 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Fq9dFTecXO/ea_profile.json
* 2024-01-09 03:09:33 (2315) [INFO] Backed up EA4 profile to /tmp/Fq9dFTecXO/ea_profile.json
* 2024-01-09 03:09:34 (279) [INFO] There is no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2024-01-10 03:08:44 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-10 03:08:44 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-10 03:08:44 (4251) [INFO] 
* 2024-01-10 03:08:44 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-10 03:08:44 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-10 03:08:44 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-10 03:08:44 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-10 03:08:44 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-10 03:08:44 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-10 03:08:44 (4281) [INFO] 
* 2024-01-10 03:08:44 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-10 03:08:44 (4251) [INFO] 
* 2024-01-10 03:09:10 (4264) [INFO] 
* 2024-01-10 03:09:10 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-10 03:09:10 (4281) [INFO] 
* 2024-01-10 03:09:10 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-10 03:09:10 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-10 03:09:38 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-10 03:09:38 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/YnA2S8Ln5J/ea_profile.json
* 2024-01-10 03:09:39 (2315) [INFO] Backed up EA4 profile to /tmp/YnA2S8Ln5J/ea_profile.json
* 2024-01-10 03:09:41 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-11 03:09:05 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-11 03:09:05 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-11 03:09:05 (4251) [INFO] 
* 2024-01-11 03:09:05 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-11 03:09:05 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-11 03:09:05 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-11 03:09:05 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-11 03:09:05 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-11 03:09:05 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-11 03:09:05 (4281) [INFO] 
* 2024-01-11 03:09:05 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-11 03:09:05 (4251) [INFO] 
* 2024-01-11 03:09:23 (4264) [INFO] 
* 2024-01-11 03:09:23 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-11 03:09:23 (4281) [INFO] 
* 2024-01-11 03:09:23 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-11 03:09:23 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-11 03:09:41 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-11 03:09:41 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RLcNrAqaQ4/ea_profile.json
* 2024-01-11 03:09:42 (2315) [INFO] Backed up EA4 profile to /tmp/RLcNrAqaQ4/ea_profile.json
* 2024-01-11 03:09:43 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-12 03:09:00 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-12 03:09:00 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-12 03:09:00 (4251) [INFO] 
* 2024-01-12 03:09:00 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-12 03:09:00 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-12 03:09:00 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-12 03:09:00 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-12 03:09:00 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-12 03:09:00 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-12 03:09:00 (4281) [INFO] 
* 2024-01-12 03:09:00 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-12 03:09:00 (4251) [INFO] 
* 2024-01-12 03:09:22 (4264) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2024-01-12 03:09:22 (4264) [INFO] Trying other mirror.
* 2024-01-12 03:09:22 (4264) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2024-01-12 03:09:22 (4264) [INFO] Trying other mirror.
* 2024-01-12 03:09:41 (4264) [INFO] 
* 2024-01-12 03:09:41 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-12 03:09:41 (4281) [INFO] 
* 2024-01-12 03:09:41 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-12 03:09:41 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-12 03:10:11 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-12 03:10:11 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/LLND3voLiW/ea_profile.json
* 2024-01-12 03:10:12 (2315) [INFO] Backed up EA4 profile to /tmp/LLND3voLiW/ea_profile.json
* 2024-01-12 03:10:13 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-13 03:09:38 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-13 03:09:38 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-13 03:09:38 (4251) [INFO] 
* 2024-01-13 03:09:38 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-13 03:09:38 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-13 03:09:38 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-13 03:09:38 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-13 03:09:38 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-13 03:09:38 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-13 03:09:38 (4281) [INFO] 
* 2024-01-13 03:09:38 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-13 03:09:38 (4251) [INFO] 
* 2024-01-13 03:09:53 (4264) [INFO] 
* 2024-01-13 03:09:53 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-13 03:09:53 (4281) [INFO] 
* 2024-01-13 03:09:53 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-13 03:09:53 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-13 03:10:24 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-13 03:10:24 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/mlLFG18qGM/ea_profile.json
* 2024-01-13 03:10:25 (2315) [INFO] Backed up EA4 profile to /tmp/mlLFG18qGM/ea_profile.json
* 2024-01-13 03:10:26 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-14 03:09:56 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-14 03:09:56 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-14 03:09:56 (4251) [INFO] 
* 2024-01-14 03:09:56 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-14 03:09:57 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-14 03:09:57 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-14 03:09:57 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-14 03:09:57 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-14 03:09:57 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-14 03:09:57 (4281) [INFO] 
* 2024-01-14 03:09:57 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-14 03:09:57 (4251) [INFO] 
* 2024-01-14 03:10:16 (4264) [INFO] 
* 2024-01-14 03:10:16 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-14 03:10:16 (4281) [INFO] 
* 2024-01-14 03:10:16 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-14 03:10:16 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-14 03:10:40 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-14 03:10:40 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/44dlXsBUnk/ea_profile.json
* 2024-01-14 03:10:41 (2315) [INFO] Backed up EA4 profile to /tmp/44dlXsBUnk/ea_profile.json
* 2024-01-14 03:10:42 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-15 03:08:46 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-15 03:08:46 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-15 03:08:46 (4251) [INFO] 
* 2024-01-15 03:08:46 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-15 03:08:46 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-15 03:08:46 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-15 03:08:46 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-15 03:08:46 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-15 03:08:46 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-15 03:08:46 (4281) [INFO] 
* 2024-01-15 03:08:46 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-15 03:08:46 (4251) [INFO] 
* 2024-01-15 03:09:13 (4264) [INFO] 
* 2024-01-15 03:09:13 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-15 03:09:13 (4281) [INFO] 
* 2024-01-15 03:09:13 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-15 03:09:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-15 03:09:40 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-15 03:09:40 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MQ75NBmdzx/ea_profile.json
* 2024-01-15 03:09:41 (2315) [INFO] Backed up EA4 profile to /tmp/MQ75NBmdzx/ea_profile.json
* 2024-01-15 03:09:43 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-16 03:08:48 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-16 03:08:48 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-16 03:08:48 (4251) [INFO] 
* 2024-01-16 03:08:48 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-16 03:08:49 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-16 03:08:49 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-16 03:08:49 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-16 03:08:49 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-16 03:08:49 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-16 03:08:49 (4281) [INFO] 
* 2024-01-16 03:08:49 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-16 03:08:49 (4251) [INFO] 
* 2024-01-16 03:09:13 (4264) [INFO] 
* 2024-01-16 03:09:13 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-16 03:09:13 (4281) [INFO] 
* 2024-01-16 03:09:13 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-16 03:09:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-16 03:09:42 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-16 03:09:42 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XGSc0fUAH_/ea_profile.json
* 2024-01-16 03:09:43 (2315) [INFO] Backed up EA4 profile to /tmp/XGSc0fUAH_/ea_profile.json
* 2024-01-16 03:09:45 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-17 03:10:00 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-17 03:10:00 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-17 03:10:00 (4251) [INFO] 
* 2024-01-17 03:10:00 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-17 03:10:00 (4264) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 3944.
* 2024-01-17 03:10:00 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:00 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:00 (4264) [INFO]     Memory :  30 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:00 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:05 ago
* 2024-01-17 03:10:00 (4264) [INFO]     State  : Sleeping, pid: 3944
* 2024-01-17 03:10:02 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:02 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:02 (4264) [INFO]     Memory :  30 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:02 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:07 ago
* 2024-01-17 03:10:02 (4264) [INFO]     State  : Sleeping, pid: 3944
* 2024-01-17 03:10:04 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:04 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:04 (4264) [INFO]     Memory :  35 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:04 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:09 ago
* 2024-01-17 03:10:04 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:06 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:06 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:06 (4264) [INFO]     Memory :  35 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:06 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:11 ago
* 2024-01-17 03:10:06 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:08 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:08 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:08 (4264) [INFO]     Memory :  35 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:08 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:13 ago
* 2024-01-17 03:10:08 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:10 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:10 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:10 (4264) [INFO]     Memory :  35 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:10 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:15 ago
* 2024-01-17 03:10:10 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:12 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:12 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:12 (4264) [INFO]     Memory :  35 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:12 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:17 ago
* 2024-01-17 03:10:12 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:14 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:14 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:14 (4264) [INFO]     Memory :  47 M RSS (3.2 GB VSZ)
* 2024-01-17 03:10:14 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:19 ago
* 2024-01-17 03:10:14 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:16 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:16 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:16 (4264) [INFO]     Memory : 115 M RSS (3.3 GB VSZ)
* 2024-01-17 03:10:16 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:21 ago
* 2024-01-17 03:10:16 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:18 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:18 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:18 (4264) [INFO]     Memory : 129 M RSS (3.3 GB VSZ)
* 2024-01-17 03:10:18 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:23 ago
* 2024-01-17 03:10:18 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:20 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:20 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:20 (4264) [INFO]     Memory : 131 M RSS (3.3 GB VSZ)
* 2024-01-17 03:10:20 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:25 ago
* 2024-01-17 03:10:20 (4264) [INFO]     State  : Uninterruptible, pid: 3944
* 2024-01-17 03:10:22 (4264) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-01-17 03:10:22 (4264) [INFO]   The other application is: yum
* 2024-01-17 03:10:22 (4264) [INFO]     Memory : 153 M RSS (3.4 GB VSZ)
* 2024-01-17 03:10:22 (4264) [INFO]     Started: Wed Jan 17 03:09:55 2024 - 00:27 ago
* 2024-01-17 03:10:22 (4264) [INFO]     State  : Running, pid: 3944
* 2024-01-17 03:10:24 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-17 03:10:24 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-17 03:10:24 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-17 03:10:24 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-17 03:10:24 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-17 03:10:24 (4264) [INFO] Cleaning up list of fastest mirrors
* 2024-01-17 03:10:24 (4281) [INFO] 
* 2024-01-17 03:10:24 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-17 03:10:24 (4251) [INFO] 
* 2024-01-17 03:10:39 (4264) [INFO] 
* 2024-01-17 03:10:39 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-17 03:10:39 (4281) [INFO] 
* 2024-01-17 03:10:39 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-17 03:10:39 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-17 03:11:01 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-17 03:11:01 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/x0kGTnFcSt/ea_profile.json
* 2024-01-17 03:11:02 (2315) [INFO] Backed up EA4 profile to /tmp/x0kGTnFcSt/ea_profile.json
* 2024-01-17 03:11:04 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-18 03:09:24 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-18 03:09:24 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-18 03:09:24 (4251) [INFO] 
* 2024-01-18 03:09:25 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-18 03:09:25 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-18 03:09:25 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-18 03:09:25 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-18 03:09:25 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-18 03:09:25 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-18 03:09:25 (4281) [INFO] 
* 2024-01-18 03:09:25 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-18 03:09:25 (4251) [INFO] 
* 2024-01-18 03:09:42 (4264) [INFO] 
* 2024-01-18 03:09:42 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-18 03:09:42 (4281) [INFO] 
* 2024-01-18 03:09:42 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-18 03:09:42 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-18 03:10:09 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-18 03:10:09 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XVgFd71wpQ/ea_profile.json
* 2024-01-18 03:10:11 (2315) [INFO] Backed up EA4 profile to /tmp/XVgFd71wpQ/ea_profile.json
* 2024-01-18 03:10:13 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-19 03:08:52 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-19 03:08:52 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-19 03:08:52 (4251) [INFO] 
* 2024-01-19 03:08:52 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-19 03:08:53 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-19 03:08:53 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-19 03:08:53 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-19 03:08:53 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-19 03:08:53 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-19 03:08:53 (4281) [INFO] 
* 2024-01-19 03:08:53 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-19 03:08:53 (4251) [INFO] 
* 2024-01-19 03:09:12 (4264) [INFO] 
* 2024-01-19 03:09:12 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-19 03:09:12 (4281) [INFO] 
* 2024-01-19 03:09:12 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-19 03:09:12 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-19 03:09:44 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-19 03:09:44 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/5L0wqSAZLS/ea_profile.json
* 2024-01-19 03:09:45 (2315) [INFO] Backed up EA4 profile to /tmp/5L0wqSAZLS/ea_profile.json
* 2024-01-19 03:09:47 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-20 03:09:27 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-20 03:09:27 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-20 03:09:27 (4251) [INFO] 
* 2024-01-20 03:09:27 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-20 03:09:27 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-20 03:09:27 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-20 03:09:27 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-20 03:09:27 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-20 03:09:27 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-20 03:09:27 (4281) [INFO] 
* 2024-01-20 03:09:27 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-20 03:09:27 (4251) [INFO] 
* 2024-01-20 03:09:44 (4264) [INFO] 
* 2024-01-20 03:09:44 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-20 03:09:44 (4281) [INFO] 
* 2024-01-20 03:09:44 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-20 03:09:44 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-20 03:10:04 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-20 03:10:04 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/jnoQS1PEzQ/ea_profile.json
* 2024-01-20 03:10:06 (2315) [INFO] Backed up EA4 profile to /tmp/jnoQS1PEzQ/ea_profile.json
* 2024-01-20 03:10:07 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-21 03:09:32 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-21 03:09:32 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-21 03:09:32 (4251) [INFO] 
* 2024-01-21 03:09:32 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-21 03:09:32 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-21 03:09:32 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-21 03:09:32 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-21 03:09:32 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-21 03:09:32 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-21 03:09:32 (4281) [INFO] 
* 2024-01-21 03:09:32 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-21 03:09:32 (4251) [INFO] 
* 2024-01-21 03:09:46 (4264) [INFO] 
* 2024-01-21 03:09:46 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-21 03:09:47 (4281) [INFO] 
* 2024-01-21 03:09:47 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-21 03:09:47 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-21 03:10:09 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-21 03:10:09 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/274mgnaDVK/ea_profile.json
* 2024-01-21 03:10:11 (2315) [INFO] Backed up EA4 profile to /tmp/274mgnaDVK/ea_profile.json
* 2024-01-21 03:10:12 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-22 03:08:40 (1774) [INFO] Checking if your system is up to date: 
* 2024-01-22 03:08:40 (4250) [INFO] Running: /usr/bin/yum clean all
* 2024-01-22 03:08:40 (4251) [INFO] 
* 2024-01-22 03:08:40 (4264) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-22 03:08:41 (4264) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-22 03:08:41 (4264) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-22 03:08:41 (4264) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-22 03:08:41 (4264) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-22 03:08:41 (4264) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-22 03:08:41 (4281) [INFO] 
* 2024-01-22 03:08:41 (4250) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-22 03:08:41 (4251) [INFO] 
* 2024-01-22 03:08:57 (4264) [INFO] 
* 2024-01-22 03:08:57 (4264) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-22 03:08:57 (4281) [INFO] 
* 2024-01-22 03:08:57 (1781) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-22 03:08:57 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-22 03:09:16 (823) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-22 03:09:16 (2292) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Wk12QFAb7d/ea_profile.json
* 2024-01-22 03:09:16 (2315) [INFO] Backed up EA4 profile to /tmp/Wk12QFAb7d/ea_profile.json
* 2024-01-22 03:09:18 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-23 03:08:46 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-23 03:08:46 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-23 03:08:46 (4319) [INFO] 
* 2024-01-23 03:08:46 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-23 03:08:46 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-23 03:08:46 (4332) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-23 03:08:46 (4332) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-23 03:08:46 (4332) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-23 03:08:46 (4332) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-23 03:08:46 (4349) [INFO] 
* 2024-01-23 03:08:46 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-23 03:08:46 (4319) [INFO] 
* 2024-01-23 03:09:04 (4332) [INFO] 
* 2024-01-23 03:09:04 (4332) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-23 03:09:04 (4349) [INFO] 
* 2024-01-23 03:09:04 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-23 03:09:04 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-23 03:09:37 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-23 03:09:37 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/G6jAdCYphL/ea_profile.json
* 2024-01-23 03:09:37 (2383) [INFO] Backed up EA4 profile to /tmp/G6jAdCYphL/ea_profile.json
* 2024-01-23 03:09:39 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-24 03:08:59 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-24 03:08:59 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-24 03:08:59 (4319) [INFO] 
* 2024-01-24 03:09:00 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-24 03:09:00 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-24 03:09:00 (4332) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-24 03:09:00 (4332) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-24 03:09:00 (4332) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-24 03:09:00 (4332) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-24 03:09:00 (4349) [INFO] 
* 2024-01-24 03:09:00 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-24 03:09:00 (4319) [INFO] 
* 2024-01-24 03:09:17 (4332) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/ec7818466ef75a7d5a714d8df3a91008efbd47b0fa223c13bf2f027b65580aad-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-01-24 03:09:17 (4332) [INFO] Trying other mirror.
* 2024-01-24 03:09:17 (4332) [INFO] Traceback (most recent call last):
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2024-01-24 03:09:17 (4332) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2024-01-24 03:09:17 (4332) [INFO]     errcode = main(args)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2024-01-24 03:09:17 (4332) [INFO]     result, resultmsgs = base.doCommands()
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2024-01-24 03:09:17 (4332) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2024-01-24 03:09:17 (4332) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2024-01-24 03:09:17 (4332) [INFO]     ignore_case=True, repoid=repoid)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2024-01-24 03:09:17 (4332) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2024-01-24 03:09:17 (4332) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2024-01-24 03:09:17 (4332) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2024-01-24 03:09:17 (4332) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2024-01-24 03:09:17 (4332) [INFO]     self.repos.populateSack(which=repos)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2024-01-24 03:09:17 (4332) [INFO]     sack._retrieve_async(repo, data)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2024-01-24 03:09:17 (4332) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2024-01-24 03:09:17 (4332) [INFO]     cached=repo.cache)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2024-01-24 03:09:17 (4332) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2024-01-24 03:09:17 (4332) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2024-01-24 03:09:17 (4332) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2024-01-24 03:09:17 (4332) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/EA4/gen/primary_db.sqlite'
* 2024-01-24 03:09:17 (4349) [INFO] 
* 2024-01-24 03:09:17 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-24 03:09:17 (1863) [INFO] Checking /scripts/sysup
* 2024-01-24 03:09:17 (4318) [INFO] Running: /scripts/sysup
* 2024-01-24 03:09:17 (4319) [INFO] 
* 2024-01-24 03:09:18 (4332) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-24 03:09:18 (4332) [INFO]   All Needed Packages are already installed.
* 2024-01-24 03:09:18 (4349) [INFO] 
* 2024-01-24 03:09:45 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-24 03:09:45 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/CmT_Trt5mD/ea_profile.json
* 2024-01-24 03:09:46 (2383) [INFO] Backed up EA4 profile to /tmp/CmT_Trt5mD/ea_profile.json
* 2024-01-24 03:09:48 (279) [INFO] There are no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2024-01-25 03:09:18 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-25 03:09:18 (4318) [INFO] Running: /usr/bin/yum clean all
* 2024-01-25 03:09:18 (4319) [INFO] 
* 2024-01-25 03:09:18 (4332) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-25 03:09:18 (4332) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-25 03:09:18 (4332) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-25 03:09:18 (4332) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-25 03:09:18 (4332) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-25 03:09:18 (4332) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-25 03:09:18 (4349) [INFO] 
* 2024-01-25 03:09:18 (4318) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-25 03:09:18 (4319) [INFO] 
* 2024-01-25 03:09:23 (4332) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/ec7818466ef75a7d5a714d8df3a91008efbd47b0fa223c13bf2f027b65580aad-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-01-25 03:09:23 (4332) [INFO] Trying other mirror.
* 2024-01-25 03:09:32 (4332) [INFO] 
* 2024-01-25 03:09:32 (4332) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-25 03:09:32 (4349) [INFO] 
* 2024-01-25 03:09:32 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-25 03:09:32 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-25 03:09:51 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-25 03:09:51 (2360) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/WjrkLRp8mV/ea_profile.json
* 2024-01-25 03:09:52 (2383) [INFO] Backed up EA4 profile to /tmp/WjrkLRp8mV/ea_profile.json
* 2024-01-25 03:09:54 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-26 03:08:48 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-26 03:08:48 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-26 03:08:48 (4322) [INFO] 
* 2024-01-26 03:08:48 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-26 03:08:48 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-26 03:08:48 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-26 03:08:48 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-26 03:08:48 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-26 03:08:48 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-26 03:08:49 (4352) [INFO] 
* 2024-01-26 03:08:49 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-26 03:08:49 (4322) [INFO] 
* 2024-01-26 03:09:13 (4335) [INFO] 
* 2024-01-26 03:09:13 (4335) [INFO] kernel.x86_64                   3.10.0-1160.105.1.el7                    updates
* 2024-01-26 03:09:13 (4352) [INFO] 
* 2024-01-26 03:09:13 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-26 03:09:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-26 03:09:41 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-26 03:09:41 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/6G1CZg2Sbk/ea_profile.json
* 2024-01-26 03:09:42 (2382) [INFO] Backed up EA4 profile to /tmp/6G1CZg2Sbk/ea_profile.json
* 2024-01-26 03:09:44 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-27 03:10:46 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-27 03:10:46 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-27 03:10:46 (4322) [INFO] 
* 2024-01-27 03:10:46 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-27 03:10:46 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-27 03:10:46 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-27 03:10:46 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-27 03:10:46 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-27 03:10:46 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-27 03:10:46 (4352) [INFO] 
* 2024-01-27 03:10:46 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-27 03:10:46 (4322) [INFO] 
* 2024-01-27 03:11:05 (4335) [INFO] 
* 2024-01-27 03:11:05 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-01-27 03:11:06 (4352) [INFO] 
* 2024-01-27 03:11:06 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-27 03:11:06 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-27 03:11:26 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-27 03:11:26 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DP76izXze5/ea_profile.json
* 2024-01-27 03:11:26 (2382) [INFO] Backed up EA4 profile to /tmp/DP76izXze5/ea_profile.json
* 2024-01-27 03:11:28 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-28 03:09:53 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-28 03:09:53 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-28 03:09:53 (4322) [INFO] 
* 2024-01-28 03:09:53 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-28 03:09:53 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-28 03:09:53 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-28 03:09:53 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-28 03:09:53 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-28 03:09:53 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-28 03:09:53 (4352) [INFO] 
* 2024-01-28 03:09:53 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-28 03:09:53 (4322) [INFO] 
* 2024-01-28 03:10:10 (4335) [INFO] 
* 2024-01-28 03:10:10 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-01-28 03:10:10 (4352) [INFO] 
* 2024-01-28 03:10:10 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-28 03:10:10 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-28 03:10:31 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-28 03:10:31 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/RGjlh7RttY/ea_profile.json
* 2024-01-28 03:10:32 (2382) [INFO] Backed up EA4 profile to /tmp/RGjlh7RttY/ea_profile.json
* 2024-01-28 03:10:33 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-29 03:08:46 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-29 03:08:46 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-29 03:08:46 (4322) [INFO] 
* 2024-01-29 03:08:46 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-29 03:08:46 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-29 03:08:46 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-29 03:08:46 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-29 03:08:46 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-29 03:08:46 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-29 03:08:46 (4352) [INFO] 
* 2024-01-29 03:08:46 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-29 03:08:46 (4322) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]  One of the configured repositories failed (Unknown),
* 2024-01-29 03:09:15 (4335) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-01-29 03:09:15 (4335) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-01-29 03:09:15 (4335) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-01-29 03:09:15 (4335) [INFO]         distribution release than is supported by the repository (and the
* 2024-01-29 03:09:15 (4335) [INFO]         packages for the previous distribution release still work).
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-01-29 03:09:15 (4335) [INFO]             yum --disablerepo=<repoid> ...
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-01-29 03:09:15 (4335) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-01-29 03:09:15 (4335) [INFO]         again or use --enablerepo for temporary usage:
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]             yum-config-manager --disable <repoid>
* 2024-01-29 03:09:15 (4335) [INFO]         or
* 2024-01-29 03:09:15 (4335) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-01-29 03:09:15 (4335) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-01-29 03:09:15 (4335) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-01-29 03:09:15 (4335) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-01-29 03:09:15 (4335) [INFO]         compromise:
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-01-29 03:09:15 (4335) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO] updates: Check uncompressed DB failed
* 2024-01-29 03:09:15 (4352) [INFO] 
* 2024-01-29 03:09:15 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-29 03:09:15 (1863) [INFO] Checking /scripts/sysup
* 2024-01-29 03:09:15 (4321) [INFO] Running: /scripts/sysup
* 2024-01-29 03:09:15 (4322) [INFO] 
* 2024-01-29 03:09:15 (4335) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-01-29 03:09:16 (4335) [INFO]   All Needed Packages are already installed.
* 2024-01-29 03:09:16 (4352) [INFO] 
* 2024-01-29 03:09:47 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-29 03:09:47 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/upoIq3kb5y/ea_profile.json
* 2024-01-29 03:09:48 (2382) [INFO] Backed up EA4 profile to /tmp/upoIq3kb5y/ea_profile.json
* 2024-01-29 03:09:49 (279) [INFO] There are no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2024-01-30 03:08:53 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-30 03:08:53 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-30 03:08:53 (4322) [INFO] 
* 2024-01-30 03:08:53 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-30 03:08:53 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-30 03:08:53 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-30 03:08:53 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-30 03:08:53 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-30 03:08:53 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-30 03:08:53 (4352) [INFO] 
* 2024-01-30 03:08:53 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-30 03:08:53 (4322) [INFO] 
* 2024-01-30 03:09:13 (4335) [INFO] 
* 2024-01-30 03:09:13 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-01-30 03:09:13 (4352) [INFO] 
* 2024-01-30 03:09:13 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-30 03:09:13 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-30 03:09:41 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-30 03:09:41 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Y7ypOHeKG7/ea_profile.json
* 2024-01-30 03:09:42 (2382) [INFO] Backed up EA4 profile to /tmp/Y7ypOHeKG7/ea_profile.json
* 2024-01-30 03:09:44 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-01-31 03:08:52 (1842) [INFO] Checking if your system is up to date: 
* 2024-01-31 03:08:52 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-01-31 03:08:52 (4322) [INFO] 
* 2024-01-31 03:08:52 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-01-31 03:08:52 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-01-31 03:08:52 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-01-31 03:08:52 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-01-31 03:08:52 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-01-31 03:08:52 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-01-31 03:08:52 (4352) [INFO] 
* 2024-01-31 03:08:52 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-01-31 03:08:52 (4322) [INFO] 
* 2024-01-31 03:09:10 (4335) [INFO] 
* 2024-01-31 03:09:10 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-01-31 03:09:10 (4352) [INFO] 
* 2024-01-31 03:09:10 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-01-31 03:09:10 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-01-31 03:09:36 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-01-31 03:09:36 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/24BLgOwDiU/ea_profile.json
* 2024-01-31 03:09:38 (2382) [INFO] Backed up EA4 profile to /tmp/24BLgOwDiU/ea_profile.json
* 2024-01-31 03:09:39 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-01 03:09:08 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-01 03:09:08 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-01 03:09:08 (4322) [INFO] 
* 2024-02-01 03:09:08 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-01 03:09:08 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-01 03:09:08 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-01 03:09:08 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-01 03:09:08 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-01 03:09:08 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-01 03:09:08 (4352) [INFO] 
* 2024-02-01 03:09:08 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-01 03:09:08 (4322) [INFO] 
* 2024-02-01 03:09:27 (4335) [INFO] 
* 2024-02-01 03:09:27 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-01 03:09:27 (4352) [INFO] 
* 2024-02-01 03:09:27 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-01 03:09:27 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-01 03:09:50 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-01 03:09:50 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/u0xdujdaXT/ea_profile.json
* 2024-02-01 03:09:51 (2382) [INFO] Backed up EA4 profile to /tmp/u0xdujdaXT/ea_profile.json
* 2024-02-01 03:09:52 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-02 03:10:08 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-02 03:10:08 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-02 03:10:08 (4322) [INFO] 
* 2024-02-02 03:10:08 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-02 03:10:08 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-02 03:10:08 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-02 03:10:08 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-02 03:10:08 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-02 03:10:08 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-02 03:10:08 (4352) [INFO] 
* 2024-02-02 03:10:08 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-02 03:10:08 (4322) [INFO] 
* 2024-02-02 03:10:24 (4335) [INFO] 
* 2024-02-02 03:10:24 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-02 03:10:24 (4352) [INFO] 
* 2024-02-02 03:10:24 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-02 03:10:24 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-02 03:10:42 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-02 03:10:42 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/fWye_7f1Kj/ea_profile.json
* 2024-02-02 03:10:42 (2382) [INFO] Backed up EA4 profile to /tmp/fWye_7f1Kj/ea_profile.json
* 2024-02-02 03:10:44 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-03 03:09:32 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-03 03:09:32 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-03 03:09:32 (4322) [INFO] 
* 2024-02-03 03:09:32 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-03 03:09:32 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-03 03:09:32 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-03 03:09:32 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-03 03:09:32 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-03 03:09:32 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-03 03:09:32 (4352) [INFO] 
* 2024-02-03 03:09:32 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-03 03:09:32 (4322) [INFO] 
* 2024-02-03 03:09:46 (4335) [INFO] 
* 2024-02-03 03:09:46 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-03 03:09:46 (4352) [INFO] 
* 2024-02-03 03:09:46 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-03 03:09:46 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-03 03:10:06 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-03 03:10:06 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/OWwMGVmyVA/ea_profile.json
* 2024-02-03 03:10:07 (2382) [INFO] Backed up EA4 profile to /tmp/OWwMGVmyVA/ea_profile.json
* 2024-02-03 03:10:09 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-04 03:09:38 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-04 03:09:38 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-04 03:09:38 (4322) [INFO] 
* 2024-02-04 03:09:38 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-04 03:09:38 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-04 03:09:38 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-04 03:09:38 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-04 03:09:38 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-04 03:09:38 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-04 03:09:38 (4352) [INFO] 
* 2024-02-04 03:09:38 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-04 03:09:38 (4322) [INFO] 
* 2024-02-04 03:09:57 (4335) [INFO] 
* 2024-02-04 03:09:57 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-04 03:09:57 (4352) [INFO] 
* 2024-02-04 03:09:57 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-04 03:09:57 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-04 03:10:21 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-04 03:10:21 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/4_bHe44nSu/ea_profile.json
* 2024-02-04 03:10:22 (2382) [INFO] Backed up EA4 profile to /tmp/4_bHe44nSu/ea_profile.json
* 2024-02-04 03:10:24 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-05 03:08:53 (1842) [INFO] Checking if your system is up to date: 
* 2024-02-05 03:08:53 (4321) [INFO] Running: /usr/bin/yum clean all
* 2024-02-05 03:08:53 (4322) [INFO] 
* 2024-02-05 03:08:53 (4335) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-05 03:08:53 (4335) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-05 03:08:53 (4335) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-05 03:08:53 (4335) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-05 03:08:53 (4335) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-05 03:08:53 (4335) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-05 03:08:53 (4352) [INFO] 
* 2024-02-05 03:08:53 (4321) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-05 03:08:53 (4322) [INFO] 
* 2024-02-05 03:09:11 (4335) [INFO] 
* 2024-02-05 03:09:11 (4335) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-05 03:09:11 (4352) [INFO] 
* 2024-02-05 03:09:11 (1849) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-05 03:09:11 (161) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-05 03:09:42 (891) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-05 03:09:42 (2359) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/9T4dCxC6zJ/ea_profile.json
* 2024-02-05 03:09:43 (2382) [INFO] Backed up EA4 profile to /tmp/9T4dCxC6zJ/ea_profile.json
* 2024-02-05 03:09:45 (268) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-06 03:08:42 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-06 03:08:42 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-06 03:08:42 (4416) [INFO] 
* 2024-02-06 03:08:42 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-06 03:08:42 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-06 03:08:42 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-06 03:08:42 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-06 03:08:42 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-06 03:08:42 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-06 03:08:43 (4446) [INFO] 
* 2024-02-06 03:08:43 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-06 03:08:43 (4416) [INFO] 
* 2024-02-06 03:08:59 (4429) [INFO] 
* 2024-02-06 03:08:59 (4429) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-06 03:08:59 (4446) [INFO] 
* 2024-02-06 03:08:59 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-06 03:08:59 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-06 03:09:25 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-06 03:09:25 (1704) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
* 2024-02-06 03:09:25 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-06 03:09:25 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-06 03:09:25 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/Xy8LPIECwU/ea_profile.json
* 2024-02-06 03:09:26 (2436) [INFO] Backed up EA4 profile to /tmp/Xy8LPIECwU/ea_profile.json
* 2024-02-06 03:09:27 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-07 03:08:41 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-07 03:08:41 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-07 03:08:41 (4416) [INFO] 
* 2024-02-07 03:08:41 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-07 03:08:41 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-07 03:08:41 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-07 03:08:41 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-07 03:08:41 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-07 03:08:41 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-07 03:08:41 (4446) [INFO] 
* 2024-02-07 03:08:41 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-07 03:08:41 (4416) [INFO] 
* 2024-02-07 03:09:00 (4429) [INFO] 
* 2024-02-07 03:09:00 (4429) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-07 03:09:00 (4446) [INFO] 
* 2024-02-07 03:09:00 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-07 03:09:00 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-07 03:09:27 (1703) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-07 03:09:27 (1704) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/44e4234513901d96c60da887faa104b900ab5f93139a5b7daadf1eb8abf74306-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2024-02-07 03:09:27 (162) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-07 03:09:27 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-07 03:09:27 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/UhCRuCGKOh/ea_profile.json
* 2024-02-07 03:09:33 (2436) [INFO] Backed up EA4 profile to /tmp/UhCRuCGKOh/ea_profile.json
* 2024-02-07 03:09:34 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-08 03:09:41 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-08 03:09:41 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-08 03:09:41 (4416) [INFO] 
* 2024-02-08 03:09:41 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-08 03:09:41 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-08 03:09:41 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-08 03:09:41 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-08 03:09:41 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-08 03:09:41 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-08 03:09:41 (4446) [INFO] 
* 2024-02-08 03:09:41 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-08 03:09:41 (4416) [INFO] 
* 2024-02-08 03:10:02 (4429) [INFO] 
* 2024-02-08 03:10:02 (4429) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-08 03:10:02 (4446) [INFO] 
* 2024-02-08 03:10:02 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-08 03:10:02 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-08 03:10:22 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-08 03:10:22 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/b_EcYmbRsn/ea_profile.json
* 2024-02-08 03:10:23 (2436) [INFO] Backed up EA4 profile to /tmp/b_EcYmbRsn/ea_profile.json
* 2024-02-08 03:10:24 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-09 03:08:55 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-09 03:08:55 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-09 03:08:55 (4416) [INFO] 
* 2024-02-09 03:08:55 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-09 03:08:55 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-09 03:08:55 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-09 03:08:55 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-09 03:08:55 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-09 03:08:55 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-09 03:08:55 (4446) [INFO] 
* 2024-02-09 03:08:55 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-09 03:08:55 (4416) [INFO] 
* 2024-02-09 03:09:11 (4429) [INFO] 
* 2024-02-09 03:09:11 (4429) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-09 03:09:11 (4446) [INFO] 
* 2024-02-09 03:09:11 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-09 03:09:11 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-09 03:09:42 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-09 03:09:42 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/DS0flSbO2F/ea_profile.json
* 2024-02-09 03:09:43 (2436) [INFO] Backed up EA4 profile to /tmp/DS0flSbO2F/ea_profile.json
* 2024-02-09 03:09:45 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-10 03:09:35 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-10 03:09:35 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-10 03:09:35 (4416) [INFO] 
* 2024-02-10 03:09:35 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-10 03:09:35 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-10 03:09:35 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-10 03:09:35 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-10 03:09:35 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-10 03:09:35 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-10 03:09:35 (4446) [INFO] 
* 2024-02-10 03:09:35 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-10 03:09:35 (4416) [INFO] 
* 2024-02-10 03:09:52 (4429) [INFO] 
* 2024-02-10 03:09:52 (4429) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-10 03:09:53 (4446) [INFO] 
* 2024-02-10 03:09:53 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-10 03:09:53 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-10 03:10:13 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-10 03:10:13 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/XxS6ceUUXK/ea_profile.json
* 2024-02-10 03:10:14 (2436) [INFO] Backed up EA4 profile to /tmp/XxS6ceUUXK/ea_profile.json
* 2024-02-10 03:10:15 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-11 03:09:47 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-11 03:09:47 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-11 03:09:47 (4416) [INFO] 
* 2024-02-11 03:09:47 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-11 03:09:47 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-11 03:09:47 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-11 03:09:47 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-11 03:09:47 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-11 03:09:47 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-11 03:09:47 (4446) [INFO] 
* 2024-02-11 03:09:47 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-11 03:09:47 (4416) [INFO] 
* 2024-02-11 03:10:03 (4429) [INFO] 
* 2024-02-11 03:10:03 (4429) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-11 03:10:03 (4446) [INFO] 
* 2024-02-11 03:10:03 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-11 03:10:03 (162) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-11 03:10:23 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-11 03:10:23 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/brfo0cdrlx/ea_profile.json
* 2024-02-11 03:10:24 (2436) [INFO] Backed up EA4 profile to /tmp/brfo0cdrlx/ea_profile.json
* 2024-02-11 03:10:25 (270) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-12 03:08:46 (1844) [INFO] Checking if your system is up to date: 
* 2024-02-12 03:08:46 (4415) [INFO] Running: /usr/bin/yum clean all
* 2024-02-12 03:08:46 (4416) [INFO] 
* 2024-02-12 03:08:46 (4429) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-12 03:08:46 (4429) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-12 03:08:46 (4429) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-12 03:08:46 (4429) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-12 03:08:46 (4429) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-12 03:08:46 (4429) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-12 03:08:46 (4446) [INFO] 
* 2024-02-12 03:08:46 (4415) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-12 03:08:46 (4416) [INFO] 
* 2024-02-12 03:09:15 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]  One of the configured repositories failed (Unknown),
* 2024-02-12 03:09:16 (4429) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-12 03:09:16 (4429) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-12 03:09:16 (4429) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-12 03:09:16 (4429) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-12 03:09:16 (4429) [INFO]         packages for the previous distribution release still work).
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-12 03:09:16 (4429) [INFO]             yum --disablerepo=<repoid> ...
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-12 03:09:16 (4429) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-12 03:09:16 (4429) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]             yum-config-manager --disable <repoid>
* 2024-02-12 03:09:16 (4429) [INFO]         or
* 2024-02-12 03:09:16 (4429) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-12 03:09:16 (4429) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-12 03:09:16 (4429) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-12 03:09:16 (4429) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-12 03:09:16 (4429) [INFO]         compromise:
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-12 03:09:16 (4429) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO] updates: Check uncompressed DB failed
* 2024-02-12 03:09:16 (4446) [INFO] 
* 2024-02-12 03:09:16 (1851) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-12 03:09:16 (1865) [INFO] Checking /scripts/sysup
* 2024-02-12 03:09:16 (4415) [INFO] Running: /scripts/sysup
* 2024-02-12 03:09:16 (4416) [INFO] 
* 2024-02-12 03:09:16 (4429) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-12 03:09:16 (4429) [INFO]   All Needed Packages are already installed.
* 2024-02-12 03:09:16 (4446) [INFO] 
* 2024-02-12 03:09:47 (893) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-12 03:09:47 (2413) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/MB8_tL95MY/ea_profile.json
* 2024-02-12 03:09:48 (2436) [INFO] Backed up EA4 profile to /tmp/MB8_tL95MY/ea_profile.json
* 2024-02-12 03:09:50 (281) [INFO] There are no known blockers to start the elevation process.
You can consider running:
    /scripts/elevate-cpanel --start
* 2024-02-13 03:08:42 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-13 03:08:42 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-13 03:08:42 (4463) [INFO] 
* 2024-02-13 03:08:42 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-13 03:08:42 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-13 03:08:42 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-13 03:08:42 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-13 03:08:42 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-13 03:08:42 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-13 03:08:42 (4493) [INFO] 
* 2024-02-13 03:08:42 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-13 03:08:42 (4463) [INFO] 
* 2024-02-13 03:08:57 (4476) [INFO] 
* 2024-02-13 03:08:57 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-13 03:08:57 (4493) [INFO] 
* 2024-02-13 03:08:57 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-13 03:08:57 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-13 03:09:41 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-13 03:09:41 (1705) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2024-02-13 03:09:41 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-13 03:09:42 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-13 03:09:42 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/pQdk9zL8uH/ea_profile.json
* 2024-02-13 03:09:42 (2437) [INFO] Backed up EA4 profile to /tmp/pQdk9zL8uH/ea_profile.json
* 2024-02-13 03:09:44 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-14 03:08:45 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-14 03:08:45 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-14 03:08:45 (4463) [INFO] 
* 2024-02-14 03:08:45 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-14 03:08:45 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-14 03:08:45 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-14 03:08:45 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-14 03:08:45 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-14 03:08:45 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-14 03:08:45 (4493) [INFO] 
* 2024-02-14 03:08:45 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-14 03:08:45 (4463) [INFO] 
* 2024-02-14 03:09:02 (4476) [INFO] 
* 2024-02-14 03:09:02 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-14 03:09:03 (4493) [INFO] 
* 2024-02-14 03:09:03 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-14 03:09:03 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-14 03:09:35 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-14 03:09:35 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/d04c0KWHSv/ea_profile.json
* 2024-02-14 03:09:36 (2437) [INFO] Backed up EA4 profile to /tmp/d04c0KWHSv/ea_profile.json
* 2024-02-14 03:09:38 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-15 03:08:53 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-15 03:08:53 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-15 03:08:53 (4463) [INFO] 
* 2024-02-15 03:08:53 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-15 03:08:54 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-15 03:08:54 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-15 03:08:54 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-15 03:08:54 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-15 03:08:54 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-15 03:08:54 (4493) [INFO] 
* 2024-02-15 03:08:54 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-15 03:08:54 (4463) [INFO] 
* 2024-02-15 03:09:15 (4476) [INFO] 
* 2024-02-15 03:09:15 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-15 03:09:15 (4493) [INFO] 
* 2024-02-15 03:09:15 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-15 03:09:15 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-15 03:09:42 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-15 03:09:42 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/kKwWJv4m29/ea_profile.json
* 2024-02-15 03:09:43 (2437) [INFO] Backed up EA4 profile to /tmp/kKwWJv4m29/ea_profile.json
* 2024-02-15 03:09:45 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-16 03:08:51 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-16 03:08:51 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-16 03:08:51 (4463) [INFO] 
* 2024-02-16 03:08:51 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-16 03:08:51 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-16 03:08:51 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-16 03:08:51 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-16 03:08:51 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-16 03:08:51 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-16 03:08:51 (4493) [INFO] 
* 2024-02-16 03:08:51 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-16 03:08:51 (4463) [INFO] 
* 2024-02-16 03:09:13 (4476) [INFO] 
* 2024-02-16 03:09:13 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-16 03:09:13 (4493) [INFO] 
* 2024-02-16 03:09:13 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-16 03:09:13 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-16 03:09:42 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-16 03:09:42 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/rvhoVhFQun/ea_profile.json
* 2024-02-16 03:09:43 (2437) [INFO] Backed up EA4 profile to /tmp/rvhoVhFQun/ea_profile.json
* 2024-02-16 03:09:44 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-17 03:09:28 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-17 03:09:28 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-17 03:09:28 (4463) [INFO] 
* 2024-02-17 03:09:28 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-17 03:09:28 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-17 03:09:28 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-17 03:09:28 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-17 03:09:28 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-17 03:09:28 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-17 03:09:28 (4493) [INFO] 
* 2024-02-17 03:09:28 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-17 03:09:28 (4463) [INFO] 
* 2024-02-17 03:09:44 (4476) [INFO] 
* 2024-02-17 03:09:44 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-17 03:09:44 (4493) [INFO] 
* 2024-02-17 03:09:44 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-17 03:09:44 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-17 03:10:06 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-17 03:10:06 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/dvIhglQlii/ea_profile.json
* 2024-02-17 03:10:07 (2437) [INFO] Backed up EA4 profile to /tmp/dvIhglQlii/ea_profile.json
* 2024-02-17 03:10:09 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-18 03:10:26 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-18 03:10:26 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-18 03:10:26 (4463) [INFO] 
* 2024-02-18 03:10:26 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-18 03:10:26 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-18 03:10:26 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-18 03:10:26 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-18 03:10:26 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-18 03:10:26 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-18 03:10:26 (4493) [INFO] 
* 2024-02-18 03:10:26 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-18 03:10:26 (4463) [INFO] 
* 2024-02-18 03:10:41 (4476) [INFO] 
* 2024-02-18 03:10:41 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-18 03:10:41 (4493) [INFO] 
* 2024-02-18 03:10:41 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-18 03:10:41 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-18 03:10:58 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-18 03:10:58 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/7KQJzht7Xp/ea_profile.json
* 2024-02-18 03:10:58 (2437) [INFO] Backed up EA4 profile to /tmp/7KQJzht7Xp/ea_profile.json
* 2024-02-18 03:11:00 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-19 03:08:42 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-19 03:08:42 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-19 03:08:42 (4463) [INFO] 
* 2024-02-19 03:08:42 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-19 03:08:43 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-19 03:08:43 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-19 03:08:43 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-19 03:08:43 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-19 03:08:43 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-19 03:08:43 (4493) [INFO] 
* 2024-02-19 03:08:43 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-19 03:08:43 (4463) [INFO] 
* 2024-02-19 03:08:58 (4476) [INFO] 
* 2024-02-19 03:08:58 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-19 03:08:58 (4493) [INFO] 
* 2024-02-19 03:08:58 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-19 03:08:58 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-19 03:09:32 (1704) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-19 03:09:32 (1705) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2024-02-19 03:09:32 (163) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-19 03:09:32 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-19 03:09:32 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ZIVIPORXzY/ea_profile.json
* 2024-02-19 03:09:33 (2437) [INFO] Backed up EA4 profile to /tmp/ZIVIPORXzY/ea_profile.json
* 2024-02-19 03:09:34 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-20 03:09:02 (1845) [INFO] Checking if your system is up to date: 
* 2024-02-20 03:09:02 (4462) [INFO] Running: /usr/bin/yum clean all
* 2024-02-20 03:09:02 (4463) [INFO] 
* 2024-02-20 03:09:02 (4476) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-20 03:09:02 (4476) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-20 03:09:02 (4476) [INFO]               : extras imunify360 imunify360-rollout-1 imunify360-rollout-2
* 2024-02-20 03:09:02 (4476) [INFO]               : imunify360-rollout-3 imunify360-rollout-4 imunify360-rollout-5
* 2024-02-20 03:09:02 (4476) [INFO]               : imunify360-rollout-6 imunify360-rollout-7 imunify360-rollout-8
* 2024-02-20 03:09:02 (4476) [INFO]               : updates wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-02-20 03:09:02 (4493) [INFO] 
* 2024-02-20 03:09:02 (4462) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-20 03:09:02 (4463) [INFO] 
* 2024-02-20 03:09:27 (4476) [INFO] 
* 2024-02-20 03:09:27 (4476) [INFO] kernel.x86_64                   3.10.0-1160.108.1.el7                    updates
* 2024-02-20 03:09:27 (4493) [INFO] 
* 2024-02-20 03:09:27 (1852) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-20 03:09:27 (163) [WARN] *** Elevation Blocker detected: ***
System is not up to date
* 2024-02-20 03:09:47 (894) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-20 03:09:47 (2414) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=AlmaLinux_8 --output=/tmp/ciUlluUJmf/ea_profile.json
* 2024-02-20 03:09:48 (2437) [INFO] Backed up EA4 profile to /tmp/ciUlluUJmf/ea_profile.json
* 2024-02-20 03:09:49 (271) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-21 03:08:52 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-21 03:08:52 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-21 03:08:52 (4911) [INFO] 
* 2024-02-21 03:08:53 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-21 03:08:53 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-21 03:08:53 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-21 03:08:53 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-21 03:08:53 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-21 03:08:53 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-21 03:08:53 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-21 03:08:53 (4941) [INFO] 
* 2024-02-21 03:08:53 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-21 03:08:53 (4911) [INFO] 
* 2024-02-21 03:09:10 (4941) [INFO] 
* 2024-02-21 03:09:10 (1803) [INFO] Checking /scripts/sysup
* 2024-02-21 03:09:10 (4910) [INFO] Running: /scripts/sysup
* 2024-02-21 03:09:10 (4911) [INFO] 
* 2024-02-21 03:09:10 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-21 03:09:11 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-21 03:09:11 (4941) [INFO] 
* 2024-02-21 03:09:12 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-21 03:09:33 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-21 03:09:33 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BxIMFjHLSp/ea_profile.json
* 2024-02-21 03:09:34 (2386) [INFO] Backed up EA4 profile to /tmp/BxIMFjHLSp/ea_profile.json
* 2024-02-21 03:09:35 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-22 03:09:11 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-22 03:09:11 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-22 03:09:11 (4911) [INFO] 
* 2024-02-22 03:09:11 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-22 03:09:11 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-22 03:09:11 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-22 03:09:11 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-22 03:09:11 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-22 03:09:11 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-22 03:09:11 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-22 03:09:11 (4941) [INFO] 
* 2024-02-22 03:09:11 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-22 03:09:11 (4911) [INFO] 
* 2024-02-22 03:09:29 (4941) [INFO] 
* 2024-02-22 03:09:29 (1803) [INFO] Checking /scripts/sysup
* 2024-02-22 03:09:29 (4910) [INFO] Running: /scripts/sysup
* 2024-02-22 03:09:29 (4911) [INFO] 
* 2024-02-22 03:09:29 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-22 03:09:30 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-22 03:09:30 (4941) [INFO] 
* 2024-02-22 03:09:31 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-22 03:09:51 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-22 03:09:51 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n9nujVx1R6/ea_profile.json
* 2024-02-22 03:09:51 (2386) [INFO] Backed up EA4 profile to /tmp/n9nujVx1R6/ea_profile.json
* 2024-02-22 03:09:53 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-23 03:08:56 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-23 03:08:56 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-23 03:08:56 (4911) [INFO] 
* 2024-02-23 03:08:56 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-23 03:08:56 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-23 03:08:56 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-23 03:08:56 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-23 03:08:56 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-23 03:08:56 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-23 03:08:56 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-23 03:08:56 (4941) [INFO] 
* 2024-02-23 03:08:56 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-23 03:08:56 (4911) [INFO] 
* 2024-02-23 03:09:03 (4924) [INFO] http://ftp.plusline.net/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:03 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:04 (4924) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-02-23 03:09:04 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:06 (4924) [INFO] https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.14/wp-toolkit/repodata/8d8331406e621d2fc1962b669b68b8b30c27e130a4ada0f3cd5f17987c5663ae-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:06 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:06 (4924) [INFO] http://ftp.wrz.de/pub/CentOS/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:06 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:06 (4924) [INFO] http://centos.mirrors.psw.services/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:06 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:07 (4924) [INFO] http://centos.schlundtech.de/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:07 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:07 (4924) [INFO] http://mirror.checkdomain.de/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:07 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:07 (4924) [INFO] http://centos.intergenia.de/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:07 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:07 (4924) [INFO] http://mirror.junda.nl/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:07 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:07 (4924) [INFO] http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:07 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:07 (4924) [INFO] http://centos.bio.lmu.de/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:07 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:08 (4924) [INFO] http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
* 2024-02-23 03:09:08 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:19 (4924) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2024-02-23 03:09:19 (4924) [INFO] Trying other mirror.
* 2024-02-23 03:09:34 (4941) [INFO] 
* 2024-02-23 03:09:34 (1803) [INFO] Checking /scripts/sysup
* 2024-02-23 03:09:34 (4910) [INFO] Running: /scripts/sysup
* 2024-02-23 03:09:34 (4911) [INFO] 
* 2024-02-23 03:09:34 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-23 03:09:35 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-23 03:09:35 (4941) [INFO] 
* 2024-02-23 03:09:36 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-23 03:10:01 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-23 03:10:01 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xOvCPBBhBs/ea_profile.json
* 2024-02-23 03:10:02 (2386) [INFO] Backed up EA4 profile to /tmp/xOvCPBBhBs/ea_profile.json
* 2024-02-23 03:10:04 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-24 03:09:32 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-24 03:09:32 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-24 03:09:32 (4911) [INFO] 
* 2024-02-24 03:09:33 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-24 03:09:33 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-24 03:09:33 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-24 03:09:33 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-24 03:09:33 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-24 03:09:33 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-24 03:09:33 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-24 03:09:33 (4941) [INFO] 
* 2024-02-24 03:09:33 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-24 03:09:33 (4911) [INFO] 
* 2024-02-24 03:09:49 (4941) [INFO] 
* 2024-02-24 03:09:49 (1803) [INFO] Checking /scripts/sysup
* 2024-02-24 03:09:49 (4910) [INFO] Running: /scripts/sysup
* 2024-02-24 03:09:49 (4911) [INFO] 
* 2024-02-24 03:09:50 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-24 03:09:50 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-24 03:09:50 (4941) [INFO] 
* 2024-02-24 03:09:51 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-24 03:10:11 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-24 03:10:11 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g7KJYLtTtK/ea_profile.json
* 2024-02-24 03:10:12 (2386) [INFO] Backed up EA4 profile to /tmp/g7KJYLtTtK/ea_profile.json
* 2024-02-24 03:10:14 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-25 03:09:19 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-25 03:09:19 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-25 03:09:19 (4911) [INFO] 
* 2024-02-25 03:09:19 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-25 03:09:19 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-25 03:09:19 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-25 03:09:19 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-25 03:09:19 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-25 03:09:19 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-25 03:09:19 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-25 03:09:19 (4941) [INFO] 
* 2024-02-25 03:09:19 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-25 03:09:19 (4911) [INFO] 
* 2024-02-25 03:09:36 (4941) [INFO] 
* 2024-02-25 03:09:36 (1803) [INFO] Checking /scripts/sysup
* 2024-02-25 03:09:36 (4910) [INFO] Running: /scripts/sysup
* 2024-02-25 03:09:36 (4911) [INFO] 
* 2024-02-25 03:09:36 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-25 03:09:36 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-25 03:09:37 (4941) [INFO] 
* 2024-02-25 03:09:38 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-25 03:09:55 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-25 03:09:55 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DMqzzabBBw/ea_profile.json
* 2024-02-25 03:09:56 (2386) [INFO] Backed up EA4 profile to /tmp/DMqzzabBBw/ea_profile.json
* 2024-02-25 03:09:58 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-26 03:08:39 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-26 03:08:39 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-26 03:08:39 (4911) [INFO] 
* 2024-02-26 03:08:40 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-26 03:08:40 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-26 03:08:40 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-26 03:08:40 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-26 03:08:40 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-26 03:08:40 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-26 03:08:40 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-26 03:08:40 (4941) [INFO] 
* 2024-02-26 03:08:40 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-26 03:08:40 (4911) [INFO] 
* 2024-02-26 03:08:55 (4941) [INFO] 
* 2024-02-26 03:08:55 (1803) [INFO] Checking /scripts/sysup
* 2024-02-26 03:08:55 (4910) [INFO] Running: /scripts/sysup
* 2024-02-26 03:08:55 (4911) [INFO] 
* 2024-02-26 03:08:55 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-26 03:08:56 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-26 03:08:56 (4941) [INFO] 
* 2024-02-26 03:08:57 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-26 03:09:14 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-26 03:09:14 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oO3jU7TUzA/ea_profile.json
* 2024-02-26 03:09:15 (2386) [INFO] Backed up EA4 profile to /tmp/oO3jU7TUzA/ea_profile.json
* 2024-02-26 03:09:16 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-27 03:08:50 (1782) [INFO] Checking if your system is up to date: 
* 2024-02-27 03:08:50 (4910) [INFO] Running: /usr/bin/yum clean all
* 2024-02-27 03:08:50 (4911) [INFO] 
* 2024-02-27 03:08:50 (4924) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-27 03:08:50 (4924) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-27 03:08:50 (4924) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-27 03:08:50 (4924) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-27 03:08:50 (4924) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-27 03:08:50 (4924) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-27 03:08:50 (4924) [INFO]               : wp-toolkit-thirdparties
* 2024-02-27 03:08:50 (4941) [INFO] 
* 2024-02-27 03:08:50 (4910) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-27 03:08:50 (4911) [INFO] 
* 2024-02-27 03:09:10 (4941) [INFO] 
* 2024-02-27 03:09:10 (1803) [INFO] Checking /scripts/sysup
* 2024-02-27 03:09:10 (4910) [INFO] Running: /scripts/sysup
* 2024-02-27 03:09:10 (4911) [INFO] 
* 2024-02-27 03:09:10 (4924) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-27 03:09:11 (4924) [INFO]   All Needed Packages are already installed.
* 2024-02-27 03:09:11 (4941) [INFO] 
* 2024-02-27 03:09:12 (1701) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-27 03:09:35 (912) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-27 03:09:35 (2363) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hu6BDNKfXh/ea_profile.json
* 2024-02-27 03:09:36 (2386) [INFO] Backed up EA4 profile to /tmp/hu6BDNKfXh/ea_profile.json
* 2024-02-27 03:09:37 (278) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-28 03:08:49 (1828) [INFO] Checking if your system is up to date: 
* 2024-02-28 03:08:49 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-02-28 03:08:49 (5105) [INFO] 
* 2024-02-28 03:08:49 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-28 03:08:49 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-28 03:08:49 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-28 03:08:49 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-28 03:08:49 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-28 03:08:49 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-28 03:08:49 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-02-28 03:08:49 (5135) [INFO] 
* 2024-02-28 03:08:49 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-28 03:08:49 (5105) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]  One of the configured repositories failed (Unknown),
* 2024-02-28 03:09:12 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-28 03:09:12 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-28 03:09:12 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-28 03:09:12 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-28 03:09:12 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-28 03:09:12 (5118) [INFO]             yum --disablerepo=<repoid> ...
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-28 03:09:12 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-28 03:09:12 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]             yum-config-manager --disable <repoid>
* 2024-02-28 03:09:12 (5118) [INFO]         or
* 2024-02-28 03:09:12 (5118) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-28 03:09:12 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-28 03:09:12 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-28 03:09:12 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-28 03:09:12 (5118) [INFO]         compromise:
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-02-28 03:09:12 (5118) [INFO] 
* 2024-02-28 03:09:12 (5118) [INFO] updates: Check uncompressed DB failed
* 2024-02-28 03:09:12 (5135) [INFO] 
* 2024-02-28 03:09:12 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-28 03:09:12 (1849) [INFO] Checking /scripts/sysup
* 2024-02-28 03:09:12 (5104) [INFO] Running: /scripts/sysup
* 2024-02-28 03:09:12 (5105) [INFO] 
* 2024-02-28 03:09:13 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-28 03:09:13 (5118) [INFO]   All Needed Packages are already installed.
* 2024-02-28 03:09:13 (5135) [INFO] 
* 2024-02-28 03:09:14 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-28 03:09:39 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-28 03:09:39 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_1WBqs0_dM/ea_profile.json
* 2024-02-28 03:09:40 (2488) [INFO] Backed up EA4 profile to /tmp/_1WBqs0_dM/ea_profile.json
* 2024-02-28 03:09:41 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-02-29 03:09:07 (1828) [INFO] Checking if your system is up to date: 
* 2024-02-29 03:09:07 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-02-29 03:09:07 (5105) [INFO] 
* 2024-02-29 03:09:08 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-02-29 03:09:08 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-02-29 03:09:08 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-02-29 03:09:08 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-02-29 03:09:08 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-02-29 03:09:08 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-02-29 03:09:08 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-02-29 03:09:08 (5135) [INFO] 
* 2024-02-29 03:09:08 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-02-29 03:09:08 (5105) [INFO] 
* 2024-02-29 03:09:23 (5118) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-02-29 03:09:23 (5118) [INFO] Trying other mirror.
* 2024-02-29 03:09:40 (5118) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-02-29 03:09:40 (5118) [INFO] Trying other mirror.
* 2024-02-29 03:09:56 (5118) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-02-29 03:09:56 (5118) [INFO] Trying other mirror.
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]  One of the configured repositories failed (EL-7 - Imunify360),
* 2024-02-29 03:09:56 (5118) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-02-29 03:09:56 (5118) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-02-29 03:09:56 (5118) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-02-29 03:09:56 (5118) [INFO]         distribution release than is supported by the repository (and the
* 2024-02-29 03:09:56 (5118) [INFO]         packages for the previous distribution release still work).
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-02-29 03:09:56 (5118) [INFO]             yum --disablerepo=imunify360 ...
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-02-29 03:09:56 (5118) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-02-29 03:09:56 (5118) [INFO]         again or use --enablerepo for temporary usage:
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]             yum-config-manager --disable imunify360
* 2024-02-29 03:09:56 (5118) [INFO]         or
* 2024-02-29 03:09:56 (5118) [INFO]             subscription-manager repos --disable=imunify360
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-02-29 03:09:56 (5118) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-02-29 03:09:56 (5118) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-02-29 03:09:56 (5118) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-02-29 03:09:56 (5118) [INFO]         compromise:
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO]             yum-config-manager --save --setopt=imunify360.skip_if_unavailable=true
* 2024-02-29 03:09:56 (5118) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO] failure: repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2 from imunify360: [Errno 256] No more mirrors to try.
* 2024-02-29 03:09:56 (5118) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-02-29 03:09:56 (5135) [INFO] 
* 2024-02-29 03:09:56 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-02-29 03:09:56 (1849) [INFO] Checking /scripts/sysup
* 2024-02-29 03:09:56 (5104) [INFO] Running: /scripts/sysup
* 2024-02-29 03:09:56 (5105) [INFO] 
* 2024-02-29 03:09:56 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-02-29 03:09:57 (5118) [INFO]   All Needed Packages are already installed.
* 2024-02-29 03:09:57 (5135) [INFO] 
* 2024-02-29 03:10:01 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-02-29 03:10:45 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-02-29 03:10:45 (1688) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2024-02-29 03:10:45 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-02-29 03:10:45 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-02-29 03:10:45 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gTztCsewLA/ea_profile.json
* 2024-02-29 03:10:50 (2488) [INFO] Backed up EA4 profile to /tmp/gTztCsewLA/ea_profile.json
* 2024-02-29 03:10:51 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-01 03:09:01 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-01 03:09:01 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-01 03:09:01 (5105) [INFO] 
* 2024-03-01 03:09:01 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-01 03:09:02 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-01 03:09:02 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-01 03:09:02 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-01 03:09:02 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-01 03:09:02 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-01 03:09:02 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-03-01 03:09:02 (5135) [INFO] 
* 2024-03-01 03:09:02 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-01 03:09:02 (5105) [INFO] 
* 2024-03-01 03:09:15 (5118) [INFO] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/5c160bfb7182d8cbbc6fc730840df7cc05b8e61567f5b55c16fa78284e54fa1f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
* 2024-03-01 03:09:15 (5118) [INFO] Trying other mirror.
* 2024-03-01 03:09:16 (5118) [INFO] Traceback (most recent call last):
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/bin/yum", line 29, in <module>
* 2024-03-01 03:09:16 (5118) [INFO]     yummain.user_main(sys.argv[1:], exit_code=True)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/share/yum-cli/yummain.py", line 375, in user_main
* 2024-03-01 03:09:16 (5118) [INFO]     errcode = main(args)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/share/yum-cli/yummain.py", line 184, in main
* 2024-03-01 03:09:16 (5118) [INFO]     result, resultmsgs = base.doCommands()
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/share/yum-cli/cli.py", line 585, in doCommands
* 2024-03-01 03:09:16 (5118) [INFO]     return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/share/yum-cli/yumcommands.py", line 1627, in doCommand
* 2024-03-01 03:09:16 (5118) [INFO]     ypl = base.returnPkgLists(extcmds, repoid=repoid)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/share/yum-cli/cli.py", line 1444, in returnPkgLists
* 2024-03-01 03:09:16 (5118) [INFO]     ignore_case=True, repoid=repoid)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 3015, in doPackageLists
* 2024-03-01 03:09:16 (5118) [INFO]     for (n,a,e,v,r) in self.up.getUpdatesList():
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1094, in <lambda>
* 2024-03-01 03:09:16 (5118) [INFO]     up = property(fget=lambda self: self._getUpdates(),
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 838, in _getUpdates
* 2024-03-01 03:09:16 (5118) [INFO]     self._up = rpmUtils.updates.Updates(self.rpmdb.simplePkgList(), self.pkgSack.simplePkgList())
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1075, in <lambda>
* 2024-03-01 03:09:16 (5118) [INFO]     pkgSack = property(fget=lambda self: self._getSacks(),
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 778, in _getSacks
* 2024-03-01 03:09:16 (5118) [INFO]     self.repos.populateSack(which=repos)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
* 2024-03-01 03:09:16 (5118) [INFO]     sack._retrieve_async(repo, data)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
* 2024-03-01 03:09:16 (5118) [INFO]     if not self._check_uncompressed_db_gen(repo, mydbtype):
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
* 2024-03-01 03:09:16 (5118) [INFO]     cached=repo.cache)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
* 2024-03-01 03:09:16 (5118) [INFO]     return decompress(filename, dest=dest, check_timestamps=True)
* 2024-03-01 03:09:16 (5118) [INFO]   File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
* 2024-03-01 03:09:16 (5118) [INFO]     os.utime(out, (fi.st_mtime, fi.st_mtime))
* 2024-03-01 03:09:16 (5118) [INFO] OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2024-03-01 03:09:16 (5135) [INFO] 
* 2024-03-01 03:09:16 (1835) [WARN] Your system is not up to date please run: /usr/bin/yum update
* 2024-03-01 03:09:16 (1849) [INFO] Checking /scripts/sysup
* 2024-03-01 03:09:16 (5104) [INFO] Running: /scripts/sysup
* 2024-03-01 03:09:16 (5105) [INFO] 
* 2024-03-01 03:09:17 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-01 03:09:17 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-01 03:09:17 (5135) [INFO] 
* 2024-03-01 03:09:19 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-01 03:09:38 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-01 03:09:38 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DEnZD0yMcH/ea_profile.json
* 2024-03-01 03:09:39 (2488) [INFO] Backed up EA4 profile to /tmp/DEnZD0yMcH/ea_profile.json
* 2024-03-01 03:09:40 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-02 03:09:24 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-02 03:09:24 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-02 03:09:24 (5105) [INFO] 
* 2024-03-02 03:09:25 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-02 03:09:25 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-02 03:09:25 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-02 03:09:25 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-02 03:09:25 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-02 03:09:25 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-02 03:09:25 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-03-02 03:09:25 (5135) [INFO] 
* 2024-03-02 03:09:25 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-02 03:09:25 (5105) [INFO] 
* 2024-03-02 03:09:42 (5135) [INFO] 
* 2024-03-02 03:09:42 (1849) [INFO] Checking /scripts/sysup
* 2024-03-02 03:09:42 (5104) [INFO] Running: /scripts/sysup
* 2024-03-02 03:09:42 (5105) [INFO] 
* 2024-03-02 03:09:42 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-02 03:09:42 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-02 03:09:42 (5135) [INFO] 
* 2024-03-02 03:09:44 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-02 03:10:03 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-02 03:10:03 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_yMSRuXpzi/ea_profile.json
* 2024-03-02 03:10:04 (2488) [INFO] Backed up EA4 profile to /tmp/_yMSRuXpzi/ea_profile.json
* 2024-03-02 03:10:06 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-03 03:09:19 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-03 03:09:19 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-03 03:09:19 (5105) [INFO] 
* 2024-03-03 03:09:19 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-03 03:09:20 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-03 03:09:20 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-03 03:09:20 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-03 03:09:20 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-03 03:09:20 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-03 03:09:20 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-03-03 03:09:20 (5135) [INFO] 
* 2024-03-03 03:09:20 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-03 03:09:20 (5105) [INFO] 
* 2024-03-03 03:09:37 (5135) [INFO] 
* 2024-03-03 03:09:37 (1849) [INFO] Checking /scripts/sysup
* 2024-03-03 03:09:37 (5104) [INFO] Running: /scripts/sysup
* 2024-03-03 03:09:37 (5105) [INFO] 
* 2024-03-03 03:09:37 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-03 03:09:38 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-03 03:09:38 (5135) [INFO] 
* 2024-03-03 03:09:39 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-03 03:09:59 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-03 03:09:59 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vErRIEctvM/ea_profile.json
* 2024-03-03 03:10:00 (2488) [INFO] Backed up EA4 profile to /tmp/vErRIEctvM/ea_profile.json
* 2024-03-03 03:10:01 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-04 03:08:40 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-04 03:08:40 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-04 03:08:40 (5105) [INFO] 
* 2024-03-04 03:08:40 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-04 03:08:40 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-04 03:08:40 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-04 03:08:40 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-04 03:08:40 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-04 03:08:40 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-04 03:08:40 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-03-04 03:08:40 (5135) [INFO] 
* 2024-03-04 03:08:40 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-04 03:08:40 (5105) [INFO] 
* 2024-03-04 03:08:55 (5135) [INFO] 
* 2024-03-04 03:08:55 (1849) [INFO] Checking /scripts/sysup
* 2024-03-04 03:08:55 (5104) [INFO] Running: /scripts/sysup
* 2024-03-04 03:08:55 (5105) [INFO] 
* 2024-03-04 03:08:55 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-04 03:08:56 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-04 03:08:56 (5135) [INFO] 
* 2024-03-04 03:08:57 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-04 03:09:30 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-04 03:09:30 (1688) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/84823fd3ece1cbb9caf902f18fea26f8c3e0e36fef5a2138e4d1ebdcfcd6551b-other.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
* 2024-03-04 03:09:30 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-04 03:09:30 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-04 03:09:30 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CidoBQhhmk/ea_profile.json
* 2024-03-04 03:09:31 (2488) [INFO] Backed up EA4 profile to /tmp/CidoBQhhmk/ea_profile.json
* 2024-03-04 03:09:32 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-05 03:08:41 (1828) [INFO] Checking if your system is up to date: 
* 2024-03-05 03:08:41 (5104) [INFO] Running: /usr/bin/yum clean all
* 2024-03-05 03:08:41 (5105) [INFO] 
* 2024-03-05 03:08:41 (5118) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-05 03:08:41 (5118) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-05 03:08:41 (5118) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-05 03:08:41 (5118) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-05 03:08:41 (5118) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-05 03:08:41 (5118) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-05 03:08:41 (5118) [INFO]               : wp-toolkit-thirdparties
* 2024-03-05 03:08:41 (5135) [INFO] 
* 2024-03-05 03:08:41 (5104) [INFO] Running: /usr/bin/yum check-update -q
* 2024-03-05 03:08:41 (5105) [INFO] 
* 2024-03-05 03:08:58 (5135) [INFO] 
* 2024-03-05 03:08:58 (1849) [INFO] Checking /scripts/sysup
* 2024-03-05 03:08:58 (5104) [INFO] Running: /scripts/sysup
* 2024-03-05 03:08:58 (5105) [INFO] 
* 2024-03-05 03:08:59 (5118) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-05 03:08:59 (5118) [INFO]   All Needed Packages are already installed.
* 2024-03-05 03:08:59 (5135) [INFO] 
* 2024-03-05 03:09:00 (1747) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-05 03:10:02 (1687) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-05 03:10:02 (1688) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
* 2024-03-05 03:10:02 (173) [WARN] *** Elevation Blocker detected: ***
yum is not stable
* 2024-03-05 03:10:02 (958) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-05 03:10:02 (2465) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7wyJhI63Xh/ea_profile.json
* 2024-03-05 03:10:03 (2488) [INFO] Backed up EA4 profile to /tmp/7wyJhI63Xh/ea_profile.json
* 2024-03-05 03:10:04 (283) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-06 03:08:48 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-06 03:08:48 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-06 03:08:48 (5196) [INFO] 
* 2024-03-06 03:08:48 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-06 03:08:48 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-06 03:08:48 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-06 03:08:48 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-06 03:08:48 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-06 03:08:48 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-06 03:08:48 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-06 03:08:48 (5226) [INFO] 
* 2024-03-06 03:08:48 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-06 03:08:48 (5196) [INFO] 
* 2024-03-06 03:09:17 (5209) [INFO] 
* 2024-03-06 03:09:17 (5226) [INFO] 
* 2024-03-06 03:09:17 (1940) [INFO] Checking /scripts/sysup
* 2024-03-06 03:09:17 (5195) [INFO] Running: /scripts/sysup
* 2024-03-06 03:09:17 (5196) [INFO] 
* 2024-03-06 03:09:18 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-06 03:09:18 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-06 03:09:18 (5226) [INFO] 
* 2024-03-06 03:09:19 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-06 03:09:51 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-06 03:09:51 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/gNmFIZiKUM/ea_profile.json
* 2024-03-06 03:09:51 (2579) [INFO] Backed up EA4 profile to /tmp/gNmFIZiKUM/ea_profile.json
* 2024-03-06 03:09:53 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-07 03:08:58 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-07 03:08:58 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-07 03:08:58 (5196) [INFO] 
* 2024-03-07 03:08:59 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-07 03:08:59 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-07 03:08:59 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-07 03:08:59 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-07 03:08:59 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-07 03:08:59 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-07 03:08:59 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-07 03:08:59 (5226) [INFO] 
* 2024-03-07 03:08:59 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-07 03:08:59 (5196) [INFO] 
* 2024-03-07 03:09:11 (5209) [INFO] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2024-03-07 03:09:11 (5209) [INFO] Trying other mirror.
* 2024-03-07 03:09:22 (5209) [INFO] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2024-03-07 03:09:22 (5209) [INFO] Trying other mirror.
* 2024-03-07 03:09:22 (5209) [INFO] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2024-03-07 03:09:22 (5209) [INFO] Trying other mirror.
* 2024-03-07 03:09:22 (5209) [INFO] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
* 2024-03-07 03:09:22 (5209) [INFO] Trying other mirror.
* 2024-03-07 03:09:35 (5209) [INFO] 
* 2024-03-07 03:09:35 (5226) [INFO] 
* 2024-03-07 03:09:35 (1940) [INFO] Checking /scripts/sysup
* 2024-03-07 03:09:35 (5195) [INFO] Running: /scripts/sysup
* 2024-03-07 03:09:35 (5196) [INFO] 
* 2024-03-07 03:09:35 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-07 03:09:36 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-07 03:09:36 (5226) [INFO] 
* 2024-03-07 03:09:37 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-07 03:10:05 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-07 03:10:05 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DmyCOmZE7V/ea_profile.json
* 2024-03-07 03:10:05 (2579) [INFO] Backed up EA4 profile to /tmp/DmyCOmZE7V/ea_profile.json
* 2024-03-07 03:10:06 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-08 03:09:05 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-08 03:09:05 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-08 03:09:05 (5196) [INFO] 
* 2024-03-08 03:09:05 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-08 03:09:05 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-08 03:09:05 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-08 03:09:05 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-08 03:09:05 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-08 03:09:05 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-08 03:09:05 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-08 03:09:05 (5226) [INFO] 
* 2024-03-08 03:09:05 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-08 03:09:05 (5196) [INFO] 
* 2024-03-08 03:09:26 (5209) [INFO] 
* 2024-03-08 03:09:26 (5226) [INFO] 
* 2024-03-08 03:09:26 (1940) [INFO] Checking /scripts/sysup
* 2024-03-08 03:09:26 (5195) [INFO] Running: /scripts/sysup
* 2024-03-08 03:09:26 (5196) [INFO] 
* 2024-03-08 03:09:26 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-08 03:09:27 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-08 03:09:27 (5226) [INFO] 
* 2024-03-08 03:09:28 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-08 03:09:46 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-08 03:09:46 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/s8X4nnE3g7/ea_profile.json
* 2024-03-08 03:09:47 (2579) [INFO] Backed up EA4 profile to /tmp/s8X4nnE3g7/ea_profile.json
* 2024-03-08 03:09:48 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-09 03:09:28 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-09 03:09:28 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-09 03:09:28 (5196) [INFO] 
* 2024-03-09 03:09:28 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-09 03:09:28 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-09 03:09:28 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-09 03:09:28 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-09 03:09:28 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-09 03:09:28 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-09 03:09:28 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-09 03:09:28 (5226) [INFO] 
* 2024-03-09 03:09:28 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-09 03:09:28 (5196) [INFO] 
* 2024-03-09 03:09:50 (5209) [INFO] 
* 2024-03-09 03:09:50 (5226) [INFO] 
* 2024-03-09 03:09:50 (1940) [INFO] Checking /scripts/sysup
* 2024-03-09 03:09:50 (5195) [INFO] Running: /scripts/sysup
* 2024-03-09 03:09:50 (5196) [INFO] 
* 2024-03-09 03:09:51 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-09 03:09:51 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-09 03:09:51 (5226) [INFO] 
* 2024-03-09 03:09:53 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-09 03:10:15 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-09 03:10:15 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/j0059vEDUj/ea_profile.json
* 2024-03-09 03:10:16 (2579) [INFO] Backed up EA4 profile to /tmp/j0059vEDUj/ea_profile.json
* 2024-03-09 03:10:18 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-10 03:09:26 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-10 03:09:26 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-10 03:09:26 (5196) [INFO] 
* 2024-03-10 03:09:26 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-10 03:09:26 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-10 03:09:26 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-10 03:09:26 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-10 03:09:26 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-10 03:09:26 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-10 03:09:26 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-10 03:09:26 (5226) [INFO] 
* 2024-03-10 03:09:26 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-10 03:09:26 (5196) [INFO] 
* 2024-03-10 03:09:45 (5209) [INFO] 
* 2024-03-10 03:09:45 (5226) [INFO] 
* 2024-03-10 03:09:45 (1940) [INFO] Checking /scripts/sysup
* 2024-03-10 03:09:45 (5195) [INFO] Running: /scripts/sysup
* 2024-03-10 03:09:45 (5196) [INFO] 
* 2024-03-10 03:09:45 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-10 03:09:46 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-10 03:09:46 (5226) [INFO] 
* 2024-03-10 03:09:48 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-10 03:10:11 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-10 03:10:11 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_E_vVj7XdJ/ea_profile.json
* 2024-03-10 03:10:12 (2579) [INFO] Backed up EA4 profile to /tmp/_E_vVj7XdJ/ea_profile.json
* 2024-03-10 03:10:13 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-11 03:08:46 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-11 03:08:46 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-11 03:08:46 (5196) [INFO] 
* 2024-03-11 03:08:46 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-11 03:08:46 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-11 03:08:46 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-11 03:08:46 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-11 03:08:46 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-11 03:08:46 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-11 03:08:46 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-11 03:08:46 (5226) [INFO] 
* 2024-03-11 03:08:46 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-11 03:08:46 (5196) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]  One of the configured repositories failed (Unknown),
* 2024-03-11 03:09:15 (5209) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-03-11 03:09:15 (5209) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-03-11 03:09:15 (5209) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-03-11 03:09:15 (5209) [INFO]         distribution release than is supported by the repository (and the
* 2024-03-11 03:09:15 (5209) [INFO]         packages for the previous distribution release still work).
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-03-11 03:09:15 (5209) [INFO]             yum --disablerepo=<repoid> ...
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-03-11 03:09:15 (5209) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-03-11 03:09:15 (5209) [INFO]         again or use --enablerepo for temporary usage:
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]             yum-config-manager --disable <repoid>
* 2024-03-11 03:09:15 (5209) [INFO]         or
* 2024-03-11 03:09:15 (5209) [INFO]             subscription-manager repos --disable=<repoid>
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-03-11 03:09:15 (5209) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-03-11 03:09:15 (5209) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-03-11 03:09:15 (5209) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-03-11 03:09:15 (5209) [INFO]         compromise:
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO]             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5209) [INFO] updates: Check uncompressed DB failed
* 2024-03-11 03:09:15 (5209) [INFO] 
* 2024-03-11 03:09:15 (5226) [INFO] 
* 2024-03-11 03:09:15 (1940) [INFO] Checking /scripts/sysup
* 2024-03-11 03:09:15 (5195) [INFO] Running: /scripts/sysup
* 2024-03-11 03:09:15 (5196) [INFO] 
* 2024-03-11 03:09:16 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-11 03:09:16 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-11 03:09:16 (5226) [INFO] 
* 2024-03-11 03:09:18 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-11 03:09:52 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-11 03:09:52 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ptimLbgVnU/ea_profile.json
* 2024-03-11 03:09:53 (2579) [INFO] Backed up EA4 profile to /tmp/ptimLbgVnU/ea_profile.json
* 2024-03-11 03:09:54 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-12 03:08:44 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-12 03:08:44 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-12 03:08:44 (5196) [INFO] 
* 2024-03-12 03:08:44 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-12 03:08:44 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-12 03:08:44 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-12 03:08:44 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-12 03:08:44 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-12 03:08:44 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-12 03:08:44 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-12 03:08:44 (5226) [INFO] 
* 2024-03-12 03:08:44 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-12 03:08:44 (5196) [INFO] 
* 2024-03-12 03:09:03 (5209) [INFO] 
* 2024-03-12 03:09:03 (5226) [INFO] 
* 2024-03-12 03:09:03 (1940) [INFO] Checking /scripts/sysup
* 2024-03-12 03:09:03 (5195) [INFO] Running: /scripts/sysup
* 2024-03-12 03:09:03 (5196) [INFO] 
* 2024-03-12 03:09:03 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-12 03:09:04 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-12 03:09:04 (5226) [INFO] 
* 2024-03-12 03:09:06 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-12 03:09:33 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-12 03:09:33 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KFgXik8Sgh/ea_profile.json
* 2024-03-12 03:09:34 (2579) [INFO] Backed up EA4 profile to /tmp/KFgXik8Sgh/ea_profile.json
* 2024-03-12 03:09:36 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-13 03:08:41 (1896) [INFO] Checking if your system is up to date: 
* 2024-03-13 03:08:41 (5195) [INFO] Running: /usr/bin/yum clean all
* 2024-03-13 03:08:41 (5196) [INFO] 
* 2024-03-13 03:08:41 (5209) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-03-13 03:08:41 (5209) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-03-13 03:08:41 (5209) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-03-13 03:08:41 (5209) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-03-13 03:08:41 (5209) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-03-13 03:08:41 (5209) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-03-13 03:08:41 (5209) [INFO]               : wp-toolkit-thirdparties
* 2024-03-13 03:08:41 (5226) [INFO] 
* 2024-03-13 03:08:41 (5195) [INFO] Running: /usr/bin/yum check-update -q | xargs -n3
* 2024-03-13 03:08:41 (5196) [INFO] 
* 2024-03-13 03:08:59 (5209) [INFO] 
* 2024-03-13 03:08:59 (5226) [INFO] 
* 2024-03-13 03:08:59 (1940) [INFO] Checking /scripts/sysup
* 2024-03-13 03:08:59 (5195) [INFO] Running: /scripts/sysup
* 2024-03-13 03:08:59 (5196) [INFO] 
* 2024-03-13 03:09:00 (5209) [INFO] checkyum version 22.3  (excludes: bind-chroot)
* 2024-03-13 03:09:00 (5209) [INFO]   All Needed Packages are already installed.
* 2024-03-13 03:09:00 (5226) [INFO] 
* 2024-03-13 03:09:02 (1796) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-13 03:09:37 (975) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-13 03:09:37 (2556) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/U951kpxoDc/ea_profile.json
* 2024-03-13 03:09:38 (2579) [INFO] Backed up EA4 profile to /tmp/U951kpxoDc/ea_profile.json
* 2024-03-13 03:09:40 (300) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-14 03:08:54 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-14 03:10:08 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-14 03:10:08 (1717) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/dbffec2ec4a3c6a99a65c43ef15bc4f7603bcdad845728364d608f14f9946e8a-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/wp-toolkit/repodata/0b55209265624ad2c3a0d4a86611623a767eb91e5054e38a9a28c6a01e555558-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-03-14 03:10:08 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-14 03:10:08 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ycNY68RJGu/ea_profile.json
* 2024-03-14 03:10:09 (2541) [INFO] Backed up EA4 profile to /tmp/ycNY68RJGu/ea_profile.json
* 2024-03-14 03:10:11 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-15 03:08:54 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-15 03:09:41 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-15 03:09:41 (1717) [ERROR] https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/fba6640a4700eea50e3abc4c19e3e97642274c144ce0b4ca3cf9290596ecd8bf-filelists.sqlite.bz2: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/dbffec2ec4a3c6a99a65c43ef15bc4f7603bcdad845728364d608f14f9946e8a-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/wp-toolkit/repodata/0b55209265624ad2c3a0d4a86611623a767eb91e5054e38a9a28c6a01e555558-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-03-15 03:09:41 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-15 03:09:41 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ezc7k9Q1v9/ea_profile.json
* 2024-03-15 03:09:42 (2541) [INFO] Backed up EA4 profile to /tmp/ezc7k9Q1v9/ea_profile.json
* 2024-03-15 03:09:43 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-16 03:09:40 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-16 03:10:32 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-16 03:10:32 (1717) [ERROR] https://download.imunify360.com/el/7/slot-1/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2604:4500:6:203f::8: Network is unreachable"
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-03-16 03:10:33 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-16 03:10:33 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/loDdvl64im/ea_profile.json
* 2024-03-16 03:10:34 (2541) [INFO] Backed up EA4 profile to /tmp/loDdvl64im/ea_profile.json
* 2024-03-16 03:10:35 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-17 03:09:32 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-17 03:09:41 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-17 03:09:41 (1717) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.


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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from imunify360: [Errno 256] No more mirrors to try.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2024-03-17 03:09:41 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-17 03:09:41 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dBTJEnn2Ed/ea_profile.json
* 2024-03-17 03:10:20 (2541) [INFO] Backed up EA4 profile to /tmp/dBTJEnn2Ed/ea_profile.json
* 2024-03-17 03:10:21 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-18 03:08:39 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-18 03:09:15 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-18 03:09:15 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MRdRQhJM09/ea_profile.json
* 2024-03-18 03:09:16 (2541) [INFO] Backed up EA4 profile to /tmp/MRdRQhJM09/ea_profile.json
* 2024-03-18 03:09:17 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-19 03:10:45 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-19 03:12:22 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-19 03:12:22 (1717) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30002 milliseconds')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
Trying other mirror.


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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from imunify360: [Errno 256] No more mirrors to try.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30002 milliseconds')
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 12] Timeout on https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: (28, 'Operation timed out after 30000 milliseconds with 0 out of 0 bytes received')
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "TCP connection reset by peer"
* 2024-03-19 03:12:22 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-19 03:12:22 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ezsNm9Suqg/ea_profile.json
* 2024-03-19 03:17:19 (340) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ezsNm9Suqg/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2520.
* 2024-03-19 03:17:19 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-20 03:09:05 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-20 03:09:42 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-20 03:09:42 (1717) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-03-20 03:09:43 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-20 03:09:43 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PA_o46BCt6/ea_profile.json
* 2024-03-20 03:09:44 (2541) [INFO] Backed up EA4 profile to /tmp/PA_o46BCt6/ea_profile.json
* 2024-03-20 03:09:45 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-21 03:09:21 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-21 03:09:41 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-21 03:09:41 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MnqiekDDfU/ea_profile.json
* 2024-03-21 03:09:41 (2541) [INFO] Backed up EA4 profile to /tmp/MnqiekDDfU/ea_profile.json
* 2024-03-21 03:09:43 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-22 03:08:54 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-22 03:09:32 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-22 03:09:32 (1717) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/96cb7d046dae95bc2d8882c0a11e2625729ac0e5509af7ca24b29a50b756e7a0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/ed51f7b7cc84ef3147efe18aafafb472118938d08e7a58e58fac0285528fd4d8-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/c27430d8e41d06db81611fbe2a4c9de43b4fa969cf790a5192bfe8c8b8564588-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/52104e28ba8978fb1130f4837f55a7a5b073996dcdd63e0028c2f11b529c1ca2-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/dbffec2ec4a3c6a99a65c43ef15bc4f7603bcdad845728364d608f14f9946e8a-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/wp-toolkit/repodata/0b55209265624ad2c3a0d4a86611623a767eb91e5054e38a9a28c6a01e555558-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-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://ftp.rrzn.uni-hannover.de/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.softaculous.com/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 500 - Internal Server Error
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/9c12a6244db35e0d9ba3110b417fc06e8a28196a9bdd43d5e22c48d99b39e619-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/extras/x86_64/repodata/0a5413843d4b238fd3894be760ed384be82139b517ce77a3a71a7b3c6a774a8b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-03-22 03:09:33 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-22 03:09:33 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Dq64_vKuGm/ea_profile.json
* 2024-03-22 03:09:34 (2541) [INFO] Backed up EA4 profile to /tmp/Dq64_vKuGm/ea_profile.json
* 2024-03-22 03:09:35 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-23 03:10:48 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-23 03:11:27 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-23 03:11:27 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VBitNYRua6/ea_profile.json
* 2024-03-23 03:11:28 (2541) [INFO] Backed up EA4 profile to /tmp/VBitNYRua6/ea_profile.json
* 2024-03-23 03:11:29 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-24 03:09:16 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-24 03:09:33 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-24 03:09:33 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YUDsqR5PE0/ea_profile.json
* 2024-03-24 03:09:34 (2541) [INFO] Backed up EA4 profile to /tmp/YUDsqR5PE0/ea_profile.json
* 2024-03-24 03:09:35 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-25 03:08:41 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-25 03:09:13 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-25 03:09:13 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WP4cQPgnGm/ea_profile.json
* 2024-03-25 03:09:14 (2541) [INFO] Backed up EA4 profile to /tmp/WP4cQPgnGm/ea_profile.json
* 2024-03-25 03:09:15 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-26 03:08:47 (1812) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-26 03:09:04 (1716) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-26 03:09:04 (1717) [ERROR] Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 585, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1395, in doCommand
    base.repos.populateSack(mdtype='all', cacheonly=1)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
    sack._retrieve_async(repo, data)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
    if not self._check_uncompressed_db_gen(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
    cached=repo.cache)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
    return decompress(filename, dest=dest, check_timestamps=True)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
    os.utime(out, (fi.st_mtime, fi.st_mtime))
OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2024-03-26 03:09:04 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-26 03:09:04 (2518) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FaOlV_2P4u/ea_profile.json
* 2024-03-26 03:09:11 (2541) [INFO] Backed up EA4 profile to /tmp/FaOlV_2P4u/ea_profile.json
* 2024-03-26 03:09:12 (191) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03-26 03:09:12 (301) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-27 03:08:52 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-27 03:09:21 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-03-27 03:09:21 (1755) [ERROR] https://download.imunify360.com/el/7/slot-6/x86_64/repodata/dbffec2ec4a3c6a99a65c43ef15bc4f7603bcdad845728364d608f14f9946e8a-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/wp-toolkit/repodata/0b55209265624ad2c3a0d4a86611623a767eb91e5054e38a9a28c6a01e555558-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.2.15/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.junda.nl/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-03-27 03:09:22 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-27 03:09:22 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/M5lGZXG1Ww/ea_profile.json
* 2024-03-27 03:09:23 (2641) [INFO] Backed up EA4 profile to /tmp/M5lGZXG1Ww/ea_profile.json
* 2024-03-27 03:09:23 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03-27 03:09:25 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-03-27 03:09:25 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-28 03:08:46 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-28 03:09:20 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-28 03:09:20 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/M48JrjsLQ1/ea_profile.json
* 2024-03-28 03:09:21 (2641) [INFO] Backed up EA4 profile to /tmp/M48JrjsLQ1/ea_profile.json
* 2024-03-28 03:09:22 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03-28 03:09:23 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-03-28 03:09:23 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-29 03:08:49 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-29 03:09:15 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-29 03:09:15 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/K5ZGAhjGFC/ea_profile.json
* 2024-03-29 03:09:16 (2641) [INFO] Backed up EA4 profile to /tmp/K5ZGAhjGFC/ea_profile.json
* 2024-03-29 03:09:17 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03-29 03:09:18 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-03-29 03:09:18 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-30 03:09:31 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-30 03:09:52 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-30 03:09:52 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xhvZVSqU3c/ea_profile.json
* 2024-03-30 03:09:53 (2641) [INFO] Backed up EA4 profile to /tmp/xhvZVSqU3c/ea_profile.json
* 2024-03-30 03:09:54 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03-30 03:09:56 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-03-30 03:09:56 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-03-31 03:09:23 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-03-31 03:09:44 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-03-31 03:09:44 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Kgs7abwJ1c/ea_profile.json
* 2024-03-31 03:09:45 (2641) [INFO] Backed up EA4 profile to /tmp/Kgs7abwJ1c/ea_profile.json
* 2024-03-31 03:09:46 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03-31 03:09:48 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-03-31 03:09:48 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-01 03:08:44 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-01 03:09:25 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-01 03:09:25 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/bKwUm8Lndh/ea_profile.json
* 2024-04-01 03:09:26 (2641) [INFO] Backed up EA4 profile to /tmp/bKwUm8Lndh/ea_profile.json
* 2024-04-01 03:09:26 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-01 03:09:28 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-01 03:09:28 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-02 03:08:56 (1850) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-02 03:09:28 (1754) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-02 03:09:28 (1755) [ERROR] https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.0/wp-toolkit/repodata/a296f05b925fa0c16b35557081f88dbd579f851e191583e6f1e985bc5ef60386-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.0/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.junda.nl/centos/7.9.2009/updates/x86_64/repodata/68b5e0423cdaa712c4e237df44b8552287c1164c8c019de3b57b1f27c209e57c-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-04-02 03:09:28 (997) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-02 03:09:28 (2618) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AIsbC9mEoo/ea_profile.json
* 2024-04-02 03:09:29 (2641) [INFO] Backed up EA4 profile to /tmp/AIsbC9mEoo/ea_profile.json
* 2024-04-02 03:09:30 (194) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-02 03:09:32 (2290) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-02 03:09:32 (305) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-03 03:08:43 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-03 03:09:21 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-03 03:09:21 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nsSXgVzxST/ea_profile.json
* 2024-04-03 03:09:21 (2647) [INFO] Backed up EA4 profile to /tmp/nsSXgVzxST/ea_profile.json
* 2024-04-03 03:09:22 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-03 03:09:24 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-03 03:09:24 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-04 03:09:08 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-04 03:09:32 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-04 03:09:32 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FYscmi7VVZ/ea_profile.json
* 2024-04-04 03:09:33 (2647) [INFO] Backed up EA4 profile to /tmp/FYscmi7VVZ/ea_profile.json
* 2024-04-04 03:09:34 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-04 03:09:36 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-04 03:09:36 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-05 03:08:56 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-05 03:09:47 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-05 03:09:47 (1760) [ERROR] https://download.docker.com/linux/centos/7/x86_64/stable/repodata/96cb7d046dae95bc2d8882c0a11e2625729ac0e5509af7ca24b29a50b756e7a0-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/4ab69131b4cec4039d3b89319fa90445d1942274cd25bfeb66aed8b28bcad98e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/73d5d92a56f1a09c3d07c7a0acca3f6084d8116e2e21705368fe3f9c0ff84ad7-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/faca56d9e744065fefdf4a79a23cf05ccfb5cf7d9616ca552dc1189051c88028-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/84831430ec0c461217f4eb7db470078398309ddab2c75a4ac434199f8b0cde93-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.1/wp-toolkit/repodata/2fe89635ac22a11dd08397ef16fd9085ec83d84a3b2e13071ff2023f7ef46770-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.1/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
* 2024-04-05 03:09:48 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-05 03:09:48 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hd5VnKmfUf/ea_profile.json
* 2024-04-05 03:09:48 (2647) [INFO] Backed up EA4 profile to /tmp/hd5VnKmfUf/ea_profile.json
* 2024-04-05 03:09:49 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-05 03:09:51 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-05 03:09:51 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-06 03:09:28 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-06 03:09:48 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-06 03:09:48 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cjFVKcePMh/ea_profile.json
* 2024-04-06 03:09:49 (2647) [INFO] Backed up EA4 profile to /tmp/cjFVKcePMh/ea_profile.json
* 2024-04-06 03:09:50 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-06 03:09:51 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-06 03:09:51 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-07 03:09:25 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-07 03:09:48 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-07 03:09:48 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N1Nopx07Oo/ea_profile.json
* 2024-04-07 03:09:49 (2647) [INFO] Backed up EA4 profile to /tmp/N1Nopx07Oo/ea_profile.json
* 2024-04-07 03:09:50 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-07 03:09:51 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-07 03:09:51 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-08 03:08:43 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-08 03:09:31 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-08 03:09:31 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0jVSvvKJYv/ea_profile.json
* 2024-04-08 03:09:32 (2647) [INFO] Backed up EA4 profile to /tmp/0jVSvvKJYv/ea_profile.json
* 2024-04-08 03:09:33 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-08 03:09:34 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-08 03:09:34 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-09 03:09:12 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-09 03:09:32 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-09 03:09:32 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2d617NqshM/ea_profile.json
* 2024-04-09 03:09:32 (2647) [INFO] Backed up EA4 profile to /tmp/2d617NqshM/ea_profile.json
* 2024-04-09 03:09:33 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-09 03:09:35 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-09 03:09:35 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-10 03:08:52 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-10 03:09:26 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-10 03:09:26 (1760) [ERROR] https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.1/wp-toolkit/repodata/2fe89635ac22a11dd08397ef16fd9085ec83d84a3b2e13071ff2023f7ef46770-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.1/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-04-10 03:09:27 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-10 03:09:27 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fmorOUQKGs/ea_profile.json
* 2024-04-10 03:09:28 (2647) [INFO] Backed up EA4 profile to /tmp/fmorOUQKGs/ea_profile.json
* 2024-04-10 03:09:28 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-10 03:09:31 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-10 03:09:31 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-11 03:08:49 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-11 03:09:33 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-11 03:09:33 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/nT2UwghBIb/ea_profile.json
* 2024-04-11 03:09:35 (2647) [INFO] Backed up EA4 profile to /tmp/nT2UwghBIb/ea_profile.json
* 2024-04-11 03:09:35 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-11 03:09:37 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-11 03:09:37 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-12 03:09:21 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-12 03:09:46 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-12 03:09:46 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jNuJlU7Wxn/ea_profile.json
* 2024-04-12 03:09:47 (2647) [INFO] Backed up EA4 profile to /tmp/jNuJlU7Wxn/ea_profile.json
* 2024-04-12 03:09:48 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-12 03:09:50 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-12 03:09:50 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-13 03:09:24 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-13 03:09:45 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-13 03:09:45 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/l233Py4l9f/ea_profile.json
* 2024-04-13 03:09:46 (2647) [INFO] Backed up EA4 profile to /tmp/l233Py4l9f/ea_profile.json
* 2024-04-13 03:09:47 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-13 03:09:48 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-13 03:09:48 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-14 03:09:25 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-14 03:09:48 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-14 03:09:48 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IzI4k0CRCR/ea_profile.json
* 2024-04-14 03:09:49 (2647) [INFO] Backed up EA4 profile to /tmp/IzI4k0CRCR/ea_profile.json
* 2024-04-14 03:09:50 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-14 03:09:52 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-14 03:09:52 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-15 03:08:46 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-15 03:09:05 (1759) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-15 03:09:05 (1760) [ERROR] Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 585, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1395, in doCommand
    base.repos.populateSack(mdtype='all', cacheonly=1)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
    sack._retrieve_async(repo, data)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
    if not self._check_uncompressed_db_gen(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
    cached=repo.cache)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
    return decompress(filename, dest=dest, check_timestamps=True)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
    os.utime(out, (fi.st_mtime, fi.st_mtime))
OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2024-04-15 03:09:06 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-15 03:09:06 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0GU6CWKmNp/ea_profile.json
* 2024-04-15 03:09:30 (346) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0GU6CWKmNp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 2626.
* 2024-04-15 03:09:30 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-16 03:09:21 (6907) [INFO] Self-update of script version 33 requested.
* 2024-04-16 03:09:21 (6929) [INFO] Script is up to date.
* 2024-04-16 03:09:24 (1855) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-16 03:10:00 (1001) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-16 03:10:01 (2624) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7AL2lOh00D/ea_profile.json
* 2024-04-16 03:10:02 (2647) [INFO] Backed up EA4 profile to /tmp/7AL2lOh00D/ea_profile.json
* 2024-04-16 03:10:03 (196) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-16 03:10:04 (2295) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-16 03:10:04 (307) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-17 03:08:41 (6907) [INFO] Self-update of script version 33 requested.
* 2024-04-17 03:08:41 (6912) [INFO] Newer version of script found. Downloading.
* 2024-04-17 03:08:41 (6921) [INFO] Script update to version 34 successful.
* 2024-04-17 03:08:44 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-17 03:09:23 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-17 03:09:23 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/U7WN5HEEP9/ea_profile.json
* 2024-04-17 03:09:24 (2664) [INFO] Backed up EA4 profile to /tmp/U7WN5HEEP9/ea_profile.json
* 2024-04-17 03:09:24 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-17 03:09:26 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-17 03:09:26 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-18 03:09:13 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-18 03:09:13 (7128) [INFO] Script is up to date.
* 2024-04-18 03:09:16 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-18 03:09:38 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-18 03:09:38 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WRDoBZUPta/ea_profile.json
* 2024-04-18 03:09:38 (2664) [INFO] Backed up EA4 profile to /tmp/WRDoBZUPta/ea_profile.json
* 2024-04-18 03:09:39 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-18 03:09:41 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-18 03:09:41 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-19 03:14:12 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-19 03:14:13 (7128) [INFO] Script is up to date.
* 2024-04-19 03:14:15 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-19 03:14:59 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-19 03:14:59 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HjPMBLRre4/ea_profile.json
* 2024-04-19 03:15:00 (2664) [INFO] Backed up EA4 profile to /tmp/HjPMBLRre4/ea_profile.json
* 2024-04-19 03:15:01 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-19 03:15:03 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-19 03:15:03 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-20 03:09:07 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-20 03:09:07 (7128) [INFO] Script is up to date.
* 2024-04-20 03:09:10 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-20 03:09:29 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-20 03:09:29 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/daM9uLdsQ3/ea_profile.json
* 2024-04-20 03:09:30 (2664) [INFO] Backed up EA4 profile to /tmp/daM9uLdsQ3/ea_profile.json
* 2024-04-20 03:09:31 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-20 03:09:33 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-20 03:09:33 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-21 03:09:48 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-21 03:09:48 (7128) [INFO] Script is up to date.
* 2024-04-21 03:09:52 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-21 03:10:17 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-21 03:10:17 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R6oy8UMND6/ea_profile.json
* 2024-04-21 03:10:18 (2664) [INFO] Backed up EA4 profile to /tmp/R6oy8UMND6/ea_profile.json
* 2024-04-21 03:10:19 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-21 03:10:20 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-21 03:10:20 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-22 03:08:50 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-22 03:08:50 (7128) [INFO] Script is up to date.
* 2024-04-22 03:08:52 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-22 03:09:23 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-22 03:09:23 (1777) [ERROR] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/7bd4173aac5e8f503cf2bc322fe0919ce1be5c5ad7cbf2cd00ad99e44b6d6f34-primary.sqlite.bz2: [Errno -3] Error performing checksum: Error opening file for checksum: Error opening file for checksum: /var/cache/yum/x86_64/7/imunify360-rollout-4/7bd4173aac5e8f503cf2bc322fe0919ce1be5c5ad7cbf2cd00ad99e44b6d6f34-primary.sqlite.bz2
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.junda.nl/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-04-22 03:09:23 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-22 03:09:23 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qwDEbHdqjU/ea_profile.json
* 2024-04-22 03:09:24 (2664) [INFO] Backed up EA4 profile to /tmp/qwDEbHdqjU/ea_profile.json
* 2024-04-22 03:09:24 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-22 03:09:26 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-22 03:09:26 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-23 03:09:15 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-23 03:09:15 (7128) [INFO] Script is up to date.
* 2024-04-23 03:09:17 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-23 03:11:11 (1776) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-23 03:11:11 (1777) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/d52d435e08dac79249d5631a79d3061530870307d1407a065c06cca92f561e64-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/d52d435e08dac79249d5631a79d3061530870307d1407a065c06cca92f561e64-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.


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

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

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

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

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

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

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

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

imunify360: Check uncompressed DB failed
* 2024-04-23 03:11:11 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-23 03:11:11 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UX0IKFD6hW/ea_profile.json
* 2024-04-23 03:11:17 (2664) [INFO] Backed up EA4 profile to /tmp/UX0IKFD6hW/ea_profile.json
* 2024-04-23 03:11:17 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-23 03:11:19 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-23 03:11:19 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-24 03:09:11 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-24 03:09:11 (7128) [INFO] Script is up to date.
* 2024-04-24 03:09:13 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-24 03:09:34 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-24 03:09:34 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vid_Ee7URU/ea_profile.json
* 2024-04-24 03:09:35 (2664) [INFO] Backed up EA4 profile to /tmp/vid_Ee7URU/ea_profile.json
* 2024-04-24 03:09:36 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-24 03:09:38 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-24 03:09:38 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-25 03:08:39 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-25 03:08:39 (7128) [INFO] Script is up to date.
* 2024-04-25 03:08:42 (1872) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-25 03:09:15 (1018) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-25 03:09:15 (2641) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VxwKPxPOWs/ea_profile.json
* 2024-04-25 03:09:16 (2664) [INFO] Backed up EA4 profile to /tmp/VxwKPxPOWs/ea_profile.json
* 2024-04-25 03:09:17 (192) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-25 03:09:18 (2312) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-25 03:09:18 (303) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-26 03:08:50 (7106) [INFO] Self-update of script version 34 requested.
* 2024-04-26 03:08:51 (7111) [INFO] Newer version of script found. Downloading.
* 2024-04-26 03:08:51 (7120) [INFO] Script update to version 35 successful.
* 2024-04-26 03:08:54 (1881) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-26 03:09:48 (1785) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-04-26 03:09:48 (1786) [ERROR] https://download.docker.com/linux/centos/7/x86_64/stable/repodata/9ce5541fb4dbb5f2c49e2f4e96c7743e5e1bb9525d68828a8267e243c0263c46-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.softaculous.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.junda.nl/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.junda.nl/centos/7.9.2009/updates/x86_64/repodata/9680c4fd3871e31153f67e1e03241a3d3af3adc141f71be06761e14e81c605ad-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-04-26 03:09:49 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-26 03:09:49 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/53IDthx_Cb/ea_profile.json
* 2024-04-26 03:09:50 (2782) [INFO] Backed up EA4 profile to /tmp/53IDthx_Cb/ea_profile.json
* 2024-04-26 03:09:51 (198) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-26 03:09:52 (2321) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-26 03:09:52 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-27 03:09:19 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-27 03:09:19 (7138) [INFO] Script is up to date.
* 2024-04-27 03:09:21 (1881) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-27 03:09:37 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-27 03:09:37 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rPF6xv6_V0/ea_profile.json
* 2024-04-27 03:09:38 (2782) [INFO] Backed up EA4 profile to /tmp/rPF6xv6_V0/ea_profile.json
* 2024-04-27 03:09:38 (198) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-27 03:09:40 (2321) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-27 03:09:40 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-28 03:09:22 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-28 03:09:23 (7138) [INFO] Script is up to date.
* 2024-04-28 03:09:26 (1881) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-28 03:09:44 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-28 03:09:44 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8yCB5uE1EG/ea_profile.json
* 2024-04-28 03:09:44 (2782) [INFO] Backed up EA4 profile to /tmp/8yCB5uE1EG/ea_profile.json
* 2024-04-28 03:09:45 (198) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-28 03:09:47 (2321) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-28 03:09:47 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-29 03:08:37 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-29 03:08:37 (7138) [INFO] Script is up to date.
* 2024-04-29 03:08:39 (1881) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-29 03:09:12 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-29 03:09:12 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PJSmC4YOGi/ea_profile.json
* 2024-04-29 03:09:13 (2782) [INFO] Backed up EA4 profile to /tmp/PJSmC4YOGi/ea_profile.json
* 2024-04-29 03:09:14 (198) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-29 03:09:15 (2321) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-29 03:09:15 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-04-30 03:08:38 (7116) [INFO] Self-update of script version 35 requested.
* 2024-04-30 03:08:38 (7138) [INFO] Script is up to date.
* 2024-04-30 03:08:40 (1881) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-04-30 03:09:11 (1029) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-04-30 03:09:11 (2759) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jj0jVDhlN3/ea_profile.json
* 2024-04-30 03:09:12 (2782) [INFO] Backed up EA4 profile to /tmp/jj0jVDhlN3/ea_profile.json
* 2024-04-30 03:09:12 (198) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04-30 03:09:14 (2321) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-04-30 03:09:14 (309) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-01 03:09:13 (7116) [INFO] Self-update of script version 35 requested.
* 2024-05-01 03:09:13 (7121) [INFO] Newer version of script found. Downloading.
* 2024-05-01 03:09:14 (7130) [INFO] Script update to version 36 successful.
* 2024-05-01 03:09:36 (1882) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-01 03:09:55 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-01 03:09:55 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oDmtrKha2t/ea_profile.json
* 2024-05-01 03:09:56 (3173) [INFO] Backed up EA4 profile to /tmp/oDmtrKha2t/ea_profile.json
* 2024-05-01 03:09:57 (199) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-01 03:09:58 (2313) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-01 03:09:58 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-02 03:09:26 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-02 03:09:26 (7530) [INFO] Script is up to date.
* 2024-05-02 03:09:35 (1882) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-02 03:09:53 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-02 03:09:53 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y0ueqUxs_g/ea_profile.json
* 2024-05-02 03:09:54 (3173) [INFO] Backed up EA4 profile to /tmp/Y0ueqUxs_g/ea_profile.json
* 2024-05-02 03:09:54 (199) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-02 03:09:56 (2313) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-02 03:09:56 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-03 03:08:46 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-03 03:08:46 (7530) [INFO] Script is up to date.
* 2024-05-03 03:08:49 (1882) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-03 03:09:20 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-03 03:09:20 (1787) [ERROR] http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/updates/x86_64/repodata/3efab55ebd2ba672a39168311a4680bd3187bf42975572a8b10008834ab82c98-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-05-03 03:09:21 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-03 03:09:21 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UTx49zdAnK/ea_profile.json
* 2024-05-03 03:09:21 (3173) [INFO] Backed up EA4 profile to /tmp/UTx49zdAnK/ea_profile.json
* 2024-05-03 03:09:22 (199) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-03 03:09:24 (2313) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-03 03:09:24 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-04 03:09:10 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-04 03:09:10 (7530) [INFO] Script is up to date.
* 2024-05-04 03:09:13 (1882) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-04 03:09:35 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-04 03:09:35 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qyg7uuvrux/ea_profile.json
* 2024-05-04 03:09:36 (3173) [INFO] Backed up EA4 profile to /tmp/qyg7uuvrux/ea_profile.json
* 2024-05-04 03:09:37 (199) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-04 03:09:39 (2313) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-04 03:09:39 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-05 03:09:23 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-05 03:09:23 (7530) [INFO] Script is up to date.
* 2024-05-05 03:09:26 (1882) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-05 03:09:48 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-05 03:09:48 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/v8POdWesAN/ea_profile.json
* 2024-05-05 03:09:49 (3173) [INFO] Backed up EA4 profile to /tmp/v8POdWesAN/ea_profile.json
* 2024-05-05 03:09:50 (199) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-05 03:09:52 (2313) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-05 03:09:52 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-06 03:08:36 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-06 03:08:36 (7530) [INFO] Script is up to date.
* 2024-05-06 03:08:39 (1882) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-06 03:08:41 (1786) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-06 03:08:41 (1787) [ERROR] https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol version."
Trying other mirror.


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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from imunify360: [Errno 256] No more mirrors to try.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#35 - "Peer reports incompatible or unsupported protocol version."
* 2024-05-06 03:08:42 (1030) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-06 03:08:42 (3150) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_tMWc1Vbw1/ea_profile.json
* 2024-05-06 03:08:43 (346) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_tMWc1Vbw1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 3152.
* 2024-05-06 03:08:43 (310) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-07 03:08:44 (7508) [INFO] Self-update of script version 36 requested.
* 2024-05-07 03:08:45 (7513) [INFO] Newer version of script found. Downloading.
* 2024-05-07 03:08:45 (7522) [INFO] Script update to version 37 successful.
* 2024-05-07 03:08:46 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-07 03:08:46 (6322) [INFO] 
* 2024-05-07 03:08:46 (6352) [INFO] 
* 2024-05-07 03:08:47 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-07 03:09:15 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-07 03:09:15 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pJI0M2BeEc/ea_profile.json
* 2024-05-07 03:09:16 (3212) [INFO] Backed up EA4 profile to /tmp/pJI0M2BeEc/ea_profile.json
* 2024-05-07 03:09:17 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-07 03:09:18 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-07 03:09:18 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-08 03:08:33 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-08 03:08:33 (7570) [INFO] Script is up to date.
* 2024-05-08 03:08:34 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-08 03:08:34 (6322) [INFO] 
* 2024-05-08 03:08:34 (6352) [INFO] 
* 2024-05-08 03:08:36 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-08 03:09:03 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-08 03:09:03 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hHJ88SXj3I/ea_profile.json
* 2024-05-08 03:09:04 (3212) [INFO] Backed up EA4 profile to /tmp/hHJ88SXj3I/ea_profile.json
* 2024-05-08 03:09:05 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-08 03:09:06 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-08 03:09:06 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-09 03:08:44 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-09 03:08:44 (7570) [INFO] Script is up to date.
* 2024-05-09 03:08:45 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-09 03:08:45 (6322) [INFO] 
* 2024-05-09 03:08:45 (6352) [INFO] 
* 2024-05-09 03:08:47 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-09 03:09:02 (1825) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-09 03:09:02 (1826) [ERROR] Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 585, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1395, in doCommand
    base.repos.populateSack(mdtype='all', cacheonly=1)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
    sack._retrieve_async(repo, data)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
    if not self._check_uncompressed_db_gen(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
    cached=repo.cache)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
    return decompress(filename, dest=dest, check_timestamps=True)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
    os.utime(out, (fi.st_mtime, fi.st_mtime))
OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/imunify360-rollout-7/gen/primary_db.sqlite'
* 2024-05-09 03:09:03 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-09 03:09:03 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kDfVOCkGVZ/ea_profile.json
* 2024-05-09 03:09:14 (3212) [INFO] Backed up EA4 profile to /tmp/kDfVOCkGVZ/ea_profile.json
* 2024-05-09 03:09:15 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-09 03:09:17 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-09 03:09:17 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-10 03:09:10 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-10 03:09:10 (7570) [INFO] Script is up to date.
* 2024-05-10 03:09:11 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-10 03:09:11 (6322) [INFO] 
* 2024-05-10 03:09:11 (6352) [INFO] 
* 2024-05-10 03:09:13 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-10 03:09:32 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-10 03:09:32 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pi_Cgq2sWe/ea_profile.json
* 2024-05-10 03:09:33 (3212) [INFO] Backed up EA4 profile to /tmp/pi_Cgq2sWe/ea_profile.json
* 2024-05-10 03:09:34 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-10 03:09:36 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-10 03:09:36 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-11 03:09:09 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-11 03:09:09 (7570) [INFO] Script is up to date.
* 2024-05-11 03:09:10 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-11 03:09:10 (6322) [INFO] 
* 2024-05-11 03:09:10 (6352) [INFO] 
* 2024-05-11 03:09:12 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-11 03:09:27 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-11 03:09:27 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/g85RJ1HKjo/ea_profile.json
* 2024-05-11 03:09:28 (3212) [INFO] Backed up EA4 profile to /tmp/g85RJ1HKjo/ea_profile.json
* 2024-05-11 03:09:28 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-11 03:09:30 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-11 03:09:30 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-12 03:09:09 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-12 03:09:09 (7570) [INFO] Script is up to date.
* 2024-05-12 03:09:10 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-12 03:09:10 (6322) [INFO] 
* 2024-05-12 03:09:10 (6352) [INFO] 
* 2024-05-12 03:09:12 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-12 03:09:26 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-12 03:09:26 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NxSbIeGYnU/ea_profile.json
* 2024-05-12 03:09:27 (3212) [INFO] Backed up EA4 profile to /tmp/NxSbIeGYnU/ea_profile.json
* 2024-05-12 03:09:28 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-12 03:09:30 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-12 03:09:30 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-13 03:08:36 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-13 03:08:36 (7570) [INFO] Script is up to date.
* 2024-05-13 03:08:37 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-13 03:08:37 (6322) [INFO] 
* 2024-05-13 03:08:37 (6352) [INFO] 
* 2024-05-13 03:08:39 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-13 03:09:10 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-13 03:09:10 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OqSSI6escO/ea_profile.json
* 2024-05-13 03:09:10 (3212) [INFO] Backed up EA4 profile to /tmp/OqSSI6escO/ea_profile.json
* 2024-05-13 03:09:11 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-13 03:09:12 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-13 03:09:12 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-14 03:08:45 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-14 03:08:45 (7570) [INFO] Script is up to date.
* 2024-05-14 03:08:46 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-14 03:08:46 (6322) [INFO] 
* 2024-05-14 03:08:46 (6352) [INFO] 
* 2024-05-14 03:08:47 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-14 03:09:22 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-14 03:09:22 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/yaxq2QXhH5/ea_profile.json
* 2024-05-14 03:09:22 (3212) [INFO] Backed up EA4 profile to /tmp/yaxq2QXhH5/ea_profile.json
* 2024-05-14 03:09:23 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-14 03:09:25 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-14 03:09:25 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-15 03:08:34 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-15 03:08:34 (7570) [INFO] Script is up to date.
* 2024-05-15 03:08:35 (6321) [INFO] Running: /usr/bin/findmnt -no PROPAGATION /usr
* 2024-05-15 03:08:35 (6322) [INFO] 
* 2024-05-15 03:08:35 (6352) [INFO] 
* 2024-05-15 03:08:36 (1921) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-15 03:09:13 (1033) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-15 03:09:13 (3189) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pgwwtY4Pdp/ea_profile.json
* 2024-05-15 03:09:14 (3212) [INFO] Backed up EA4 profile to /tmp/pgwwtY4Pdp/ea_profile.json
* 2024-05-15 03:09:15 (200) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-15 03:09:16 (2352) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-15 03:09:16 (313) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-16 03:09:29 (7548) [INFO] Self-update of script version 37 requested.
* 2024-05-16 03:09:29 (7553) [INFO] Newer version of script found. Downloading.
* 2024-05-16 03:09:30 (7562) [INFO] Script update to version 38 successful.
* 2024-05-16 03:09:32 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-16 03:09:57 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-16 03:09:57 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/VrxGhchIhr/ea_profile.json
* 2024-05-16 03:09:58 (5705) [INFO] Backed up EA4 profile to /tmp/VrxGhchIhr/ea_profile.json
* 2024-05-16 03:09:59 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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 03:10:01 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-16 03:10:01 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-17 03:08:50 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-17 03:08:50 (7748) [INFO] Script is up to date.
* 2024-05-17 03:08:52 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-17 03:09:22 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-17 03:09:22 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OUAYta5Lh8/ea_profile.json
* 2024-05-17 03:09:23 (5705) [INFO] Backed up EA4 profile to /tmp/OUAYta5Lh8/ea_profile.json
* 2024-05-17 03:09:24 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-17 03:09:25 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-17 03:09:25 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-18 03:09:08 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-18 03:09:08 (7748) [INFO] Script is up to date.
* 2024-05-18 03:09:11 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-18 03:09:27 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-18 03:09:27 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_ikUz9gEUs/ea_profile.json
* 2024-05-18 03:09:28 (5705) [INFO] Backed up EA4 profile to /tmp/_ikUz9gEUs/ea_profile.json
* 2024-05-18 03:09:29 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-18 03:09:31 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-18 03:09:31 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-19 03:09:10 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-19 03:09:10 (7748) [INFO] Script is up to date.
* 2024-05-19 03:09:13 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-19 03:09:31 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-19 03:09:31 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NaXiK6mhk8/ea_profile.json
* 2024-05-19 03:09:32 (5705) [INFO] Backed up EA4 profile to /tmp/NaXiK6mhk8/ea_profile.json
* 2024-05-19 03:09:32 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-19 03:09:34 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-19 03:09:34 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-20 03:08:33 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-20 03:08:33 (7748) [INFO] Script is up to date.
* 2024-05-20 03:08:35 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-20 03:09:03 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-20 03:09:03 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PEHDJrOKH_/ea_profile.json
* 2024-05-20 03:09:03 (5705) [INFO] Backed up EA4 profile to /tmp/PEHDJrOKH_/ea_profile.json
* 2024-05-20 03:09:04 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-20 03:09:06 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-20 03:09:06 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-21 03:09:14 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-21 03:09:14 (7748) [INFO] Script is up to date.
* 2024-05-21 03:09:16 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-21 03:09:31 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-21 03:09:31 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OIjfV6PDgj/ea_profile.json
* 2024-05-21 03:09:32 (5705) [INFO] Backed up EA4 profile to /tmp/OIjfV6PDgj/ea_profile.json
* 2024-05-21 03:09:32 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-21 03:09:34 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-21 03:09:34 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-22 03:09:04 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-22 03:09:04 (7748) [INFO] Script is up to date.
* 2024-05-22 03:09:06 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-22 03:09:39 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-22 03:09:39 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/R2ky3lYzP8/ea_profile.json
* 2024-05-22 03:09:40 (5705) [INFO] Backed up EA4 profile to /tmp/R2ky3lYzP8/ea_profile.json
* 2024-05-22 03:09:41 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-22 03:09:42 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-22 03:09:42 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-23 03:08:59 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-23 03:08:59 (7748) [INFO] Script is up to date.
* 2024-05-23 03:09:02 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-23 03:09:21 (1932) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-23 03:09:21 (1933) [ERROR] https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/updates/x86_64/repodata/52c5dbf32d1549111153e47fd493a976f3273327364606be10962af3bccae78b-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

updates: Check uncompressed DB failed
* 2024-05-23 03:09:21 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-23 03:09:21 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MWOUQ25fYa/ea_profile.json
* 2024-05-23 03:09:24 (5705) [INFO] Backed up EA4 profile to /tmp/MWOUQ25fYa/ea_profile.json
* 2024-05-23 03:09:25 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-23 03:09:27 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-23 03:09:27 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-24 03:09:23 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-24 03:09:23 (7748) [INFO] Script is up to date.
* 2024-05-24 03:09:25 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-24 03:09:32 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-24 03:09:32 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qTTbn0dxT1/ea_profile.json
* 2024-05-24 03:09:33 (5705) [INFO] Backed up EA4 profile to /tmp/qTTbn0dxT1/ea_profile.json
* 2024-05-24 03:09:34 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.114.2.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-24 03:09:36 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-24 03:09:36 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-25 03:09:17 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-25 03:09:17 (7748) [INFO] Script is up to date.
* 2024-05-25 03:09:19 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-25 03:09:33 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-25 03:09:33 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sKfyZFIQQY/ea_profile.json
* 2024-05-25 03:09:34 (5705) [INFO] Backed up EA4 profile to /tmp/sKfyZFIQQY/ea_profile.json
* 2024-05-25 03:09:35 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.118.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-25 03:09:36 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-25 03:09:36 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-26 03:09:17 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-26 03:09:17 (7748) [INFO] Script is up to date.
* 2024-05-26 03:09:21 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-26 03:09:38 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-26 03:09:38 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/b6S2kxZnUU/ea_profile.json
* 2024-05-26 03:09:39 (5705) [INFO] Backed up EA4 profile to /tmp/b6S2kxZnUU/ea_profile.json
* 2024-05-26 03:09:40 (201) [WARN] *** Elevation Blocker detected: ***
The running kernel version (3.10.0-1160.108.1.el7.x86_64) does not match that of
the default boot entry (3.10.0-1160.118.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-26 03:09:42 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-26 03:09:42 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-27 03:08:38 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-27 03:08:38 (7748) [INFO] Script is up to date.
* 2024-05-27 03:08:40 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-27 03:09:05 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-27 03:09:05 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SZAWnRAGFi/ea_profile.json
* 2024-05-27 03:09:06 (5705) [INFO] Backed up EA4 profile to /tmp/SZAWnRAGFi/ea_profile.json
* 2024-05-27 03:09:08 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-27 03:09:08 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-28 03:08:41 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-28 03:08:41 (7748) [INFO] Script is up to date.
* 2024-05-28 03:08:43 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-28 03:09:07 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-28 03:09:07 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7tGbamqhZS/ea_profile.json
* 2024-05-28 03:09:08 (5705) [INFO] Backed up EA4 profile to /tmp/7tGbamqhZS/ea_profile.json
* 2024-05-28 03:09:10 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-28 03:09:10 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-29 03:08:35 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-29 03:08:35 (7748) [INFO] Script is up to date.
* 2024-05-29 03:08:38 (2028) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-29 03:09:05 (1039) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-29 03:09:05 (5682) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KVgd4FVC4D/ea_profile.json
* 2024-05-29 03:09:06 (5705) [INFO] Backed up EA4 profile to /tmp/KVgd4FVC4D/ea_profile.json
* 2024-05-29 03:09:08 (2459) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-29 03:09:08 (314) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-30 03:08:44 (7726) [INFO] Self-update of script version 38 requested.
* 2024-05-30 03:08:44 (7731) [INFO] Newer version of script found. Downloading.
* 2024-05-30 03:08:44 (7740) [INFO] Script update to version 39 successful.
* 2024-05-30 03:08:45 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-05-30 03:08:45 (6568) [INFO] 
* 2024-05-30 03:08:48 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-05-30 03:08:48 (6598) [INFO] 
* 2024-05-30 03:08:50 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-30 03:09:19 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-30 03:09:19 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PNIXozektp/ea_profile.json
* 2024-05-30 03:09:19 (5773) [INFO] Backed up EA4 profile to /tmp/PNIXozektp/ea_profile.json
* 2024-05-30 03:09:21 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-30 03:09:21 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-05-31 03:08:51 (7795) [INFO] Self-update of script version 39 requested.
* 2024-05-31 03:08:51 (7817) [INFO] Script is up to date.
* 2024-05-31 03:08:52 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-05-31 03:08:52 (6568) [INFO] 
* 2024-05-31 03:08:58 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-05-31 03:08:58 (6598) [INFO] 
* 2024-05-31 03:09:00 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-05-31 03:09:26 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-05-31 03:09:26 (1982) [ERROR] https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/ef6bcb19d7d18e089209ff20e80701631ca455c5aa5ea2ad449fbfa90d8b1ee5-updateinfo.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/1066950cc1da4fd445a81a6274409b32f87dbaecb45999066fd9b9382cd2b82d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/65c4f66e2808d328890505c3c2f13bb35a96f457d1c21a6346191c4dc07e6080-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/84918c7f1af216697a78d124bdf9431a3fce3d3a92cfd3acc2ae4492c921311c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/77a57c3d6c53d2c08a8dafd38ae6919b8cc38b6ce41e5ebc346b730a355b47c8-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.wrz.de/pub/CentOS/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror1.hs-esslingen.de/pub/Mirrors/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.softaculous.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.halifax.rwth-aachen.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.fau.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/873e3f4ba7e1f50ba189c86efb1630c800da1efaeb20bbbcbd240390ad9214b5-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-05-31 03:09:26 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-05-31 03:09:26 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cne54KbP6S/ea_profile.json
* 2024-05-31 03:09:27 (5773) [INFO] Backed up EA4 profile to /tmp/cne54KbP6S/ea_profile.json
* 2024-05-31 03:09:29 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-05-31 03:09:29 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-01 03:09:12 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-01 03:09:12 (7817) [INFO] Script is up to date.
* 2024-06-01 03:09:13 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-01 03:09:13 (6568) [INFO] 
* 2024-06-01 03:09:16 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-01 03:09:16 (6598) [INFO] 
* 2024-06-01 03:09:18 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-01 03:09:34 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-01 03:09:34 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3H0wWBAn66/ea_profile.json
* 2024-06-01 03:09:35 (5773) [INFO] Backed up EA4 profile to /tmp/3H0wWBAn66/ea_profile.json
* 2024-06-01 03:09:37 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-01 03:09:37 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-02 03:09:13 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-02 03:09:13 (7817) [INFO] Script is up to date.
* 2024-06-02 03:09:14 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-02 03:09:14 (6568) [INFO] 
* 2024-06-02 03:09:17 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-02 03:09:17 (6598) [INFO] 
* 2024-06-02 03:09:19 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-02 03:09:35 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-02 03:09:35 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/XHLOKwkDcT/ea_profile.json
* 2024-06-02 03:09:36 (5773) [INFO] Backed up EA4 profile to /tmp/XHLOKwkDcT/ea_profile.json
* 2024-06-02 03:09:38 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-02 03:09:38 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-03 03:08:32 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-03 03:08:32 (7817) [INFO] Script is up to date.
* 2024-06-03 03:08:33 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-03 03:08:33 (6568) [INFO] 
* 2024-06-03 03:08:35 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-03 03:08:35 (6598) [INFO] 
* 2024-06-03 03:08:37 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-03 03:09:11 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-03 03:09:11 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Lbicszl6Nv/ea_profile.json
* 2024-06-03 03:09:12 (5773) [INFO] Backed up EA4 profile to /tmp/Lbicszl6Nv/ea_profile.json
* 2024-06-03 03:09:14 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-03 03:09:14 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-04 03:08:46 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-04 03:08:46 (7817) [INFO] Script is up to date.
* 2024-06-04 03:08:47 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-04 03:08:47 (6568) [INFO] 
* 2024-06-04 03:08:50 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-04 03:08:50 (6598) [INFO] 
* 2024-06-04 03:08:52 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-04 03:09:04 (1981) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-06-04 03:09:04 (1982) [ERROR] Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 375, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 184, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 585, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 1395, in doCommand
    base.repos.populateSack(mdtype='all', cacheonly=1)
  File "/usr/lib/python2.7/site-packages/yum/repos.py", line 380, in populateSack
    sack._retrieve_async(repo, data)
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 185, in _retrieve_async
    if not self._check_uncompressed_db_gen(repo, mydbtype):
  File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 287, in _check_uncompressed_db_gen
    cached=repo.cache)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1176, in repo_gen_decompress
    return decompress(filename, dest=dest, check_timestamps=True)
  File "/usr/lib/python2.7/site-packages/yum/misc.py", line 1163, in decompress
    os.utime(out, (fi.st_mtime, fi.st_mtime))
OSError: [Errno 2] No such file or directory: '/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite'
* 2024-06-04 03:09:04 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-04 03:09:04 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LoN_M1s_qy/ea_profile.json
* 2024-06-04 03:09:11 (5773) [INFO] Backed up EA4 profile to /tmp/LoN_M1s_qy/ea_profile.json
* 2024-06-04 03:09:13 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-04 03:09:13 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-05 03:08:40 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-05 03:08:40 (7817) [INFO] Script is up to date.
* 2024-06-05 03:08:41 (6567) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-05 03:08:41 (6568) [INFO] 
* 2024-06-05 03:08:41 (6581) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-05 03:08:41 (6598) [INFO] 
* 2024-06-05 03:08:43 (2077) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-05 03:09:14 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-05 03:09:14 (5750) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4xFp2dGctD/ea_profile.json
* 2024-06-05 03:09:15 (5773) [INFO] Backed up EA4 profile to /tmp/4xFp2dGctD/ea_profile.json
* 2024-06-05 03:09:17 (2508) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-05 03:09:17 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-06 03:09:23 (7795) [INFO] Self-update of script version 39 requested.
* 2024-06-06 03:09:23 (7800) [INFO] Newer version of script found. Downloading.
* 2024-06-06 03:09:23 (7809) [INFO] Script update to version 40 successful.
* 2024-06-06 03:09:24 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-06 03:09:24 (6580) [INFO] 
* 2024-06-06 03:09:27 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-06 03:09:27 (6610) [INFO] 
* 2024-06-06 03:09:29 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-06 03:09:35 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-06 03:09:35 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9zJS2qrSgq/ea_profile.json
* 2024-06-06 03:09:36 (5785) [INFO] Backed up EA4 profile to /tmp/9zJS2qrSgq/ea_profile.json
* 2024-06-06 03:09:38 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-06 03:09:38 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-07 03:08:55 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-07 03:08:55 (7829) [INFO] Script is up to date.
* 2024-06-07 03:08:56 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-07 03:08:56 (6580) [INFO] 
* 2024-06-07 03:08:59 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 3, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-07 03:09:00 (6610) [INFO] 
* 2024-06-07 03:09:02 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-07 03:09:18 (1982) [WARN] Initial run of "yum makecache" failed: http://31.22.112.31/cpanelsync/repos/CentOS/7/cPAddons/x86_64/repodata/09d0fd29b1475e0c4501df58bd892b1a8d0446824daa06005fcd2b4a83287a94-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://31.22.112.31/cpanelsync/repos/CentOS/7/cpanel-plugins/repodata/a81cf28d281285e4eaf20ac143e9b0d028a9a0f6c122939df1fd206568fdd029-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/c4a3ed3173b7171f9636d6a149b9c932730f74fe2cd50d9ab7bc4caed7baf5aa-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/ef6bcb19d7d18e089209ff20e80701631ca455c5aa5ea2ad449fbfa90d8b1ee5-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/1066950cc1da4fd445a81a6274409b32f87dbaecb45999066fd9b9382cd2b82d-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/aa1f3958af9cb5f1f6c34b5725f63de4f5e3e46c236205b598fecfec6ad506f6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/65c4f66e2808d328890505c3c2f13bb35a96f457d1c21a6346191c4dc07e6080-updateinfo.xml.gz: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/002b81c9c93242d32766c4f8496aea981ac7df990c5b652cfc917b2cef7c6364-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/wp-toolkit/repodata/6a0ce87c8e04f3b37985ccf6df87bdac7e70a20443d9af161396fcbd56e0ed9c-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.3.2/thirdparty/repodata/e476b6187d7fdf21ff3a7e8d521e7ad6ff15ea00ac660ff6e42a1fa846d59a32-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.junda.nl/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirror.iphh.net/CentOS/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.rackspeed.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/os/x86_64/repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.eu.oneandone.net/linux/distributions/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirrors.xtom.de/centos/7.9.2009/updates/x86_64/repodata/99a4ce3aa59de821307502915bd144d51e70bfc585a2d0154147c9e4398092ec-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.


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

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

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

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

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

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

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

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

MariaDB106: Check uncompressed DB failed
* 2024-06-07 03:09:18 (1983) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-07 03:09:18 (6579) [INFO] Running: /usr/bin/yum clean all
* 2024-06-07 03:09:18 (6580) [INFO] 
* 2024-06-07 03:09:18 (6593) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-07 03:09:18 (6593) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-06-07 03:09:18 (6593) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-06-07 03:09:18 (6593) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-07 03:09:18 (6593) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-06-07 03:09:18 (6593) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-06-07 03:09:18 (6593) [INFO]               : wp-toolkit-thirdparties
* 2024-06-07 03:09:18 (6593) [INFO] Cleaning up list of fastest mirrors
* 2024-06-07 03:09:18 (6610) [INFO] 
* 2024-06-07 03:09:49 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-07 03:09:49 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MyRBs9pXMS/ea_profile.json
* 2024-06-07 03:09:50 (5785) [INFO] Backed up EA4 profile to /tmp/MyRBs9pXMS/ea_profile.json
* 2024-06-07 03:09:53 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-07 03:09:53 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-08 03:09:04 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-08 03:09:04 (7829) [INFO] Script is up to date.
* 2024-06-08 03:09:05 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-08 03:09:05 (6580) [INFO] 
* 2024-06-08 03:09:07 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 3, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-08 03:09:07 (6610) [INFO] 
* 2024-06-08 03:09:09 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-08 03:09:23 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-08 03:09:23 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3ZEQyn4NPq/ea_profile.json
* 2024-06-08 03:09:24 (5785) [INFO] Backed up EA4 profile to /tmp/3ZEQyn4NPq/ea_profile.json
* 2024-06-08 03:09:26 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-08 03:09:26 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-09 03:09:14 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-09 03:09:14 (7829) [INFO] Script is up to date.
* 2024-06-09 03:09:15 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-09 03:09:15 (6580) [INFO] 
* 2024-06-09 03:09:17 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 3, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-09 03:09:18 (6610) [INFO] 
* 2024-06-09 03:09:19 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-09 03:09:33 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-09 03:09:33 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/J5lEEOgBlm/ea_profile.json
* 2024-06-09 03:09:34 (5785) [INFO] Backed up EA4 profile to /tmp/J5lEEOgBlm/ea_profile.json
* 2024-06-09 03:09:36 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-09 03:09:36 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-10 03:08:35 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-10 03:08:36 (7829) [INFO] Script is up to date.
* 2024-06-10 03:08:36 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-10 03:08:36 (6580) [INFO] 
* 2024-06-10 03:08:39 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-10 03:08:40 (6610) [INFO] 
* 2024-06-10 03:08:41 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-10 03:09:14 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-10 03:09:14 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cHQmMGNbk1/ea_profile.json
* 2024-06-10 03:09:15 (5785) [INFO] Backed up EA4 profile to /tmp/cHQmMGNbk1/ea_profile.json
* 2024-06-10 03:09:17 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-10 03:09:17 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-11 03:10:41 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-11 03:10:42 (7829) [INFO] Script is up to date.
* 2024-06-11 03:10:42 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-11 03:10:42 (6580) [INFO] 
* 2024-06-11 03:10:46 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-11 03:10:46 (6610) [INFO] 
* 2024-06-11 03:10:48 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-11 03:10:57 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-11 03:10:57 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Pv4nC_NH1d/ea_profile.json
* 2024-06-11 03:10:58 (5785) [INFO] Backed up EA4 profile to /tmp/Pv4nC_NH1d/ea_profile.json
* 2024-06-11 03:11:00 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-11 03:11:00 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-12 03:09:39 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-12 03:09:39 (7829) [INFO] Script is up to date.
* 2024-06-12 03:09:40 (6579) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-12 03:09:40 (6580) [INFO] 
* 2024-06-12 03:09:44 (6593) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-12 03:09:45 (6610) [INFO] 
* 2024-06-12 03:09:47 (2089) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-12 03:10:17 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-12 03:10:17 (5762) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DFpfzNswEJ/ea_profile.json
* 2024-06-12 03:10:18 (5785) [INFO] Backed up EA4 profile to /tmp/DFpfzNswEJ/ea_profile.json
* 2024-06-12 03:10:20 (2520) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-12 03:10:20 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-13 03:08:37 (7807) [INFO] Self-update of script version 40 requested.
* 2024-06-13 03:08:37 (7812) [INFO] Newer version of script found. Downloading.
* 2024-06-13 03:08:38 (7821) [INFO] Script update to version 41 successful.
* 2024-06-13 03:08:38 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-13 03:08:38 (6591) [INFO] 
* 2024-06-13 03:08:41 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-13 03:08:41 (6621) [INFO] 
* 2024-06-13 03:08:43 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-13 03:09:16 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-13 03:09:16 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ybo9pvHUjE/ea_profile.json
* 2024-06-13 03:09:17 (5796) [INFO] Backed up EA4 profile to /tmp/ybo9pvHUjE/ea_profile.json
* 2024-06-13 03:09:19 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-13 03:09:19 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-14 03:08:54 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-14 03:08:54 (7840) [INFO] Script is up to date.
* 2024-06-14 03:08:55 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-14 03:08:55 (6591) [INFO] 
* 2024-06-14 03:08:55 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-14 03:08:56 (6621) [INFO] 
* 2024-06-14 03:08:57 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-14 03:09:19 (1985) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.docker.com/linux/centos/7/x86_64/stable/repodata/aa1f3958af9cb5f1f6c34b5725f63de4f5e3e46c236205b598fecfec6ad506f6-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.hosteurope.de/mirror/centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://repo.imunify360.cloudlinux.com/defense360//el/7/updates/x86_64/repodata/3b4965f2156e8d04419e466a4f399d7dff3961c2b0d4cd45efb8421594c21854-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-1/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-2/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-3/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-4/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-5/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-6/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-7/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://download.imunify360.com/el/7/slot-8/x86_64/repodata/9e1fa9eafa1d6a7fa1c824e8dee832be6d72768247dcfa4fb83b51bb1d2b351e-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://asi-fs-d.contabo.net/centos/7/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.4.0/wp-toolkit/repodata/0f98e56cc8fb8b964589e668041481a56fe53251c3e3ce76e2114dafc81bd226-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
https://wp-toolkit.plesk.com/cPanel/CentOS-7-x86_64/6.4.0/thirdparty/repodata/22544a8db9133c23ce295c3fd232a1053810bf40817d18d8081c01c83b42293b-primary.sqlite.bz2: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rz.uni-frankfurt.de/pub/mirrors/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.plusline.net/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://de.mirrors.clouvider.net/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-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://mirror.softaculous.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.speedkom.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centosmirror.netcup.net/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://artfiles.org/centos.org/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.tu-chemnitz.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.mirrors.psw.services/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://centos.schlundtech.de/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.bio.lmu.de/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://centos.intergenia.de/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/extras/x86_64/repodata/e12dbf10e94bc2b33b1f45e026559bc8685728b139dddae0654d96bc624c5602-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.netzwerge.de/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.softaculous.com/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.23m.com/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://mirror.netcologne.de/centos/7.9.2009/updates/x86_64/repodata/f6151c2b03f43d0e2d8299b35d9ee7105ace1cec9c8678983a21ae2c73096a05-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://ftp.uni-bayreuth.de/linux/CentOS/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://mirror.checkdomain.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.antilo.de/pub/linux/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
http://ftp.rrzn.uni-hannover.de/centos/7.9.2009/os/x86_64/repodata/6d0c3a488c282fe537794b5946b01e28c7f44db79097bb06826e1c0c88bad5ef-primary.sqlite.bz2: [Errno 14] HTTP Error 416 - Requested Range Not Satisfiable
Trying other mirror.
* 2024-06-14 03:09:19 (1986) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-06-14 03:09:19 (6590) [INFO] Running: /usr/bin/yum clean all
* 2024-06-14 03:09:19 (6591) [INFO] 
* 2024-06-14 03:09:19 (6604) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-06-14 03:09:19 (6604) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-06-14 03:09:19 (6604) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-06-14 03:09:19 (6604) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-06-14 03:09:19 (6604) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-06-14 03:09:19 (6604) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-06-14 03:09:19 (6604) [INFO]               : wp-toolkit-thirdparties
* 2024-06-14 03:09:19 (6604) [INFO] Cleaning up list of fastest mirrors
* 2024-06-14 03:09:19 (6621) [INFO] 
* 2024-06-14 03:09:45 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-14 03:09:45 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ml310Sqe5i/ea_profile.json
* 2024-06-14 03:09:46 (5796) [INFO] Backed up EA4 profile to /tmp/Ml310Sqe5i/ea_profile.json
* 2024-06-14 03:09:49 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-14 03:09:49 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-15 03:09:15 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-15 03:09:15 (7840) [INFO] Script is up to date.
* 2024-06-15 03:09:16 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-15 03:09:16 (6591) [INFO] 
* 2024-06-15 03:09:19 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-15 03:09:19 (6621) [INFO] 
* 2024-06-15 03:09:21 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-15 03:09:36 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-15 03:09:36 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YqnVpOKPUC/ea_profile.json
* 2024-06-15 03:09:36 (5796) [INFO] Backed up EA4 profile to /tmp/YqnVpOKPUC/ea_profile.json
* 2024-06-15 03:09:39 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-15 03:09:39 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-16 03:09:13 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-16 03:09:13 (7840) [INFO] Script is up to date.
* 2024-06-16 03:09:14 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-16 03:09:14 (6591) [INFO] 
* 2024-06-16 03:09:16 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-16 03:09:16 (6621) [INFO] 
* 2024-06-16 03:09:18 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-16 03:09:36 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-16 03:09:36 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BPB1RizIAm/ea_profile.json
* 2024-06-16 03:09:37 (5796) [INFO] Backed up EA4 profile to /tmp/BPB1RizIAm/ea_profile.json
* 2024-06-16 03:09:40 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-16 03:09:40 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-17 03:08:37 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-17 03:08:37 (7840) [INFO] Script is up to date.
* 2024-06-17 03:08:38 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-17 03:08:38 (6591) [INFO] 
* 2024-06-17 03:08:41 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-17 03:08:42 (6621) [INFO] 
* 2024-06-17 03:08:44 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-17 03:09:12 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-17 03:09:12 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TU1YQC2EYA/ea_profile.json
* 2024-06-17 03:09:13 (5796) [INFO] Backed up EA4 profile to /tmp/TU1YQC2EYA/ea_profile.json
* 2024-06-17 03:09:15 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-17 03:09:15 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-18 03:08:34 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-18 03:08:34 (7840) [INFO] Script is up to date.
* 2024-06-18 03:08:35 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-18 03:08:35 (6591) [INFO] 
* 2024-06-18 03:08:37 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-18 03:08:38 (6621) [INFO] 
* 2024-06-18 03:08:39 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-18 03:09:07 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-18 03:09:07 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MMkQWayqNO/ea_profile.json
* 2024-06-18 03:09:08 (5796) [INFO] Backed up EA4 profile to /tmp/MMkQWayqNO/ea_profile.json
* 2024-06-18 03:09:10 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-18 03:09:10 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-19 03:08:34 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-19 03:08:34 (7840) [INFO] Script is up to date.
* 2024-06-19 03:08:35 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-19 03:08:35 (6591) [INFO] 
* 2024-06-19 03:08:38 (6604) [INFO] {"items": "7.12.4", "warnings": [], "version": "7.12.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-19 03:08:38 (6621) [INFO] 
* 2024-06-19 03:08:39 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-19 03:09:04 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-19 03:09:04 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e8iI336Pkr/ea_profile.json
* 2024-06-19 03:09:04 (5796) [INFO] Backed up EA4 profile to /tmp/e8iI336Pkr/ea_profile.json
* 2024-06-19 03:09:06 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-19 03:09:06 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-20 03:08:48 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-20 03:08:48 (7840) [INFO] Script is up to date.
* 2024-06-20 03:08:49 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-20 03:08:49 (6591) [INFO] 
* 2024-06-20 03:08:51 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-20 03:08:51 (6621) [INFO] 
* 2024-06-20 03:08:52 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-20 03:09:22 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-20 03:09:22 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Wih7Fj_DSs/ea_profile.json
* 2024-06-20 03:09:22 (5796) [INFO] Backed up EA4 profile to /tmp/Wih7Fj_DSs/ea_profile.json
* 2024-06-20 03:09:25 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-20 03:09:25 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-21 03:09:15 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-21 03:09:15 (7840) [INFO] Script is up to date.
* 2024-06-21 03:09:16 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-21 03:09:16 (6591) [INFO] 
* 2024-06-21 03:09:17 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-21 03:09:17 (6621) [INFO] 
* 2024-06-21 03:09:18 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-21 03:09:25 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-21 03:09:25 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LPraF8tS7_/ea_profile.json
* 2024-06-21 03:09:26 (5796) [INFO] Backed up EA4 profile to /tmp/LPraF8tS7_/ea_profile.json
* 2024-06-21 03:09:29 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-21 03:09:29 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-22 03:09:06 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-22 03:09:06 (7840) [INFO] Script is up to date.
* 2024-06-22 03:09:07 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-22 03:09:07 (6591) [INFO] 
* 2024-06-22 03:09:09 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-22 03:09:10 (6621) [INFO] 
* 2024-06-22 03:09:11 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-22 03:09:27 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-22 03:09:27 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fkPh_5EHSM/ea_profile.json
* 2024-06-22 03:09:28 (5796) [INFO] Backed up EA4 profile to /tmp/fkPh_5EHSM/ea_profile.json
* 2024-06-22 03:09:30 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-22 03:09:30 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-23 03:09:50 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-23 03:09:50 (7840) [INFO] Script is up to date.
* 2024-06-23 03:09:51 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-23 03:09:51 (6591) [INFO] 
* 2024-06-23 03:09:52 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-23 03:09:52 (6621) [INFO] 
* 2024-06-23 03:09:53 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-23 03:10:19 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-23 03:10:19 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PHnuysF6ht/ea_profile.json
* 2024-06-23 03:10:20 (5796) [INFO] Backed up EA4 profile to /tmp/PHnuysF6ht/ea_profile.json
* 2024-06-23 03:10:22 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-23 03:10:22 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-24 03:08:33 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-24 03:08:33 (7840) [INFO] Script is up to date.
* 2024-06-24 03:08:34 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-24 03:08:34 (6591) [INFO] 
* 2024-06-24 03:08:36 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-24 03:08:36 (6621) [INFO] 
* 2024-06-24 03:08:38 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-24 03:09:05 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-24 03:09:05 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/a6C3bLddpN/ea_profile.json
* 2024-06-24 03:09:05 (5796) [INFO] Backed up EA4 profile to /tmp/a6C3bLddpN/ea_profile.json
* 2024-06-24 03:09:08 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-24 03:09:08 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-25 03:08:46 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-25 03:08:46 (7840) [INFO] Script is up to date.
* 2024-06-25 03:08:47 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-25 03:08:47 (6591) [INFO] 
* 2024-06-25 03:08:50 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-25 03:08:50 (6621) [INFO] 
* 2024-06-25 03:08:51 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-25 03:09:21 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-25 03:09:21 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zyRy1X56QB/ea_profile.json
* 2024-06-25 03:09:22 (5796) [INFO] Backed up EA4 profile to /tmp/zyRy1X56QB/ea_profile.json
* 2024-06-25 03:09:24 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-25 03:09:24 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-26 03:09:01 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-26 03:09:01 (7840) [INFO] Script is up to date.
* 2024-06-26 03:09:01 (6590) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-26 03:09:01 (6591) [INFO] 
* 2024-06-26 03:09:05 (6604) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-26 03:09:05 (6621) [INFO] 
* 2024-06-26 03:09:06 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-26 03:09:21 (1042) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-26 03:09:21 (5773) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_t3CxdVbZ8/ea_profile.json
* 2024-06-26 03:09:22 (5796) [INFO] Backed up EA4 profile to /tmp/_t3CxdVbZ8/ea_profile.json
* 2024-06-26 03:09:24 (2531) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-26 03:09:24 (317) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-27 03:08:33 (7818) [INFO] Self-update of script version 41 requested.
* 2024-06-27 03:08:33 (7823) [INFO] Newer version of script found. Downloading.
* 2024-06-27 03:08:33 (7832) [INFO] Script update to version 43 successful.
* 2024-06-27 03:08:34 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-27 03:08:34 (6738) [INFO] 
* 2024-06-27 03:08:36 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-27 03:08:36 (6768) [INFO] 
* 2024-06-27 03:08:38 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-27 03:09:05 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-27 03:09:05 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SWTytlsqKZ/ea_profile.json
* 2024-06-27 03:09:06 (5904) [INFO] Backed up EA4 profile to /tmp/SWTytlsqKZ/ea_profile.json
* 2024-06-27 03:09:08 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-27 03:09:08 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-28 03:08:41 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-28 03:08:42 (7994) [INFO] Script is up to date.
* 2024-06-28 03:08:42 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-28 03:08:42 (6738) [INFO] 
* 2024-06-28 03:08:45 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-28 03:08:45 (6768) [INFO] 
* 2024-06-28 03:08:47 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-28 03:09:14 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-28 03:09:15 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Nb9d96pTSJ/ea_profile.json
* 2024-06-28 03:09:16 (5904) [INFO] Backed up EA4 profile to /tmp/Nb9d96pTSJ/ea_profile.json
* 2024-06-28 03:09:18 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-28 03:09:18 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-29 03:09:04 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-29 03:09:04 (7994) [INFO] Script is up to date.
* 2024-06-29 03:09:05 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-29 03:09:05 (6738) [INFO] 
* 2024-06-29 03:09:07 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-29 03:09:07 (6768) [INFO] 
* 2024-06-29 03:09:09 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-29 03:09:23 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-29 03:09:24 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hnRPnPTqRM/ea_profile.json
* 2024-06-29 03:09:24 (5904) [INFO] Backed up EA4 profile to /tmp/hnRPnPTqRM/ea_profile.json
* 2024-06-29 03:09:26 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-29 03:09:26 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-06-30 03:09:08 (7972) [INFO] Self-update of script version 43 requested.
* 2024-06-30 03:09:08 (7994) [INFO] Script is up to date.
* 2024-06-30 03:09:09 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-06-30 03:09:09 (6738) [INFO] 
* 2024-06-30 03:09:11 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-06-30 03:09:12 (6768) [INFO] 
* 2024-06-30 03:09:13 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-06-30 03:09:28 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-06-30 03:09:28 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/njmly5bCPD/ea_profile.json
* 2024-06-30 03:09:29 (5904) [INFO] Backed up EA4 profile to /tmp/njmly5bCPD/ea_profile.json
* 2024-06-30 03:09:31 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-06-30 03:09:31 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-01 03:08:35 (7972) [INFO] Self-update of script version 43 requested.
* 2024-07-01 03:08:35 (7994) [INFO] Script is up to date.
* 2024-07-01 03:08:36 (6737) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-01 03:08:36 (6738) [INFO] 
* 2024-07-01 03:08:37 (6751) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-01 03:08:38 (6768) [INFO] 
* 2024-07-01 03:08:39 (2100) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-01 03:09:04 (1045) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-01 03:09:05 (5881) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3BHlyk6Myw/ea_profile.json
* 2024-07-01 03:09:05 (5904) [INFO] Backed up EA4 profile to /tmp/3BHlyk6Myw/ea_profile.json
* 2024-07-01 03:09:08 (2532) [WARN] Elevating with Sectigo as the provider for AutoSSL is not supported.
If you proceed with this upgrade, we will switch your system
to use the Let's Encrypt™ provider.

* 2024-07-01 03:09:08 (320) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-02 03:09:19 (7972) [INFO] Self-update of script version 43 requested.
* 2024-07-02 03:09:19 (7977) [INFO] Newer version of script found. Downloading.
* 2024-07-02 03:09:20 (7986) [INFO] Script update to version 44 successful.
* 2024-07-02 03:09:20 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-02 03:09:20 (6800) [INFO] 
* 2024-07-02 03:09:22 (6813) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-02 03:09:22 (6830) [INFO] 
* 2024-07-02 03:09:24 (2101) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-02 03:09:28 (1986) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-02 03:09:28 (1987) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-02 03:09:28 (6799) [INFO] Running: /usr/bin/yum clean all
* 2024-07-02 03:09:28 (6800) [INFO] 
* 2024-07-02 03:09:28 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-02 03:09:28 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-02 03:09:28 (6813) [INFO]               : docker-ce-stable extras imunify360 imunify360-rollout-1
* 2024-07-02 03:09:28 (6813) [INFO]               : imunify360-rollout-2 imunify360-rollout-3 imunify360-rollout-4
* 2024-07-02 03:09:28 (6813) [INFO]               : imunify360-rollout-5 imunify360-rollout-6 imunify360-rollout-7
* 2024-07-02 03:09:28 (6813) [INFO]               : imunify360-rollout-8 updates wp-toolkit-cpanel
* 2024-07-02 03:09:28 (6813) [INFO]               : wp-toolkit-thirdparties
* 2024-07-02 03:09:28 (6813) [INFO] Cleaning up list of fastest mirrors
* 2024-07-02 03:09:28 (6830) [INFO] 
* 2024-07-02 03:09:30 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-02 03:09:30 (1997) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-02 03:09:30 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-02 03:09:31 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QUnVl2GpE_/ea_profile.json
* 2024-07-02 03:09:33 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QUnVl2GpE_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-02 03:09:33 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-03 03:08:32 (8035) [INFO] Self-update of script version 44 requested.
* 2024-07-03 03:08:33 (8057) [INFO] Script is up to date.
* 2024-07-03 03:08:33 (6799) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-03 03:08:33 (6800) [INFO] 
* 2024-07-03 03:08:35 (6813) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-03 03:08:35 (6830) [INFO] 
* 2024-07-03 03:08:37 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 03:08:37 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 03:08:37 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 03:08:37 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 03:08:37 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 03:08:37 (2123) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-03 03:08:37 (2101) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-03 03:08:40 (1986) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-03 03:08:40 (1987) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-03 03:08:40 (6799) [INFO] Running: /usr/bin/yum clean all
* 2024-07-03 03:08:40 (6800) [INFO] 
* 2024-07-03 03:08:40 (6813) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-03 03:08:40 (6813) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-03 03:08:40 (6813) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-03 03:08:40 (6813) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-03 03:08:40 (6813) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-03 03:08:40 (6813) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-03 03:08:40 (6813) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-03 03:08:40 (6813) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-03 03:08:40 (6813) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-03 03:08:40 (6813) [INFO] Cleaning up list of fastest mirrors
* 2024-07-03 03:08:40 (6830) [INFO] 
* 2024-07-03 03:08:43 (1996) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-03 03:08:43 (1997) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-03 03:08:43 (1046) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-03 03:08:44 (5943) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LcHZl7UL8B/ea_profile.json
* 2024-07-03 03:08:47 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LcHZl7UL8B/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5945.
* 2024-07-03 03:08:47 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-04 03:08:31 (8035) [INFO] Self-update of script version 44 requested.
* 2024-07-04 03:08:32 (8040) [INFO] Newer version of script found. Downloading.
* 2024-07-04 03:08:32 (8049) [INFO] Script update to version 45 successful.
* 2024-07-04 03:08:33 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-04 03:08:33 (6814) [INFO] 
* 2024-07-04 03:08:36 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-04 03:08:36 (6844) [INFO] 
* 2024-07-04 03:08:38 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 03:08:38 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 03:08:38 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 03:08:38 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 03:08:38 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 03:08:38 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-04 03:08:38 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-04 03:08:40 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-04 03:08:40 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-04 03:08:40 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-04 03:08:40 (6814) [INFO] 
* 2024-07-04 03:08:40 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-04 03:08:40 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-04 03:08:40 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-04 03:08:40 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-04 03:08:40 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-04 03:08:40 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-04 03:08:40 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-04 03:08:40 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-04 03:08:40 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-04 03:08:40 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-04 03:08:40 (6844) [INFO] 
* 2024-07-04 03:08:42 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-04 03:08:42 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-04 03:08:43 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-04 03:08:43 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WLwi9QgACH/ea_profile.json
* 2024-07-04 03:08:45 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WLwi9QgACH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-04 03:08:45 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-05 03:08:35 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-05 03:08:35 (8071) [INFO] Script is up to date.
* 2024-07-05 03:08:36 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-05 03:08:36 (6814) [INFO] 
* 2024-07-05 03:08:39 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-05 03:08:39 (6844) [INFO] 
* 2024-07-05 03:08:41 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 03:08:41 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 03:08:41 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 03:08:41 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 03:08:41 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 03:08:41 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-05 03:08:41 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-05 03:08:44 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-05 03:08:44 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-05 03:08:44 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-05 03:08:44 (6814) [INFO] 
* 2024-07-05 03:08:44 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-05 03:08:44 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-05 03:08:44 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-05 03:08:44 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-05 03:08:44 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-05 03:08:44 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-05 03:08:44 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-05 03:08:44 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-05 03:08:44 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-05 03:08:44 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-05 03:08:44 (6844) [INFO] 
* 2024-07-05 03:08:47 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-05 03:08:47 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-05 03:08:48 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-05 03:08:48 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hx7j_5pctC/ea_profile.json
* 2024-07-05 03:08:50 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hx7j_5pctC/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-05 03:08:50 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-06 03:09:04 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-06 03:09:04 (8071) [INFO] Script is up to date.
* 2024-07-06 03:09:05 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-06 03:09:05 (6814) [INFO] 
* 2024-07-06 03:09:08 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-06 03:09:08 (6844) [INFO] 
* 2024-07-06 03:09:10 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 03:09:10 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 03:09:10 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 03:09:10 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 03:09:10 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 03:09:10 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-06 03:09:10 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-06 03:09:12 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-06 03:09:12 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-06 03:09:12 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-06 03:09:12 (6814) [INFO] 
* 2024-07-06 03:09:12 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-06 03:09:12 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-06 03:09:12 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-06 03:09:12 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-06 03:09:12 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-06 03:09:12 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-06 03:09:12 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-06 03:09:12 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-06 03:09:12 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-06 03:09:12 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-06 03:09:12 (6844) [INFO] 
* 2024-07-06 03:09:15 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-06 03:09:15 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-06 03:09:15 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-06 03:09:16 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NObZ0qt8tL/ea_profile.json
* 2024-07-06 03:09:18 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NObZ0qt8tL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-06 03:09:18 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-07 03:09:09 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-07 03:09:09 (8071) [INFO] Script is up to date.
* 2024-07-07 03:09:10 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-07 03:09:10 (6814) [INFO] 
* 2024-07-07 03:09:13 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-07 03:09:13 (6844) [INFO] 
* 2024-07-07 03:09:15 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 03:09:15 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 03:09:15 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 03:09:15 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 03:09:15 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 03:09:15 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-07 03:09:15 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-07 03:09:17 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-07 03:09:17 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-07 03:09:17 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-07 03:09:17 (6814) [INFO] 
* 2024-07-07 03:09:17 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-07 03:09:17 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-07 03:09:17 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-07 03:09:17 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-07 03:09:17 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-07 03:09:17 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-07 03:09:17 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-07 03:09:17 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-07 03:09:17 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-07 03:09:17 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-07 03:09:17 (6844) [INFO] 
* 2024-07-07 03:09:20 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-07 03:09:20 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-07 03:09:20 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-07 03:09:21 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Zbjqq86vh1/ea_profile.json
* 2024-07-07 03:09:22 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Zbjqq86vh1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-07 03:09:22 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-08 03:08:31 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-08 03:08:31 (8071) [INFO] Script is up to date.
* 2024-07-08 03:08:32 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-08 03:08:32 (6814) [INFO] 
* 2024-07-08 03:08:34 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-08 03:08:34 (6844) [INFO] 
* 2024-07-08 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-08 03:08:35 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-08 03:08:38 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-08 03:08:38 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-08 03:08:38 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-08 03:08:38 (6814) [INFO] 
* 2024-07-08 03:08:38 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-08 03:08:38 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-08 03:08:38 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-08 03:08:38 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-08 03:08:38 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-08 03:08:38 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-08 03:08:38 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-08 03:08:38 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-08 03:08:38 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-08 03:08:38 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-08 03:08:39 (6844) [INFO] 
* 2024-07-08 03:08:42 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-08 03:08:42 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-08 03:08:42 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-08 03:08:42 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WNiACqF8Qp/ea_profile.json
* 2024-07-08 03:08:44 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/WNiACqF8Qp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-08 03:08:44 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-09 03:08:34 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-09 03:08:34 (8071) [INFO] Script is up to date.
* 2024-07-09 03:08:35 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-09 03:08:35 (6814) [INFO] 
* 2024-07-09 03:08:37 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-09 03:08:37 (6844) [INFO] 
* 2024-07-09 03:08:39 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 03:08:39 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 03:08:39 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 03:08:39 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 03:08:39 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 03:08:39 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-09 03:08:39 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-09 03:08:42 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-09 03:08:42 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-09 03:08:42 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-09 03:08:42 (6814) [INFO] 
* 2024-07-09 03:08:43 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-09 03:08:43 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-09 03:08:43 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-09 03:08:43 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-09 03:08:43 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-09 03:08:43 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-09 03:08:43 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-09 03:08:43 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-09 03:08:43 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-09 03:08:43 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-09 03:08:43 (6844) [INFO] 
* 2024-07-09 03:08:46 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-09 03:08:46 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-09 03:08:46 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-09 03:08:47 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dRv92N_Xhy/ea_profile.json
* 2024-07-09 03:08:49 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dRv92N_Xhy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-09 03:08:49 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-10 03:08:30 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-10 03:08:30 (8071) [INFO] Script is up to date.
* 2024-07-10 03:08:31 (6813) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-10 03:08:31 (6814) [INFO] 
* 2024-07-10 03:08:33 (6827) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-10 03:08:33 (6844) [INFO] 
* 2024-07-10 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-1' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-2' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-3' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-4' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-5' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 03:08:35 (2136) [INFO] Unsupported YUM repo enabled 'centos7els-rollout-6' without packages installed from /etc/yum.repos.d/centos7-els-rollout.repo, these will be disabled before ELevation
* 2024-07-10 03:08:35 (2114) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-10 03:08:37 (1999) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-10 03:08:37 (2000) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-10 03:08:37 (6813) [INFO] Running: /usr/bin/yum clean all
* 2024-07-10 03:08:37 (6814) [INFO] 
* 2024-07-10 03:08:38 (6827) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-10 03:08:38 (6827) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-10 03:08:38 (6827) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-10 03:08:38 (6827) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-10 03:08:38 (6827) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-10 03:08:38 (6827) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-10 03:08:38 (6827) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-10 03:08:38 (6827) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-10 03:08:38 (6827) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-10 03:08:38 (6827) [INFO] Cleaning up list of fastest mirrors
* 2024-07-10 03:08:38 (6844) [INFO] 
* 2024-07-10 03:08:40 (2009) [ERROR] yum appears to be unstable. Please address this before upgrading
* 2024-07-10 03:08:40 (2010) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-10 03:08:41 (1059) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-10 03:08:41 (5957) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9sRWmc6f1k/ea_profile.json
* 2024-07-10 03:08:43 (357) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9sRWmc6f1k/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5959.
* 2024-07-10 03:08:43 (321) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-11 03:08:33 (8049) [INFO] Self-update of script version 45 requested.
* 2024-07-11 03:08:33 (8054) [INFO] Newer version of script found. Downloading.
* 2024-07-11 03:08:34 (8063) [INFO] Script update to version 46 successful.
* 2024-07-11 03:08:34 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-11 03:08:34 (6847) [INFO] 
* 2024-07-11 03:08:38 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-11 03:08:38 (6877) [INFO] 
* 2024-07-11 03:08:38 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-11 03:08:38 (6847) [INFO] 
* 2024-07-11 03:08:41 (6877) [INFO] 
* 2024-07-11 03:08:42 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-11 03:08:44 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-11 03:08:44 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-11 03:08:44 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-11 03:08:44 (6847) [INFO] 
* 2024-07-11 03:08:44 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-11 03:08:44 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-11 03:08:44 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-11 03:08:44 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-11 03:08:44 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-11 03:08:44 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-11 03:08:44 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-11 03:08:44 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-11 03:08:44 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-11 03:08:44 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-11 03:08:44 (6877) [INFO] 
* 2024-07-11 03:08:48 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-11 03:08:48 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-11 03:08:48 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-11 03:08:48 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vm9KEA9a8t/ea_profile.json
* 2024-07-11 03:08:50 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/vm9KEA9a8t/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-11 03:08:50 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-12 03:08:31 (8126) [INFO] Self-update of script version 46 requested.
* 2024-07-12 03:08:31 (8131) [INFO] Newer version of script found. Downloading.
* 2024-07-12 03:08:32 (8140) [INFO] Script update to version 47 successful.
* 2024-07-12 03:08:33 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-12 03:08:33 (6849) [INFO] 
* 2024-07-12 03:08:33 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-12 03:08:33 (6879) [INFO] 
* 2024-07-12 03:08:34 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-12 03:08:34 (6849) [INFO] 
* 2024-07-12 03:08:37 (6879) [INFO] 
* 2024-07-12 03:08:38 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-12 03:08:40 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-12 03:08:40 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-12 03:08:40 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-12 03:08:40 (6849) [INFO] 
* 2024-07-12 03:08:40 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-12 03:08:40 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-12 03:08:40 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-12 03:08:40 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-12 03:08:40 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-12 03:08:40 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-12 03:08:40 (6862) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-12 03:08:40 (6862) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-12 03:08:40 (6862) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-12 03:08:40 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-12 03:08:40 (6879) [INFO] 
* 2024-07-12 03:08:43 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-12 03:08:43 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-12 03:08:43 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-12 03:08:44 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Km7347ZmCt/ea_profile.json
* 2024-07-12 03:08:46 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Km7347ZmCt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-12 03:08:46 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-13 03:09:03 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-13 03:09:03 (8150) [INFO] Script is up to date.
* 2024-07-13 03:09:04 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-13 03:09:04 (6849) [INFO] 
* 2024-07-13 03:09:06 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-13 03:09:06 (6879) [INFO] 
* 2024-07-13 03:09:07 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-13 03:09:07 (6849) [INFO] 
* 2024-07-13 03:09:08 (6879) [INFO] 
* 2024-07-13 03:09:10 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-13 03:09:11 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-13 03:09:11 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-13 03:09:11 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-13 03:09:11 (6849) [INFO] 
* 2024-07-13 03:09:11 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-13 03:09:11 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-13 03:09:11 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-13 03:09:11 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-13 03:09:11 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-13 03:09:11 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-13 03:09:11 (6862) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-13 03:09:11 (6862) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-13 03:09:11 (6862) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-13 03:09:11 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-13 03:09:11 (6879) [INFO] 
* 2024-07-13 03:09:14 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-13 03:09:14 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-13 03:09:14 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-13 03:09:15 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lxRh9LB970/ea_profile.json
* 2024-07-13 03:09:17 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lxRh9LB970/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-13 03:09:17 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-14 03:09:04 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-14 03:09:04 (8150) [INFO] Script is up to date.
* 2024-07-14 03:09:05 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-14 03:09:05 (6849) [INFO] 
* 2024-07-14 03:09:08 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-14 03:09:08 (6879) [INFO] 
* 2024-07-14 03:09:09 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-14 03:09:09 (6849) [INFO] 
* 2024-07-14 03:09:10 (6879) [INFO] 
* 2024-07-14 03:09:12 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-14 03:09:13 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-14 03:09:13 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-14 03:09:13 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-14 03:09:13 (6849) [INFO] 
* 2024-07-14 03:09:13 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-14 03:09:13 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-14 03:09:13 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-14 03:09:13 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-14 03:09:13 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-14 03:09:13 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-14 03:09:13 (6862) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-14 03:09:13 (6862) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-14 03:09:13 (6862) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-14 03:09:13 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-14 03:09:13 (6879) [INFO] 
* 2024-07-14 03:09:16 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-14 03:09:16 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-14 03:09:17 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-14 03:09:17 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fSXfo2HZ6Z/ea_profile.json
* 2024-07-14 03:09:19 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fSXfo2HZ6Z/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-14 03:09:19 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-15 03:08:44 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-15 03:08:44 (8150) [INFO] Script is up to date.
* 2024-07-15 03:08:45 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-15 03:08:45 (6849) [INFO] 
* 2024-07-15 03:08:45 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-15 03:08:46 (6879) [INFO] 
* 2024-07-15 03:08:46 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-15 03:08:46 (6849) [INFO] 
* 2024-07-15 03:08:49 (6879) [INFO] 
* 2024-07-15 03:08:51 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-15 03:08:53 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-15 03:08:53 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-15 03:08:53 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-15 03:08:53 (6849) [INFO] 
* 2024-07-15 03:08:53 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-15 03:08:53 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-15 03:08:53 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-15 03:08:53 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-15 03:08:53 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-15 03:08:53 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-15 03:08:53 (6862) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-15 03:08:53 (6862) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-15 03:08:53 (6862) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-15 03:08:53 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-15 03:08:53 (6879) [INFO] 
* 2024-07-15 03:08:56 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-15 03:08:56 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-15 03:08:56 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-15 03:08:57 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y86UF16WM1/ea_profile.json
* 2024-07-15 03:08:59 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y86UF16WM1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-15 03:08:59 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-16 03:08:40 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-16 03:08:40 (8150) [INFO] Script is up to date.
* 2024-07-16 03:08:41 (6848) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-16 03:08:41 (6849) [INFO] 
* 2024-07-16 03:08:44 (6862) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-16 03:08:44 (6879) [INFO] 
* 2024-07-16 03:08:45 (6848) [INFO] Running: /usr/bin/yum list extras
* 2024-07-16 03:08:45 (6849) [INFO] 
* 2024-07-16 03:08:47 (6879) [INFO] 
* 2024-07-16 03:08:49 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-16 03:08:50 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-16 03:08:50 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-16 03:08:50 (6848) [INFO] Running: /usr/bin/yum clean all
* 2024-07-16 03:08:50 (6849) [INFO] 
* 2024-07-16 03:08:50 (6862) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-16 03:08:50 (6862) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-16 03:08:50 (6862) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-16 03:08:50 (6862) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-16 03:08:50 (6862) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-16 03:08:50 (6862) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-16 03:08:50 (6862) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-16 03:08:50 (6862) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-16 03:08:50 (6862) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-16 03:08:50 (6862) [INFO] Cleaning up list of fastest mirrors
* 2024-07-16 03:08:50 (6879) [INFO] 
* 2024-07-16 03:08:54 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-16 03:08:54 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-16 03:08:54 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-16 03:08:55 (5990) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8y209hGKv4/ea_profile.json
* 2024-07-16 03:08:56 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8y209hGKv4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5992.
* 2024-07-16 03:08:56 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-17 03:08:54 (8128) [INFO] Self-update of script version 47 requested.
* 2024-07-17 03:08:54 (8133) [INFO] Newer version of script found. Downloading.
* 2024-07-17 03:08:55 (8142) [INFO] Script update to version 48 successful.
* 2024-07-17 03:08:56 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-17 03:08:56 (6847) [INFO] 
* 2024-07-17 03:09:00 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-17 03:09:01 (6877) [INFO] 
* 2024-07-17 03:09:01 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-17 03:09:01 (6847) [INFO] 
* 2024-07-17 03:09:06 (6877) [INFO] 
* 2024-07-17 03:09:08 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-17 03:09:10 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-17 03:09:10 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-17 03:09:10 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-17 03:09:10 (6847) [INFO] 
* 2024-07-17 03:09:10 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-17 03:09:10 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-17 03:09:10 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-17 03:09:10 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-17 03:09:10 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-17 03:09:10 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-17 03:09:10 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-17 03:09:10 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-17 03:09:10 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-17 03:09:10 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-17 03:09:10 (6877) [INFO] 
* 2024-07-17 03:09:12 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-17 03:09:12 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-17 03:09:13 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-17 03:09:14 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4e5W8zO0Di/ea_profile.json
* 2024-07-17 03:09:16 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4e5W8zO0Di/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-17 03:09:16 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-18 03:08:50 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-18 03:08:51 (8148) [INFO] Script is up to date.
* 2024-07-18 03:08:52 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-18 03:08:52 (6847) [INFO] 
* 2024-07-18 03:09:05 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-18 03:09:05 (6877) [INFO] 
* 2024-07-18 03:09:06 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-18 03:09:06 (6847) [INFO] 
* 2024-07-18 03:09:08 (6877) [INFO] 
* 2024-07-18 03:09:11 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-18 03:09:12 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-18 03:09:12 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-18 03:09:12 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-18 03:09:12 (6847) [INFO] 
* 2024-07-18 03:09:12 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-18 03:09:12 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-18 03:09:12 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-18 03:09:12 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-18 03:09:12 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-18 03:09:12 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-18 03:09:12 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-18 03:09:12 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-18 03:09:12 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-18 03:09:12 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-18 03:09:12 (6877) [INFO] 
* 2024-07-18 03:09:14 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-18 03:09:14 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-18 03:09:15 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-18 03:09:15 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pmahbrL1bz/ea_profile.json
* 2024-07-18 03:09:17 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pmahbrL1bz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-18 03:09:17 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-19 03:09:32 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-19 03:09:33 (8148) [INFO] Script is up to date.
* 2024-07-19 03:09:34 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-19 03:09:34 (6847) [INFO] 
* 2024-07-19 03:09:40 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-19 03:09:40 (6877) [INFO] 
* 2024-07-19 03:09:42 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-19 03:09:42 (6847) [INFO] 
* 2024-07-19 03:09:44 (6877) [INFO] 
* 2024-07-19 03:09:49 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-19 03:09:51 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-19 03:09:51 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-19 03:09:51 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-19 03:09:51 (6847) [INFO] 
* 2024-07-19 03:09:51 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-19 03:09:52 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-19 03:09:52 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-19 03:09:52 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-19 03:09:52 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-19 03:09:52 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-19 03:09:52 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-19 03:09:52 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-19 03:09:52 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-19 03:09:52 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-19 03:09:52 (6877) [INFO] 
* 2024-07-19 03:09:55 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-19 03:09:55 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-19 03:09:55 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-19 03:09:56 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FE8tl3dWOG/ea_profile.json
* 2024-07-19 03:09:59 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FE8tl3dWOG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-19 03:09:59 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-20 03:11:02 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-20 03:11:02 (8148) [INFO] Script is up to date.
* 2024-07-20 03:11:04 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-20 03:11:04 (6847) [INFO] 
* 2024-07-20 03:11:09 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-20 03:11:09 (6877) [INFO] 
* 2024-07-20 03:11:10 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-20 03:11:10 (6847) [INFO] 
* 2024-07-20 03:11:12 (6877) [INFO] 
* 2024-07-20 03:11:17 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-20 03:11:20 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-20 03:11:20 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-20 03:11:20 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-20 03:11:20 (6847) [INFO] 
* 2024-07-20 03:11:21 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-20 03:11:21 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-20 03:11:21 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-20 03:11:21 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-20 03:11:21 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-20 03:11:21 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-20 03:11:21 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-20 03:11:21 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-20 03:11:21 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-20 03:11:21 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-20 03:11:21 (6877) [INFO] 
* 2024-07-20 03:11:23 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-20 03:11:23 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-20 03:11:24 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-20 03:11:25 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KVOGL0nARp/ea_profile.json
* 2024-07-20 03:11:29 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KVOGL0nARp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-20 03:11:29 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-21 03:11:14 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-21 03:11:14 (8148) [INFO] Script is up to date.
* 2024-07-21 03:11:16 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-21 03:11:16 (6847) [INFO] 
* 2024-07-21 03:11:24 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-21 03:11:25 (6877) [INFO] 
* 2024-07-21 03:11:26 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-21 03:11:26 (6847) [INFO] 
* 2024-07-21 03:11:28 (6877) [INFO] 
* 2024-07-21 03:11:33 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-21 03:11:35 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-21 03:11:35 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-21 03:11:35 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-21 03:11:35 (6847) [INFO] 
* 2024-07-21 03:11:36 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-21 03:11:36 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-21 03:11:36 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-21 03:11:36 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-21 03:11:36 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-21 03:11:36 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-21 03:11:36 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-21 03:11:36 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-21 03:11:36 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-21 03:11:36 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-21 03:11:36 (6877) [INFO] 
* 2024-07-21 03:11:39 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-21 03:11:39 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-21 03:11:40 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-21 03:11:41 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F5Ysqajbk5/ea_profile.json
* 2024-07-21 03:11:47 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/F5Ysqajbk5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-21 03:11:47 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-22 03:09:29 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-22 03:09:29 (8148) [INFO] Script is up to date.
* 2024-07-22 03:09:31 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-22 03:09:31 (6847) [INFO] 
* 2024-07-22 03:09:37 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-22 03:09:37 (6877) [INFO] 
* 2024-07-22 03:09:39 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-22 03:09:39 (6847) [INFO] 
* 2024-07-22 03:09:42 (6877) [INFO] 
* 2024-07-22 03:09:46 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-22 03:09:48 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-22 03:09:48 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-22 03:09:48 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-22 03:09:48 (6847) [INFO] 
* 2024-07-22 03:09:49 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-22 03:09:49 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-22 03:09:49 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-22 03:09:49 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-22 03:09:49 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-22 03:09:49 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-22 03:09:49 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-22 03:09:49 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-22 03:09:49 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-22 03:09:49 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-22 03:09:49 (6877) [INFO] 
* 2024-07-22 03:09:53 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-22 03:09:53 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-22 03:09:53 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-22 03:09:56 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fs2e90HBLQ/ea_profile.json
* 2024-07-22 03:09:59 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fs2e90HBLQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-22 03:09:59 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-23 03:09:31 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-23 03:09:31 (8148) [INFO] Script is up to date.
* 2024-07-23 03:09:35 (6846) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-23 03:09:35 (6847) [INFO] 
* 2024-07-23 03:09:43 (6860) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-23 03:09:44 (6877) [INFO] 
* 2024-07-23 03:09:45 (6846) [INFO] Running: /usr/bin/yum list extras
* 2024-07-23 03:09:45 (6847) [INFO] 
* 2024-07-23 03:09:47 (6877) [INFO] 
* 2024-07-23 03:09:51 (2139) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-23 03:09:53 (2025) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-23 03:09:53 (2026) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-23 03:09:53 (6846) [INFO] Running: /usr/bin/yum clean all
* 2024-07-23 03:09:53 (6847) [INFO] 
* 2024-07-23 03:09:53 (6860) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-23 03:09:53 (6860) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-23 03:09:53 (6860) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-23 03:09:53 (6860) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-23 03:09:53 (6860) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-23 03:09:53 (6860) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-23 03:09:53 (6860) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-23 03:09:53 (6860) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-23 03:09:53 (6860) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-23 03:09:53 (6860) [INFO] Cleaning up list of fastest mirrors
* 2024-07-23 03:09:53 (6877) [INFO] 
* 2024-07-23 03:09:56 (2035) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-23 03:09:56 (2036) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-23 03:09:57 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-23 03:10:00 (5988) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qf0RUBO6sT/ea_profile.json
* 2024-07-23 03:10:02 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qf0RUBO6sT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 5990.
* 2024-07-23 03:10:02 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-24 03:09:33 (8126) [INFO] Self-update of script version 48 requested.
* 2024-07-24 03:09:33 (8131) [INFO] Newer version of script found. Downloading.
* 2024-07-24 03:09:34 (8140) [INFO] Script update to version 49 successful.
* 2024-07-24 03:09:36 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-24 03:09:36 (6908) [INFO] 
* 2024-07-24 03:09:43 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-24 03:09:43 (6938) [INFO] 
* 2024-07-24 03:09:45 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-24 03:09:45 (6908) [INFO] 
* 2024-07-24 03:09:47 (6938) [INFO] 
* 2024-07-24 03:09:52 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-24 03:09:52 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-24 03:09:54 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-24 03:09:54 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-24 03:09:54 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-24 03:09:54 (6908) [INFO] 
* 2024-07-24 03:09:54 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-24 03:09:55 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-24 03:09:55 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-24 03:09:55 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-24 03:09:55 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-24 03:09:55 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-24 03:09:55 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-24 03:09:55 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-24 03:09:55 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-24 03:09:55 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-24 03:09:55 (6938) [INFO] 
* 2024-07-24 03:09:57 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-24 03:09:57 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-24 03:09:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-24 03:09:59 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/THA9ZEIGEE/ea_profile.json
* 2024-07-24 03:10:02 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/THA9ZEIGEE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-24 03:10:02 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-25 03:09:41 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-25 03:09:42 (8209) [INFO] Script is up to date.
* 2024-07-25 03:09:44 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-25 03:09:44 (6908) [INFO] 
* 2024-07-25 03:09:53 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-25 03:09:53 (6938) [INFO] 
* 2024-07-25 03:09:54 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-25 03:09:54 (6908) [INFO] 
* 2024-07-25 03:09:57 (6938) [INFO] 
* 2024-07-25 03:10:02 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-25 03:10:02 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-25 03:10:04 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-25 03:10:04 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-25 03:10:04 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-25 03:10:04 (6908) [INFO] 
* 2024-07-25 03:10:05 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-25 03:10:05 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-25 03:10:05 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-25 03:10:05 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-25 03:10:05 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-25 03:10:05 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-25 03:10:05 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-25 03:10:05 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-25 03:10:05 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-25 03:10:05 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-25 03:10:05 (6938) [INFO] 
* 2024-07-25 03:10:09 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-25 03:10:09 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-25 03:10:10 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-25 03:10:11 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_qFAbTWkeK/ea_profile.json
* 2024-07-25 03:10:15 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_qFAbTWkeK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-25 03:10:15 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-26 03:09:32 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-26 03:09:32 (8209) [INFO] Script is up to date.
* 2024-07-26 03:09:34 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-26 03:09:34 (6908) [INFO] 
* 2024-07-26 03:09:39 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-26 03:09:40 (6938) [INFO] 
* 2024-07-26 03:09:42 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-26 03:09:42 (6908) [INFO] 
* 2024-07-26 03:09:46 (6938) [INFO] 
* 2024-07-26 03:09:50 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-26 03:09:50 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-26 03:09:53 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-26 03:09:53 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-26 03:09:53 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-26 03:09:53 (6908) [INFO] 
* 2024-07-26 03:09:53 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-26 03:09:53 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-26 03:09:53 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-26 03:09:53 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-26 03:09:53 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-26 03:09:53 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-26 03:09:53 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-26 03:09:53 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-26 03:09:53 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-26 03:09:54 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-26 03:09:54 (6938) [INFO] 
* 2024-07-26 03:09:58 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-26 03:09:58 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-26 03:09:59 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-26 03:10:00 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Tf533N3fCQ/ea_profile.json
* 2024-07-26 03:10:02 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Tf533N3fCQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-26 03:10:02 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-27 03:11:17 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-27 03:11:17 (8209) [INFO] Script is up to date.
* 2024-07-27 03:11:18 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-27 03:11:18 (6908) [INFO] 
* 2024-07-27 03:11:24 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-27 03:11:25 (6938) [INFO] 
* 2024-07-27 03:11:26 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-27 03:11:26 (6908) [INFO] 
* 2024-07-27 03:11:30 (6938) [INFO] 
* 2024-07-27 03:11:35 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-27 03:11:35 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-27 03:11:37 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-27 03:11:37 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-27 03:11:37 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-27 03:11:37 (6908) [INFO] 
* 2024-07-27 03:11:37 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-27 03:11:37 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-27 03:11:37 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-27 03:11:37 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-27 03:11:37 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-27 03:11:37 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-27 03:11:37 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-27 03:11:37 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-27 03:11:37 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-27 03:11:37 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-27 03:11:37 (6938) [INFO] 
* 2024-07-27 03:11:41 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-27 03:11:41 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-27 03:11:42 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-27 03:11:44 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fADpr9ZfJf/ea_profile.json
* 2024-07-27 03:11:47 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/fADpr9ZfJf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-27 03:11:47 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-28 03:11:30 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-28 03:11:31 (8209) [INFO] Script is up to date.
* 2024-07-28 03:11:32 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-28 03:11:32 (6908) [INFO] 
* 2024-07-28 03:11:39 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-28 03:11:39 (6938) [INFO] 
* 2024-07-28 03:11:41 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-28 03:11:41 (6908) [INFO] 
* 2024-07-28 03:11:44 (6938) [INFO] 
* 2024-07-28 03:11:48 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-28 03:11:48 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-28 03:11:51 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-28 03:11:51 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-28 03:11:51 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-28 03:11:51 (6908) [INFO] 
* 2024-07-28 03:11:52 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-28 03:11:53 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-28 03:11:53 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-28 03:11:53 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-28 03:11:53 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-28 03:11:53 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-28 03:11:53 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-28 03:11:53 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-28 03:11:53 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-28 03:11:53 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-28 03:11:53 (6938) [INFO] 
* 2024-07-28 03:11:57 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-28 03:11:57 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-28 03:11:58 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-28 03:12:01 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uklKSTSpvQ/ea_profile.json
* 2024-07-28 03:12:06 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uklKSTSpvQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-28 03:12:06 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-29 03:09:26 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-29 03:09:26 (8209) [INFO] Script is up to date.
* 2024-07-29 03:09:28 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-29 03:09:28 (6908) [INFO] 
* 2024-07-29 03:09:36 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-29 03:09:37 (6938) [INFO] 
* 2024-07-29 03:09:37 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-29 03:09:37 (6908) [INFO] 
* 2024-07-29 03:09:40 (6938) [INFO] 
* 2024-07-29 03:09:44 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-29 03:09:44 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-29 03:09:46 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-29 03:09:46 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-29 03:09:46 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-29 03:09:46 (6908) [INFO] 
* 2024-07-29 03:09:46 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-29 03:09:46 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-29 03:09:46 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-29 03:09:46 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-29 03:09:46 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-29 03:09:46 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-29 03:09:46 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-29 03:09:46 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-29 03:09:46 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-29 03:09:46 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-29 03:09:46 (6938) [INFO] 
* 2024-07-29 03:09:49 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-29 03:09:49 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-29 03:09:50 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-29 03:09:51 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y_RFIjFGLB/ea_profile.json
* 2024-07-29 03:09:53 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y_RFIjFGLB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-29 03:09:53 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-30 03:09:29 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-30 03:09:29 (8209) [INFO] Script is up to date.
* 2024-07-30 03:09:32 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-30 03:09:32 (6908) [INFO] 
* 2024-07-30 03:09:38 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-30 03:09:39 (6938) [INFO] 
* 2024-07-30 03:09:40 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-30 03:09:40 (6908) [INFO] 
* 2024-07-30 03:09:41 (6938) [INFO] 
* 2024-07-30 03:09:46 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-30 03:09:46 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-30 03:09:47 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-30 03:09:47 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-30 03:09:47 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-30 03:09:47 (6908) [INFO] 
* 2024-07-30 03:09:48 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-30 03:09:48 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-30 03:09:48 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-30 03:09:48 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-30 03:09:48 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-30 03:09:48 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-30 03:09:48 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-30 03:09:48 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-30 03:09:48 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-30 03:09:48 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-30 03:09:48 (6938) [INFO] 
* 2024-07-30 03:09:51 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-30 03:09:51 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-30 03:09:52 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-30 03:09:53 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OkE_sEWnsI/ea_profile.json
* 2024-07-30 03:09:55 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/OkE_sEWnsI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-30 03:09:55 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-07-31 03:09:45 (8187) [INFO] Self-update of script version 49 requested.
* 2024-07-31 03:09:45 (8209) [INFO] Script is up to date.
* 2024-07-31 03:09:47 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-07-31 03:09:47 (6908) [INFO] 
* 2024-07-31 03:09:57 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-07-31 03:09:57 (6938) [INFO] 
* 2024-07-31 03:09:58 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-07-31 03:09:58 (6908) [INFO] 
* 2024-07-31 03:10:01 (6938) [INFO] 
* 2024-07-31 03:10:06 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-07-31 03:10:06 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-07-31 03:10:08 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-31 03:10:08 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-07-31 03:10:08 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-07-31 03:10:08 (6908) [INFO] 
* 2024-07-31 03:10:09 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-07-31 03:10:09 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-07-31 03:10:09 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-07-31 03:10:09 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-07-31 03:10:09 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-07-31 03:10:09 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-07-31 03:10:09 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-07-31 03:10:09 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-07-31 03:10:09 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-07-31 03:10:09 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-07-31 03:10:09 (6938) [INFO] 
* 2024-07-31 03:10:15 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-07-31 03:10:15 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-07-31 03:10:16 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-07-31 03:10:17 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3Um0aSTrm3/ea_profile.json
* 2024-07-31 03:10:19 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/3Um0aSTrm3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-07-31 03:10:19 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-01 03:09:13 (8187) [INFO] Self-update of script version 49 requested.
* 2024-08-01 03:09:14 (8209) [INFO] Script is up to date.
* 2024-08-01 03:09:15 (6907) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-01 03:09:15 (6908) [INFO] 
* 2024-08-01 03:09:18 (6921) [INFO] {"items": "7.13.4", "warnings": [], "version": "7.13.4", "eula": null, "license": {"status": true, "expiration": null, "user_limit": -1, "id": "IMUNIFYAV", "user_count": 2, "message": null, "license_type": "imunifyAV", "ip_license": true, "upgrade_url": "../../../scripts14/purchase_imunifyavplus_init_IMUNIFY", "upgrade_url_360": "../../../scripts14/purchase_imunify360_init_IMUNIFY"}}
* 2024-08-01 03:09:19 (6938) [INFO] 
* 2024-08-01 03:09:19 (6907) [INFO] Running: /usr/bin/yum list extras
* 2024-08-01 03:09:19 (6908) [INFO] 
* 2024-08-01 03:09:21 (6938) [INFO] 
* 2024-08-01 03:09:23 (2164) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-01 03:09:23 (214) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-01 03:09:25 (2047) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

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

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

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

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

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

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

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-01 03:09:25 (2048) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-01 03:09:25 (6907) [INFO] Running: /usr/bin/yum clean all
* 2024-08-01 03:09:25 (6908) [INFO] 
* 2024-08-01 03:09:26 (6921) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-01 03:09:26 (6921) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-01 03:09:26 (6921) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-01 03:09:26 (6921) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-01 03:09:26 (6921) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-01 03:09:26 (6921) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-01 03:09:26 (6921) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-01 03:09:26 (6921) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-01 03:09:26 (6921) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-01 03:09:26 (6921) [INFO] Cleaning up list of fastest mirrors
* 2024-08-01 03:09:26 (6938) [INFO] 
* 2024-08-01 03:09:29 (2057) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-01 03:09:29 (2058) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

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

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



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

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

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-01 03:09:30 (1063) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-01 03:09:30 (6049) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kuWUapvfRy/ea_profile.json
* 2024-08-01 03:09:33 (374) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kuWUapvfRy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6051.
* 2024-08-01 03:09:33 (338) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-02 03:08:48 (8187) [INFO] Self-update of script version 49 requested.
* 2024-08-02 03:08:48 (8192) [INFO] Newer version of script found. Downloading.
* 2024-08-02 03:08:49 (8201) [INFO] Script update to version 50 successful.
* 2024-08-02 03:08:50 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-02 03:08:50 (7164) [INFO] 
* 2024-08-02 03:08:54 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-02 03:08:54 (7164) [INFO] 
* 2024-08-02 03:09:00 (2176) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-02 03:09:00 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-02 03:09:02 (2059) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-02 03:09:02 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-02 03:09:02 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-02 03:09:02 (7164) [INFO] 
* 2024-08-02 03:09:02 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-02 03:09:02 (7177) [INFO] Existing lock /var/run/yum.pid: another copy is running as pid 8278.
* 2024-08-02 03:09:02 (7177) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-02 03:09:02 (7177) [INFO]   The other application is: yum
* 2024-08-02 03:09:02 (7177) [INFO]     Memory :  30 M RSS (423 MB VSZ)
* 2024-08-02 03:09:02 (7177) [INFO]     Started: Fri Aug  2 03:09:01 2024 - 00:01 ago
* 2024-08-02 03:09:02 (7177) [INFO]     State  : Sleeping, pid: 8278
* 2024-08-02 03:09:04 (7177) [INFO] Another app is currently holding the yum lock; waiting for it to exit...
* 2024-08-02 03:09:04 (7177) [INFO]   The other application is: yum
* 2024-08-02 03:09:04 (7177) [INFO]     Memory :  32 M RSS (429 MB VSZ)
* 2024-08-02 03:09:04 (7177) [INFO]     Started: Fri Aug  2 03:09:01 2024 - 00:03 ago
* 2024-08-02 03:09:04 (7177) [INFO]     State  : Sleeping, pid: 8278
* 2024-08-02 03:09:07 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-02 03:09:07 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-02 03:09:07 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-02 03:09:07 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-02 03:09:07 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-02 03:09:07 (7177) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-02 03:09:07 (7177) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-02 03:09:07 (7177) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-02 03:09:07 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-02 03:09:07 (7194) [INFO] 
* 2024-08-02 03:09:10 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-02 03:09:10 (2070) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-02 03:09:10 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-02 03:09:11 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/P68zilWqtK/ea_profile.json
* 2024-08-02 03:09:12 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/P68zilWqtK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-02 03:09:12 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-03 03:09:36 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-03 03:09:37 (8496) [INFO] Script is up to date.
* 2024-08-03 03:09:37 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-03 03:09:37 (7164) [INFO] 
* 2024-08-03 03:09:41 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-03 03:09:41 (7164) [INFO] 
* 2024-08-03 03:09:48 (2176) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-03 03:09:48 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-03 03:09:50 (2059) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-03 03:09:50 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-03 03:09:50 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-03 03:09:51 (7164) [INFO] 
* 2024-08-03 03:09:51 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-03 03:09:51 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-03 03:09:51 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-03 03:09:51 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-03 03:09:51 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-03 03:09:51 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-03 03:09:51 (7177) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-03 03:09:51 (7177) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-03 03:09:51 (7177) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-03 03:09:51 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-03 03:09:51 (7194) [INFO] 
* 2024-08-03 03:09:55 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-03 03:09:55 (2070) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-03 03:09:55 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-03 03:09:56 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KGzXrZEua7/ea_profile.json
* 2024-08-03 03:09:58 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KGzXrZEua7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-03 03:09:58 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-04 03:09:47 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-04 03:09:47 (8496) [INFO] Script is up to date.
* 2024-08-04 03:09:48 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-04 03:09:48 (7164) [INFO] 
* 2024-08-04 03:09:52 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-04 03:09:52 (7164) [INFO] 
* 2024-08-04 03:09:57 (2176) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-04 03:09:57 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-04 03:09:58 (2059) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-04 03:09:58 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-04 03:09:58 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-04 03:09:58 (7164) [INFO] 
* 2024-08-04 03:09:58 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-04 03:09:58 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-04 03:09:58 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-04 03:09:58 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-04 03:09:58 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-04 03:09:58 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-04 03:09:58 (7177) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-04 03:09:58 (7177) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-04 03:09:58 (7177) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-04 03:09:59 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-04 03:09:59 (7194) [INFO] 
* 2024-08-04 03:10:01 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-04 03:10:01 (2070) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-04 03:10:02 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-04 03:10:03 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5OM_g7GRoS/ea_profile.json
* 2024-08-04 03:10:05 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5OM_g7GRoS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-04 03:10:05 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-05 03:08:43 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-05 03:08:44 (8496) [INFO] Script is up to date.
* 2024-08-05 03:08:45 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-05 03:08:45 (7164) [INFO] 
* 2024-08-05 03:08:48 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-05 03:08:48 (7164) [INFO] 
* 2024-08-05 03:08:53 (2176) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-05 03:08:53 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-05 03:08:54 (2059) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-05 03:08:54 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-05 03:08:54 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-05 03:08:54 (7164) [INFO] 
* 2024-08-05 03:08:54 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-05 03:08:55 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-05 03:08:55 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-05 03:08:55 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-05 03:08:55 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-05 03:08:55 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-05 03:08:55 (7177) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-05 03:08:55 (7177) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-05 03:08:55 (7177) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-05 03:08:55 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-05 03:08:55 (7194) [INFO] 
* 2024-08-05 03:08:58 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-05 03:08:58 (2070) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-05 03:08:58 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-05 03:08:59 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L0tNEexsfS/ea_profile.json
* 2024-08-05 03:09:01 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/L0tNEexsfS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-05 03:09:01 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-06 03:08:59 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-06 03:09:00 (8496) [INFO] Script is up to date.
* 2024-08-06 03:09:01 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-06 03:09:01 (7164) [INFO] 
* 2024-08-06 03:09:05 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-06 03:09:05 (7164) [INFO] 
* 2024-08-06 03:09:09 (2176) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-06 03:09:09 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-06 03:09:11 (2059) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-06 03:09:11 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-06 03:09:11 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-06 03:09:11 (7164) [INFO] 
* 2024-08-06 03:09:11 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-06 03:09:11 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-06 03:09:11 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-06 03:09:11 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-06 03:09:11 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-06 03:09:11 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-06 03:09:11 (7177) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-06 03:09:11 (7177) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-06 03:09:11 (7177) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-06 03:09:11 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-06 03:09:11 (7194) [INFO] 
* 2024-08-06 03:09:14 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-06 03:09:14 (2070) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-06 03:09:14 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-06 03:09:15 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rmvJXVYFZW/ea_profile.json
* 2024-08-06 03:09:17 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rmvJXVYFZW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-06 03:09:17 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-07 03:09:18 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-07 03:09:18 (8496) [INFO] Script is up to date.
* 2024-08-07 03:09:19 (7163) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-07 03:09:19 (7164) [INFO] 
* 2024-08-07 03:09:24 (7163) [INFO] Running: /usr/bin/yum list extras
* 2024-08-07 03:09:24 (7164) [INFO] 
* 2024-08-07 03:09:28 (2176) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-07 03:09:28 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-07 03:09:31 (2059) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-07 03:09:31 (2060) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-07 03:09:31 (7163) [INFO] Running: /usr/bin/yum clean all
* 2024-08-07 03:09:31 (7164) [INFO] 
* 2024-08-07 03:09:31 (7177) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-07 03:09:31 (7177) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-07 03:09:31 (7177) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-07 03:09:31 (7177) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-07 03:09:31 (7177) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-07 03:09:31 (7177) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-07 03:09:31 (7177) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-07 03:09:31 (7177) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-07 03:09:31 (7177) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-07 03:09:31 (7177) [INFO] Cleaning up list of fastest mirrors
* 2024-08-07 03:09:31 (7194) [INFO] 
* 2024-08-07 03:09:34 (2069) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-07 03:09:34 (2070) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-07 03:09:35 (1075) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-07 03:09:36 (6305) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CjsF5MEekQ/ea_profile.json
* 2024-08-07 03:09:37 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CjsF5MEekQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6307.
* 2024-08-07 03:09:37 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-08 03:08:56 (8474) [INFO] Self-update of script version 50 requested.
* 2024-08-08 03:08:56 (8479) [INFO] Newer version of script found. Downloading.
* 2024-08-08 03:08:57 (8488) [INFO] Script update to version 51 successful.
* 2024-08-08 03:08:58 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-08 03:08:58 (7324) [INFO] 
* 2024-08-08 03:09:06 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-08 03:09:06 (7324) [INFO] 
* 2024-08-08 03:09:13 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-08 03:09:13 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-08 03:09:15 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-08 03:09:15 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-08 03:09:15 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-08 03:09:15 (7324) [INFO] 
* 2024-08-08 03:09:15 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-08 03:09:15 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-08 03:09:15 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-08 03:09:15 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-08 03:09:15 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-08 03:09:15 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-08 03:09:15 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-08 03:09:15 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-08 03:09:15 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-08 03:09:15 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-08 03:09:15 (7354) [INFO] 
* 2024-08-08 03:09:18 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-08 03:09:18 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-08 03:09:18 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-08 03:09:20 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DsIjrimkWp/ea_profile.json
* 2024-08-08 03:09:21 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DsIjrimkWp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-08 03:09:21 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-09 03:10:06 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-09 03:10:16 (8664) [INFO] Script is up to date.
* 2024-08-09 03:10:22 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-09 03:10:22 (7324) [INFO] 
* 2024-08-09 03:10:31 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-09 03:10:31 (7324) [INFO] 
* 2024-08-09 03:10:51 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-09 03:10:51 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-09 03:11:09 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-09 03:11:09 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-09 03:11:09 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-09 03:11:09 (7324) [INFO] 
* 2024-08-09 03:11:09 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-09 03:11:09 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-09 03:11:09 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-09 03:11:09 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-09 03:11:09 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-09 03:11:09 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-09 03:11:09 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-09 03:11:09 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-09 03:11:09 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-09 03:11:09 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-09 03:11:09 (7354) [INFO] 
* 2024-08-09 03:11:11 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-09 03:11:11 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-09 03:11:12 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-09 03:11:12 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MmI_nZR9E4/ea_profile.json
* 2024-08-09 03:11:14 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MmI_nZR9E4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-09 03:11:14 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-10 03:11:17 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-10 03:11:21 (8664) [INFO] Script is up to date.
* 2024-08-10 03:11:25 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-10 03:11:25 (7324) [INFO] 
* 2024-08-10 03:11:32 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-10 03:11:32 (7324) [INFO] 
* 2024-08-10 03:11:48 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-10 03:11:48 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-10 03:11:49 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-10 03:11:49 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-10 03:11:49 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-10 03:11:49 (7324) [INFO] 
* 2024-08-10 03:11:49 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-10 03:11:50 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-10 03:11:50 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-10 03:11:50 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-10 03:11:50 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-10 03:11:50 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-10 03:11:50 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-10 03:11:50 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-10 03:11:50 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-10 03:11:50 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-10 03:11:50 (7354) [INFO] 
* 2024-08-10 03:11:52 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-10 03:11:52 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-10 03:11:53 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-10 03:11:54 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/E5mOWVIyv8/ea_profile.json
* 2024-08-10 03:11:56 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/E5mOWVIyv8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-10 03:11:56 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-11 03:09:23 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-11 03:09:23 (8664) [INFO] Script is up to date.
* 2024-08-11 03:09:24 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-11 03:09:24 (7324) [INFO] 
* 2024-08-11 03:09:27 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-11 03:09:27 (7324) [INFO] 
* 2024-08-11 03:09:30 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-11 03:09:30 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-11 03:09:44 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-11 03:09:44 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-11 03:09:44 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-11 03:09:44 (7324) [INFO] 
* 2024-08-11 03:09:44 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-11 03:09:44 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-11 03:09:44 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-11 03:09:44 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-11 03:09:44 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-11 03:09:44 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-11 03:09:44 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-11 03:09:44 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-11 03:09:44 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-11 03:09:44 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-11 03:09:44 (7354) [INFO] 
* 2024-08-11 03:09:53 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-11 03:09:53 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-11 03:09:53 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-11 03:09:54 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IMZI7fA9It/ea_profile.json
* 2024-08-11 03:10:04 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IMZI7fA9It/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-11 03:10:04 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-12 03:08:37 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-12 03:08:37 (8664) [INFO] Script is up to date.
* 2024-08-12 03:08:38 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-12 03:08:38 (7324) [INFO] 
* 2024-08-12 03:08:41 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-12 03:08:41 (7324) [INFO] 
* 2024-08-12 03:08:47 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-12 03:08:47 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-12 03:08:49 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-12 03:08:49 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-12 03:08:49 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-12 03:08:49 (7324) [INFO] 
* 2024-08-12 03:08:49 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-12 03:08:49 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-12 03:08:49 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-12 03:08:49 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-12 03:08:49 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-12 03:08:49 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-12 03:08:49 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-12 03:08:49 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-12 03:08:49 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-12 03:08:49 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-12 03:08:49 (7354) [INFO] 
* 2024-08-12 03:08:53 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-12 03:08:53 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-12 03:08:53 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-12 03:08:54 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dy5DFTJJHV/ea_profile.json
* 2024-08-12 03:08:56 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dy5DFTJJHV/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-12 03:08:56 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-13 03:09:59 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-13 03:10:03 (8664) [INFO] Script is up to date.
* 2024-08-13 03:10:07 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-13 03:10:07 (7324) [INFO] 
* 2024-08-13 03:10:17 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-13 03:10:17 (7324) [INFO] 
* 2024-08-13 03:10:27 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-13 03:10:27 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-13 03:10:33 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-13 03:10:33 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-13 03:10:33 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-13 03:10:33 (7324) [INFO] 
* 2024-08-13 03:10:33 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-13 03:10:33 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-13 03:10:33 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-13 03:10:33 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-13 03:10:33 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-13 03:10:33 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-13 03:10:33 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-13 03:10:33 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-13 03:10:33 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-13 03:10:33 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-13 03:10:33 (7354) [INFO] 
* 2024-08-13 03:10:37 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-13 03:10:37 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-13 03:10:37 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-13 03:10:38 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QEuyNYss24/ea_profile.json
* 2024-08-13 03:10:39 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QEuyNYss24/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-13 03:10:39 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-14 03:08:40 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-14 03:08:40 (8664) [INFO] Script is up to date.
* 2024-08-14 03:08:41 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-14 03:08:41 (7324) [INFO] 
* 2024-08-14 03:08:44 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-14 03:08:44 (7324) [INFO] 
* 2024-08-14 03:08:48 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-14 03:08:48 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-14 03:08:49 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-14 03:08:49 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-14 03:08:49 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-14 03:08:49 (7324) [INFO] 
* 2024-08-14 03:08:50 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-14 03:08:50 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-14 03:08:50 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-14 03:08:50 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-14 03:08:50 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-14 03:08:50 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-14 03:08:50 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-14 03:08:50 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-14 03:08:50 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-14 03:08:50 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-14 03:08:50 (7354) [INFO] 
* 2024-08-14 03:08:53 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-14 03:08:53 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-14 03:08:53 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-14 03:08:54 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u8IIh_vxiM/ea_profile.json
* 2024-08-14 03:08:55 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/u8IIh_vxiM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-14 03:08:55 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-15 03:08:38 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-15 03:08:38 (8664) [INFO] Script is up to date.
* 2024-08-15 03:08:39 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-15 03:08:39 (7324) [INFO] 
* 2024-08-15 03:08:42 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-15 03:08:42 (7324) [INFO] 
* 2024-08-15 03:08:46 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-15 03:08:46 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-15 03:08:48 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-15 03:08:48 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-15 03:08:48 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-15 03:08:48 (7324) [INFO] 
* 2024-08-15 03:08:48 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-15 03:08:48 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-15 03:08:48 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-15 03:08:48 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-15 03:08:48 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-15 03:08:48 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-15 03:08:48 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-15 03:08:48 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-15 03:08:48 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-15 03:08:48 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-15 03:08:48 (7354) [INFO] 
* 2024-08-15 03:08:51 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-15 03:08:51 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-15 03:08:51 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-15 03:08:52 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uCpVdMM5wI/ea_profile.json
* 2024-08-15 03:08:53 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uCpVdMM5wI/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-15 03:08:53 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-16 03:09:41 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-16 03:09:41 (8664) [INFO] Script is up to date.
* 2024-08-16 03:09:42 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-16 03:09:42 (7324) [INFO] 
* 2024-08-16 03:09:46 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-16 03:09:46 (7324) [INFO] 
* 2024-08-16 03:09:50 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-16 03:09:50 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-16 03:09:51 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-16 03:09:51 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-16 03:09:51 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-16 03:09:51 (7324) [INFO] 
* 2024-08-16 03:09:51 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-16 03:09:51 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-16 03:09:51 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-16 03:09:51 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-16 03:09:51 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-16 03:09:51 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-16 03:09:51 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-16 03:09:51 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-16 03:09:51 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-16 03:09:51 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-16 03:09:51 (7354) [INFO] 
* 2024-08-16 03:09:54 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-16 03:09:54 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-16 03:09:55 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-16 03:09:55 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/InVYVP8oHQ/ea_profile.json
* 2024-08-16 03:09:57 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/InVYVP8oHQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-16 03:09:57 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-17 03:09:15 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-17 03:09:15 (8664) [INFO] Script is up to date.
* 2024-08-17 03:09:16 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-17 03:09:16 (7324) [INFO] 
* 2024-08-17 03:09:20 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-17 03:09:20 (7324) [INFO] 
* 2024-08-17 03:09:22 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-17 03:09:22 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-17 03:09:24 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-17 03:09:24 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-17 03:09:24 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-17 03:09:24 (7324) [INFO] 
* 2024-08-17 03:09:24 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-17 03:09:24 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-17 03:09:24 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-17 03:09:24 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-17 03:09:24 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-17 03:09:24 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-17 03:09:24 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-17 03:09:24 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-17 03:09:24 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-17 03:09:24 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-17 03:09:24 (7354) [INFO] 
* 2024-08-17 03:09:27 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-17 03:09:27 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-17 03:09:27 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-17 03:09:28 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0YnKp4MJSM/ea_profile.json
* 2024-08-17 03:09:29 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0YnKp4MJSM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-17 03:09:29 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-18 03:09:09 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-18 03:09:09 (8664) [INFO] Script is up to date.
* 2024-08-18 03:09:10 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-18 03:09:10 (7324) [INFO] 
* 2024-08-18 03:09:14 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-18 03:09:14 (7324) [INFO] 
* 2024-08-18 03:09:17 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-18 03:09:17 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-18 03:09:20 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-18 03:09:20 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-18 03:09:20 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-18 03:09:20 (7324) [INFO] 
* 2024-08-18 03:09:20 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-18 03:09:20 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-18 03:09:20 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-18 03:09:20 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-18 03:09:20 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-18 03:09:20 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-18 03:09:20 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-18 03:09:20 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-18 03:09:20 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-18 03:09:20 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-18 03:09:20 (7354) [INFO] 
* 2024-08-18 03:09:23 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-18 03:09:23 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-18 03:09:23 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-18 03:09:24 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/205sJ7aprq/ea_profile.json
* 2024-08-18 03:09:26 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/205sJ7aprq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-18 03:09:26 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-19 03:08:34 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-19 03:08:34 (8664) [INFO] Script is up to date.
* 2024-08-19 03:08:35 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-19 03:08:35 (7324) [INFO] 
* 2024-08-19 03:08:36 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-19 03:08:36 (7324) [INFO] 
* 2024-08-19 03:08:40 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-19 03:08:40 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-19 03:08:42 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-19 03:08:42 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-19 03:08:42 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-19 03:08:42 (7324) [INFO] 
* 2024-08-19 03:08:42 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-19 03:08:42 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-19 03:08:42 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-19 03:08:42 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-19 03:08:42 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-19 03:08:42 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-19 03:08:42 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-19 03:08:42 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-19 03:08:42 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-19 03:08:42 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-19 03:08:42 (7354) [INFO] 
* 2024-08-19 03:08:44 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-19 03:08:44 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-19 03:08:44 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-19 03:08:45 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EUss85mxzE/ea_profile.json
* 2024-08-19 03:08:47 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EUss85mxzE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-19 03:08:47 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-20 03:08:35 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-20 03:08:35 (8664) [INFO] Script is up to date.
* 2024-08-20 03:08:36 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-20 03:08:36 (7324) [INFO] 
* 2024-08-20 03:08:37 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-20 03:08:37 (7324) [INFO] 
* 2024-08-20 03:08:40 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-20 03:08:40 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-20 03:08:42 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-20 03:08:42 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-20 03:08:42 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-20 03:08:42 (7324) [INFO] 
* 2024-08-20 03:08:42 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-20 03:08:42 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-20 03:08:42 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-20 03:08:42 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-20 03:08:42 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-20 03:08:42 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-20 03:08:42 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-20 03:08:42 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-20 03:08:42 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-20 03:08:42 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-20 03:08:42 (7354) [INFO] 
* 2024-08-20 03:08:45 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-20 03:08:45 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-20 03:08:46 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-20 03:08:46 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NUMIyXyYJ4/ea_profile.json
* 2024-08-20 03:08:48 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NUMIyXyYJ4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-20 03:08:48 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-21 03:08:37 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-21 03:08:37 (8664) [INFO] Script is up to date.
* 2024-08-21 03:08:38 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-21 03:08:38 (7324) [INFO] 
* 2024-08-21 03:08:42 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-21 03:08:42 (7324) [INFO] 
* 2024-08-21 03:08:46 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-21 03:08:46 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-21 03:08:47 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-21 03:08:47 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-21 03:08:47 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-21 03:08:47 (7324) [INFO] 
* 2024-08-21 03:08:47 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-21 03:08:48 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-21 03:08:48 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-21 03:08:48 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-21 03:08:48 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-21 03:08:48 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-21 03:08:48 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-21 03:08:48 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-21 03:08:48 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-21 03:08:48 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-21 03:08:48 (7354) [INFO] 
* 2024-08-21 03:08:51 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-21 03:08:51 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-21 03:08:51 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-21 03:08:51 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EgU3Fgp7IX/ea_profile.json
* 2024-08-21 03:08:54 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EgU3Fgp7IX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-21 03:08:54 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-22 03:08:35 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-22 03:08:35 (8664) [INFO] Script is up to date.
* 2024-08-22 03:08:36 (7323) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-22 03:08:36 (7324) [INFO] 
* 2024-08-22 03:08:39 (7323) [INFO] Running: /usr/bin/yum list extras
* 2024-08-22 03:08:39 (7324) [INFO] 
* 2024-08-22 03:08:44 (2146) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-22 03:08:44 (226) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-22 03:08:46 (2029) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-22 03:08:46 (2030) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-22 03:08:46 (7323) [INFO] Running: /usr/bin/yum clean all
* 2024-08-22 03:08:46 (7324) [INFO] 
* 2024-08-22 03:08:46 (7337) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-22 03:08:46 (7337) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-22 03:08:46 (7337) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-22 03:08:46 (7337) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-22 03:08:46 (7337) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-22 03:08:46 (7337) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-22 03:08:46 (7337) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-22 03:08:46 (7337) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-22 03:08:46 (7337) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-22 03:08:46 (7337) [INFO] Cleaning up list of fastest mirrors
* 2024-08-22 03:08:46 (7354) [INFO] 
* 2024-08-22 03:08:50 (2039) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-22 03:08:50 (2040) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-22 03:08:50 (1058) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-22 03:08:50 (6442) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B0fqKcF9rM/ea_profile.json
* 2024-08-22 03:08:52 (386) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/B0fqKcF9rM/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6444.
* 2024-08-22 03:08:52 (350) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-23 03:08:33 (8642) [INFO] Self-update of script version 51 requested.
* 2024-08-23 03:08:33 (8647) [INFO] Newer version of script found. Downloading.
* 2024-08-23 03:08:34 (8656) [INFO] Script update to version 52 successful.
* 2024-08-23 03:08:35 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-23 03:08:35 (7574) [INFO] 
* 2024-08-23 03:08:37 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-23 03:08:37 (7574) [INFO] 
* 2024-08-23 03:08:41 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-23 03:08:41 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-23 03:08:43 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-23 03:08:43 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-23 03:08:43 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-23 03:08:43 (7574) [INFO] 
* 2024-08-23 03:08:43 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-23 03:08:43 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-23 03:08:43 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-23 03:08:43 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-23 03:08:43 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-23 03:08:43 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-23 03:08:43 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-23 03:08:43 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-23 03:08:43 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-23 03:08:43 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-23 03:08:43 (7604) [INFO] 
* 2024-08-23 03:08:45 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-23 03:08:45 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-23 03:08:45 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-23 03:08:45 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9ae4CSpXJ4/ea_profile.json
* 2024-08-23 03:08:47 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9ae4CSpXJ4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-23 03:08:47 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-24 03:09:14 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-24 03:09:14 (8939) [INFO] Script is up to date.
* 2024-08-24 03:09:15 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-24 03:09:15 (7574) [INFO] 
* 2024-08-24 03:09:17 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-24 03:09:17 (7574) [INFO] 
* 2024-08-24 03:09:20 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-24 03:09:20 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-24 03:09:22 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-24 03:09:22 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-24 03:09:22 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-24 03:09:22 (7574) [INFO] 
* 2024-08-24 03:09:22 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-24 03:09:22 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-24 03:09:22 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-24 03:09:22 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-24 03:09:22 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-24 03:09:22 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-24 03:09:22 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-24 03:09:22 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-24 03:09:22 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-24 03:09:22 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-24 03:09:22 (7604) [INFO] 
* 2024-08-24 03:09:24 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-24 03:09:24 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-24 03:09:24 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-24 03:09:25 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/27T5cYQcCu/ea_profile.json
* 2024-08-24 03:09:26 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/27T5cYQcCu/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-24 03:09:26 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-25 03:09:28 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-25 03:09:29 (8939) [INFO] Script is up to date.
* 2024-08-25 03:09:30 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-25 03:09:30 (7574) [INFO] 
* 2024-08-25 03:09:33 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-25 03:09:33 (7574) [INFO] 
* 2024-08-25 03:09:36 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-25 03:09:36 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-25 03:09:38 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-25 03:09:38 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-25 03:09:38 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-25 03:09:38 (7574) [INFO] 
* 2024-08-25 03:09:38 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-25 03:09:38 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-25 03:09:38 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-25 03:09:38 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-25 03:09:38 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-25 03:09:38 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-25 03:09:38 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-25 03:09:38 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-25 03:09:38 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-25 03:09:38 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-25 03:09:38 (7604) [INFO] 
* 2024-08-25 03:09:40 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-25 03:09:40 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-25 03:09:40 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-25 03:09:41 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9QUXBCNZIe/ea_profile.json
* 2024-08-25 03:09:43 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9QUXBCNZIe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-25 03:09:43 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-26 03:08:33 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-26 03:08:33 (8939) [INFO] Script is up to date.
* 2024-08-26 03:08:34 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-26 03:08:34 (7574) [INFO] 
* 2024-08-26 03:08:36 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-26 03:08:36 (7574) [INFO] 
* 2024-08-26 03:08:39 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-26 03:08:39 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-26 03:08:40 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-26 03:08:40 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-26 03:08:40 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-26 03:08:40 (7574) [INFO] 
* 2024-08-26 03:08:40 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-26 03:08:40 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-26 03:08:40 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-26 03:08:40 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-26 03:08:40 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-26 03:08:40 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-26 03:08:40 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-26 03:08:40 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-26 03:08:40 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-26 03:08:40 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-26 03:08:40 (7604) [INFO] 
* 2024-08-26 03:08:43 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-26 03:08:43 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-26 03:08:43 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-26 03:08:44 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JqLLv7Lk0l/ea_profile.json
* 2024-08-26 03:08:45 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/JqLLv7Lk0l/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-26 03:08:45 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-27 03:08:31 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-27 03:08:31 (8939) [INFO] Script is up to date.
* 2024-08-27 03:08:32 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-27 03:08:32 (7574) [INFO] 
* 2024-08-27 03:08:34 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-27 03:08:34 (7574) [INFO] 
* 2024-08-27 03:08:42 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-27 03:08:42 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-27 03:08:47 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-27 03:08:47 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-27 03:08:47 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-27 03:08:47 (7574) [INFO] 
* 2024-08-27 03:08:47 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-27 03:08:47 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-27 03:08:47 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-27 03:08:47 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-27 03:08:47 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-27 03:08:47 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-27 03:08:47 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-27 03:08:47 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-27 03:08:47 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-27 03:08:47 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-27 03:08:47 (7604) [INFO] 
* 2024-08-27 03:08:51 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-27 03:08:51 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-27 03:08:51 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-27 03:08:52 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RJspWpn3NB/ea_profile.json
* 2024-08-27 03:08:55 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RJspWpn3NB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-27 03:08:55 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-28 03:08:31 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-28 03:08:31 (8939) [INFO] Script is up to date.
* 2024-08-28 03:08:31 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-28 03:08:31 (7574) [INFO] 
* 2024-08-28 03:08:35 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-28 03:08:35 (7574) [INFO] 
* 2024-08-28 03:08:38 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-28 03:08:38 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-28 03:08:39 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-28 03:08:39 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-28 03:08:39 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-28 03:08:39 (7574) [INFO] 
* 2024-08-28 03:08:39 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-28 03:08:40 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-28 03:08:40 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-28 03:08:40 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-28 03:08:40 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-28 03:08:40 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-28 03:08:40 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-28 03:08:40 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-28 03:08:40 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-28 03:08:40 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-28 03:08:40 (7604) [INFO] 
* 2024-08-28 03:08:43 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-28 03:08:43 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-28 03:08:43 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-28 03:08:44 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LTaxGUkYa4/ea_profile.json
* 2024-08-28 03:08:46 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LTaxGUkYa4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-28 03:08:46 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-29 03:08:31 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-29 03:08:31 (8939) [INFO] Script is up to date.
* 2024-08-29 03:08:32 (7573) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-29 03:08:32 (7574) [INFO] 
* 2024-08-29 03:08:34 (7573) [INFO] Running: /usr/bin/yum list extras
* 2024-08-29 03:08:34 (7574) [INFO] 
* 2024-08-29 03:08:38 (2080) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-29 03:08:38 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-29 03:08:40 (1963) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-29 03:08:40 (1964) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-29 03:08:40 (7573) [INFO] Running: /usr/bin/yum clean all
* 2024-08-29 03:08:40 (7574) [INFO] 
* 2024-08-29 03:08:40 (7587) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-29 03:08:40 (7587) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-29 03:08:40 (7587) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-29 03:08:40 (7587) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-29 03:08:40 (7587) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-29 03:08:40 (7587) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-29 03:08:40 (7587) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-29 03:08:40 (7587) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-29 03:08:40 (7587) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-29 03:08:40 (7587) [INFO] Cleaning up list of fastest mirrors
* 2024-08-29 03:08:40 (7604) [INFO] 
* 2024-08-29 03:08:42 (1973) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-29 03:08:42 (1974) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-29 03:08:42 (992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-29 03:08:43 (6692) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Sv8hxsxjMN/ea_profile.json
* 2024-08-29 03:08:44 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Sv8hxsxjMN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6694.
* 2024-08-29 03:08:44 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-30 03:08:32 (8917) [INFO] Self-update of script version 52 requested.
* 2024-08-30 03:08:32 (8922) [INFO] Newer version of script found. Downloading.
* 2024-08-30 03:08:32 (8931) [INFO] Script update to version 53 successful.
* 2024-08-30 03:08:33 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-30 03:08:33 (7647) [INFO] 
* 2024-08-30 03:08:35 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-08-30 03:08:35 (7647) [INFO] 
* 2024-08-30 03:08:40 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-30 03:08:40 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-30 03:08:41 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-30 03:08:41 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-30 03:08:41 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-08-30 03:08:41 (7647) [INFO] 
* 2024-08-30 03:08:41 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-30 03:08:42 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-30 03:08:42 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-30 03:08:42 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-30 03:08:42 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-30 03:08:42 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-30 03:08:42 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-30 03:08:42 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-30 03:08:42 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-30 03:08:42 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-08-30 03:08:42 (7677) [INFO] 
* 2024-08-30 03:08:44 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-30 03:08:44 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-30 03:08:45 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-30 03:08:45 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A8R215UxT4/ea_profile.json
* 2024-08-30 03:08:47 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/A8R215UxT4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-08-30 03:08:47 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-08-31 03:09:16 (8992) [INFO] Self-update of script version 53 requested.
* 2024-08-31 03:09:16 (9014) [INFO] Script is up to date.
* 2024-08-31 03:09:17 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-08-31 03:09:17 (7647) [INFO] 
* 2024-08-31 03:09:20 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-08-31 03:09:20 (7647) [INFO] 
* 2024-08-31 03:09:23 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-08-31 03:09:23 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-08-31 03:09:25 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-31 03:09:25 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-08-31 03:09:25 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-08-31 03:09:25 (7647) [INFO] 
* 2024-08-31 03:09:25 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-08-31 03:09:25 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-08-31 03:09:25 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-08-31 03:09:25 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-08-31 03:09:25 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-08-31 03:09:25 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-08-31 03:09:25 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-08-31 03:09:25 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-08-31 03:09:25 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-08-31 03:09:25 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-08-31 03:09:25 (7677) [INFO] 
* 2024-08-31 03:09:28 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-08-31 03:09:28 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-08-31 03:09:28 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-08-31 03:09:29 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ybr9cVDvta/ea_profile.json
* 2024-08-31 03:09:30 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Ybr9cVDvta/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-08-31 03:09:30 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-01 03:09:25 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-01 03:09:25 (9014) [INFO] Script is up to date.
* 2024-09-01 03:09:26 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-01 03:09:26 (7647) [INFO] 
* 2024-09-01 03:09:29 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-01 03:09:29 (7647) [INFO] 
* 2024-09-01 03:09:32 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-01 03:09:32 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-01 03:09:34 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-01 03:09:34 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-01 03:09:34 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-01 03:09:34 (7647) [INFO] 
* 2024-09-01 03:09:34 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-01 03:09:34 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-01 03:09:34 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-01 03:09:34 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-01 03:09:34 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-01 03:09:34 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-01 03:09:34 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-01 03:09:34 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-01 03:09:34 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-01 03:09:34 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-01 03:09:34 (7677) [INFO] 
* 2024-09-01 03:09:37 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-01 03:09:37 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-01 03:09:38 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-01 03:09:38 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uq2XK5Yj4d/ea_profile.json
* 2024-09-01 03:09:40 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uq2XK5Yj4d/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-01 03:09:40 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-02 03:08:37 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-02 03:08:37 (9014) [INFO] Script is up to date.
* 2024-09-02 03:08:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-02 03:08:38 (7647) [INFO] 
* 2024-09-02 03:08:40 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-02 03:08:40 (7647) [INFO] 
* 2024-09-02 03:08:45 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-02 03:08:45 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-02 03:08:47 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-02 03:08:47 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-02 03:08:47 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-02 03:08:47 (7647) [INFO] 
* 2024-09-02 03:08:47 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-02 03:08:47 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-02 03:08:47 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-02 03:08:47 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-02 03:08:47 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-02 03:08:47 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-02 03:08:47 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-02 03:08:47 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-02 03:08:47 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-02 03:08:47 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-02 03:08:47 (7677) [INFO] 
* 2024-09-02 03:08:50 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-02 03:08:50 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-02 03:08:50 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-02 03:08:51 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zFTyD47i7g/ea_profile.json
* 2024-09-02 03:08:53 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/zFTyD47i7g/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-02 03:08:53 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-03 03:08:38 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-03 03:08:38 (9014) [INFO] Script is up to date.
* 2024-09-03 03:08:39 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-03 03:08:39 (7647) [INFO] 
* 2024-09-03 03:08:41 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-03 03:08:41 (7647) [INFO] 
* 2024-09-03 03:08:47 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-03 03:08:47 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-03 03:08:48 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-03 03:08:48 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-03 03:08:48 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-03 03:08:48 (7647) [INFO] 
* 2024-09-03 03:08:48 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-03 03:08:48 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-03 03:08:48 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-03 03:08:48 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-03 03:08:48 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-03 03:08:48 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-03 03:08:48 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-03 03:08:48 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-03 03:08:48 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-03 03:08:49 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-03 03:08:49 (7677) [INFO] 
* 2024-09-03 03:08:51 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-03 03:08:51 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-03 03:08:51 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-03 03:08:52 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TzU2fv0gqe/ea_profile.json
* 2024-09-03 03:08:54 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TzU2fv0gqe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-03 03:08:54 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-04 03:08:38 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-04 03:08:38 (9014) [INFO] Script is up to date.
* 2024-09-04 03:08:39 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-04 03:08:39 (7647) [INFO] 
* 2024-09-04 03:08:42 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-04 03:08:42 (7647) [INFO] 
* 2024-09-04 03:08:46 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-04 03:08:46 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-04 03:08:47 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-04 03:08:47 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-04 03:08:47 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-04 03:08:47 (7647) [INFO] 
* 2024-09-04 03:08:47 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-04 03:08:47 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-04 03:08:47 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-04 03:08:47 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-04 03:08:47 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-04 03:08:47 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-04 03:08:47 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-04 03:08:47 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-04 03:08:47 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-04 03:08:47 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-04 03:08:47 (7677) [INFO] 
* 2024-09-04 03:08:50 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-04 03:08:50 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-04 03:08:51 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-04 03:08:51 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_8y2WqIcXT/ea_profile.json
* 2024-09-04 03:08:53 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_8y2WqIcXT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-04 03:08:53 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-05 03:08:35 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-05 03:08:35 (9014) [INFO] Script is up to date.
* 2024-09-05 03:08:36 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-05 03:08:36 (7647) [INFO] 
* 2024-09-05 03:08:39 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-05 03:08:39 (7647) [INFO] 
* 2024-09-05 03:08:43 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-05 03:08:43 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-05 03:08:44 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-05 03:08:44 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-05 03:08:44 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-05 03:08:44 (7647) [INFO] 
* 2024-09-05 03:08:44 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-05 03:08:44 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-05 03:08:44 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-05 03:08:44 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-05 03:08:44 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-05 03:08:44 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-05 03:08:44 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-05 03:08:44 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-05 03:08:44 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-05 03:08:44 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-05 03:08:44 (7677) [INFO] 
* 2024-09-05 03:08:47 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-05 03:08:47 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-05 03:08:47 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-05 03:08:48 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xjjMx97ZhD/ea_profile.json
* 2024-09-05 03:08:49 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xjjMx97ZhD/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-05 03:08:49 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-06 03:08:37 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-06 03:08:37 (9014) [INFO] Script is up to date.
* 2024-09-06 03:08:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-06 03:08:38 (7647) [INFO] 
* 2024-09-06 03:08:41 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-06 03:08:41 (7647) [INFO] 
* 2024-09-06 03:08:49 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-06 03:08:49 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-06 03:08:51 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-06 03:08:51 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-06 03:08:51 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-06 03:08:51 (7647) [INFO] 
* 2024-09-06 03:08:51 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-06 03:08:51 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-06 03:08:51 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-06 03:08:51 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-06 03:08:51 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-06 03:08:51 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-06 03:08:51 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-06 03:08:51 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-06 03:08:51 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-06 03:08:51 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-06 03:08:51 (7677) [INFO] 
* 2024-09-06 03:08:56 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-06 03:08:56 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-06 03:08:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-06 03:08:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1U6nK1nrGy/ea_profile.json
* 2024-09-06 03:09:02 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1U6nK1nrGy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-06 03:09:02 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-07 03:09:15 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-07 03:09:15 (9014) [INFO] Script is up to date.
* 2024-09-07 03:09:16 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-07 03:09:16 (7647) [INFO] 
* 2024-09-07 03:09:20 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-07 03:09:20 (7647) [INFO] 
* 2024-09-07 03:09:24 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-07 03:09:24 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-07 03:09:26 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-07 03:09:26 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-07 03:09:26 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-07 03:09:26 (7647) [INFO] 
* 2024-09-07 03:09:26 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-07 03:09:26 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-07 03:09:26 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-07 03:09:26 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-07 03:09:26 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-07 03:09:26 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-07 03:09:26 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-07 03:09:26 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-07 03:09:26 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-07 03:09:26 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-07 03:09:26 (7677) [INFO] 
* 2024-09-07 03:09:29 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-07 03:09:29 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-07 03:09:29 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-07 03:09:30 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NlA4tvP1OW/ea_profile.json
* 2024-09-07 03:09:32 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NlA4tvP1OW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-07 03:09:32 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-08 03:09:11 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-08 03:09:11 (9014) [INFO] Script is up to date.
* 2024-09-08 03:09:12 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-08 03:09:12 (7647) [INFO] 
* 2024-09-08 03:09:14 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-08 03:09:14 (7647) [INFO] 
* 2024-09-08 03:09:18 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-08 03:09:18 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-08 03:09:19 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-08 03:09:19 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-08 03:09:20 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-08 03:09:20 (7647) [INFO] 
* 2024-09-08 03:09:20 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-08 03:09:20 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-08 03:09:20 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-08 03:09:20 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-08 03:09:20 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-08 03:09:20 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-08 03:09:20 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-08 03:09:20 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-08 03:09:20 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-08 03:09:20 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-08 03:09:20 (7677) [INFO] 
* 2024-09-08 03:09:22 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-08 03:09:22 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-08 03:09:23 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-08 03:09:23 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i41zoFATeR/ea_profile.json
* 2024-09-08 03:09:25 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/i41zoFATeR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-08 03:09:25 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-09 03:08:39 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-09 03:08:39 (9014) [INFO] Script is up to date.
* 2024-09-09 03:08:40 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-09 03:08:40 (7647) [INFO] 
* 2024-09-09 03:08:43 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-09 03:08:43 (7647) [INFO] 
* 2024-09-09 03:08:48 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-09 03:08:48 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-09 03:08:49 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-09 03:08:49 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-09 03:08:49 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-09 03:08:49 (7647) [INFO] 
* 2024-09-09 03:08:49 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-09 03:08:49 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-09 03:08:49 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-09 03:08:49 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-09 03:08:49 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-09 03:08:49 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-09 03:08:49 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-09 03:08:49 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-09 03:08:49 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-09 03:08:49 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-09 03:08:49 (7677) [INFO] 
* 2024-09-09 03:08:53 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-09 03:08:53 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-09 03:08:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-09 03:08:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CKsKDJulLv/ea_profile.json
* 2024-09-09 03:08:55 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CKsKDJulLv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-09 03:08:55 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-10 03:08:49 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-10 03:08:49 (9014) [INFO] Script is up to date.
* 2024-09-10 03:08:50 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-10 03:08:50 (7647) [INFO] 
* 2024-09-10 03:08:53 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-10 03:08:53 (7647) [INFO] 
* 2024-09-10 03:08:58 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-10 03:08:58 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-10 03:09:00 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-10 03:09:00 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-10 03:09:00 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-10 03:09:00 (7647) [INFO] 
* 2024-09-10 03:09:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-10 03:09:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-10 03:09:00 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-10 03:09:00 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-10 03:09:00 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-10 03:09:00 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-10 03:09:00 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-10 03:09:00 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-10 03:09:00 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-10 03:09:00 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-10 03:09:00 (7677) [INFO] 
* 2024-09-10 03:09:06 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-10 03:09:06 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-10 03:09:06 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-10 03:09:07 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eAIU1e6ZOJ/ea_profile.json
* 2024-09-10 03:09:09 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eAIU1e6ZOJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-10 03:09:09 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-11 03:08:43 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-11 03:08:43 (9014) [INFO] Script is up to date.
* 2024-09-11 03:08:44 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-11 03:08:44 (7647) [INFO] 
* 2024-09-11 03:08:48 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-11 03:08:48 (7647) [INFO] 
* 2024-09-11 03:08:52 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-11 03:08:52 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-11 03:08:54 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-11 03:08:54 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-11 03:08:54 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-11 03:08:54 (7647) [INFO] 
* 2024-09-11 03:08:54 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-11 03:08:54 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-11 03:08:54 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-11 03:08:54 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-11 03:08:54 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-11 03:08:54 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-11 03:08:54 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-11 03:08:54 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-11 03:08:54 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-11 03:08:54 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-11 03:08:54 (7677) [INFO] 
* 2024-09-11 03:08:56 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-11 03:08:56 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-11 03:08:56 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-11 03:08:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TgR8Nv6c98/ea_profile.json
* 2024-09-11 03:08:59 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TgR8Nv6c98/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-11 03:08:59 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-12 03:08:59 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-12 03:08:59 (9014) [INFO] Script is up to date.
* 2024-09-12 03:09:01 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-12 03:09:01 (7647) [INFO] 
* 2024-09-12 03:09:08 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-12 03:09:08 (7647) [INFO] 
* 2024-09-12 03:09:13 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-12 03:09:13 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-12 03:09:15 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-12 03:09:15 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-12 03:09:15 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-12 03:09:15 (7647) [INFO] 
* 2024-09-12 03:09:15 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-12 03:09:15 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-12 03:09:15 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-12 03:09:15 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-12 03:09:15 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-12 03:09:15 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-12 03:09:15 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-12 03:09:15 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-12 03:09:15 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-12 03:09:15 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-12 03:09:15 (7677) [INFO] 
* 2024-09-12 03:09:20 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-12 03:09:20 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-12 03:09:20 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-12 03:09:21 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n00woPPra8/ea_profile.json
* 2024-09-12 03:09:24 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/n00woPPra8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-12 03:09:24 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-13 03:08:47 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-13 03:08:47 (9014) [INFO] Script is up to date.
* 2024-09-13 03:08:48 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-13 03:08:48 (7647) [INFO] 
* 2024-09-13 03:08:52 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-13 03:08:52 (7647) [INFO] 
* 2024-09-13 03:08:57 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-13 03:08:57 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-13 03:08:59 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-13 03:08:59 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-13 03:08:59 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-13 03:08:59 (7647) [INFO] 
* 2024-09-13 03:09:00 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-13 03:09:00 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-13 03:09:00 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-13 03:09:00 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-13 03:09:00 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-13 03:09:00 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-13 03:09:00 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-13 03:09:00 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-13 03:09:00 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-13 03:09:00 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-13 03:09:00 (7677) [INFO] 
* 2024-09-13 03:09:49 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-13 03:09:49 (1977) [ERROR] https://archive.mariadb.org/mariadb-10.6/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.6/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.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-13 03:09:49 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-13 03:09:50 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/33a7ROXs4s/ea_profile.json
* 2024-09-13 03:09:52 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/33a7ROXs4s/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-13 03:09:52 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-14 03:09:53 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-14 03:09:54 (9014) [INFO] Script is up to date.
* 2024-09-14 03:09:55 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-14 03:09:55 (7647) [INFO] 
* 2024-09-14 03:09:59 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-14 03:09:59 (7647) [INFO] 
* 2024-09-14 03:10:03 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-14 03:10:03 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-14 03:10:05 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-14 03:10:05 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-14 03:10:05 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-14 03:10:05 (7647) [INFO] 
* 2024-09-14 03:10:05 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-14 03:10:05 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-14 03:10:05 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-14 03:10:05 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-14 03:10:05 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-14 03:10:05 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-14 03:10:05 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-14 03:10:05 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-14 03:10:05 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-14 03:10:05 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-14 03:10:06 (7677) [INFO] 
* 2024-09-14 03:10:07 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-14 03:10:07 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-14 03:10:08 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-14 03:10:09 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/k8GQBlERlP/ea_profile.json
* 2024-09-14 03:10:10 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/k8GQBlERlP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-14 03:10:10 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-15 03:09:22 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-15 03:09:22 (9014) [INFO] Script is up to date.
* 2024-09-15 03:09:23 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-15 03:09:23 (7647) [INFO] 
* 2024-09-15 03:09:26 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-15 03:09:26 (7647) [INFO] 
* 2024-09-15 03:09:30 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-15 03:09:30 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-15 03:09:32 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-15 03:09:32 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-15 03:09:32 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-15 03:09:32 (7647) [INFO] 
* 2024-09-15 03:09:32 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-15 03:09:32 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-15 03:09:32 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-15 03:09:32 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-15 03:09:32 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-15 03:09:32 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-15 03:09:32 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-15 03:09:32 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-15 03:09:32 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-15 03:09:32 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-15 03:09:32 (7677) [INFO] 
* 2024-09-15 03:09:36 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-15 03:09:36 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-15 03:09:36 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-15 03:09:37 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0FhHaKvEaE/ea_profile.json
* 2024-09-15 03:09:38 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/0FhHaKvEaE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-15 03:09:38 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-16 03:08:56 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-16 03:08:56 (9014) [INFO] Script is up to date.
* 2024-09-16 03:08:57 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-16 03:08:57 (7647) [INFO] 
* 2024-09-16 03:09:02 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-16 03:09:02 (7647) [INFO] 
* 2024-09-16 03:09:07 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-16 03:09:07 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-16 03:09:10 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-16 03:09:10 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-16 03:09:10 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-16 03:09:10 (7647) [INFO] 
* 2024-09-16 03:09:10 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-16 03:09:10 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-16 03:09:10 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-16 03:09:10 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-16 03:09:10 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-16 03:09:10 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-16 03:09:10 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-16 03:09:10 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-16 03:09:10 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-16 03:09:10 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-16 03:09:10 (7677) [INFO] 
* 2024-09-16 03:09:14 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-16 03:09:14 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-16 03:09:14 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-16 03:09:15 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w5Tm5rs4Nm/ea_profile.json
* 2024-09-16 03:09:18 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w5Tm5rs4Nm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-16 03:09:18 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-17 03:08:33 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-17 03:08:33 (9014) [INFO] Script is up to date.
* 2024-09-17 03:08:34 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-17 03:08:34 (7647) [INFO] 
* 2024-09-17 03:08:36 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-17 03:08:36 (7647) [INFO] 
* 2024-09-17 03:08:40 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-17 03:08:40 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-17 03:08:41 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-17 03:08:41 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-17 03:08:41 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-17 03:08:41 (7647) [INFO] 
* 2024-09-17 03:08:42 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-17 03:08:42 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-17 03:08:42 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-17 03:08:42 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-17 03:08:42 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-17 03:08:42 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-17 03:08:42 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-17 03:08:42 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-17 03:08:42 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-17 03:08:42 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-17 03:08:42 (7677) [INFO] 
* 2024-09-17 03:08:44 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-17 03:08:44 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-17 03:08:45 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-17 03:08:45 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jjcvhLfuRf/ea_profile.json
* 2024-09-17 03:08:48 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jjcvhLfuRf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-17 03:08:48 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-18 03:08:37 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-18 03:08:37 (9014) [INFO] Script is up to date.
* 2024-09-18 03:08:38 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-18 03:08:38 (7647) [INFO] 
* 2024-09-18 03:08:39 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-18 03:08:39 (7647) [INFO] 
* 2024-09-18 03:08:43 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-18 03:08:43 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-18 03:08:45 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-18 03:08:45 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-18 03:08:45 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-18 03:08:45 (7647) [INFO] 
* 2024-09-18 03:08:45 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-18 03:08:45 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-18 03:08:45 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-18 03:08:45 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-18 03:08:45 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-18 03:08:45 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-18 03:08:45 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-18 03:08:45 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-18 03:08:45 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-18 03:08:45 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-18 03:08:45 (7677) [INFO] 
* 2024-09-18 03:08:48 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-18 03:08:48 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-18 03:08:49 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-18 03:08:49 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GOV3JIriED/ea_profile.json
* 2024-09-18 03:08:51 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GOV3JIriED/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-18 03:08:51 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-19 03:09:26 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-19 03:09:26 (9014) [INFO] Script is up to date.
* 2024-09-19 03:09:27 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-19 03:09:27 (7647) [INFO] 
* 2024-09-19 03:09:29 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-19 03:09:29 (7647) [INFO] 
* 2024-09-19 03:09:41 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-19 03:09:41 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-19 03:09:49 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-19 03:09:49 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-19 03:09:49 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-19 03:09:49 (7647) [INFO] 
* 2024-09-19 03:09:49 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-19 03:09:49 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-19 03:09:49 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-19 03:09:49 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-19 03:09:49 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-19 03:09:49 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-19 03:09:49 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-19 03:09:49 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-19 03:09:49 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-19 03:09:49 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-19 03:09:49 (7677) [INFO] 
* 2024-09-19 03:09:58 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-19 03:09:58 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-19 03:09:58 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-19 03:09:59 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TbnzBefKan/ea_profile.json
* 2024-09-19 03:10:10 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TbnzBefKan/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-19 03:10:10 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-20 03:08:40 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-20 03:08:40 (9014) [INFO] Script is up to date.
* 2024-09-20 03:08:41 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-20 03:08:41 (7647) [INFO] 
* 2024-09-20 03:08:41 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-20 03:08:41 (7647) [INFO] 
* 2024-09-20 03:08:46 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-20 03:08:46 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-20 03:08:47 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-20 03:08:47 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-20 03:08:47 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-20 03:08:47 (7647) [INFO] 
* 2024-09-20 03:08:47 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-20 03:08:47 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-20 03:08:47 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-20 03:08:48 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-20 03:08:48 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-20 03:08:48 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-20 03:08:48 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-20 03:08:48 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-20 03:08:48 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-20 03:08:48 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-20 03:08:48 (7677) [INFO] 
* 2024-09-20 03:08:53 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-20 03:08:53 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-20 03:08:53 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-20 03:08:54 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/76itOsvapP/ea_profile.json
* 2024-09-20 03:08:58 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/76itOsvapP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-20 03:08:58 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-21 03:09:18 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-21 03:09:18 (9014) [INFO] Script is up to date.
* 2024-09-21 03:09:19 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-21 03:09:19 (7647) [INFO] 
* 2024-09-21 03:09:21 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-21 03:09:21 (7647) [INFO] 
* 2024-09-21 03:09:24 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-21 03:09:24 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-21 03:09:25 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-21 03:09:25 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-21 03:09:25 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-21 03:09:25 (7647) [INFO] 
* 2024-09-21 03:09:25 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-21 03:09:25 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-21 03:09:25 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-21 03:09:25 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-21 03:09:25 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-21 03:09:25 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-21 03:09:25 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-21 03:09:25 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-21 03:09:25 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-21 03:09:25 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-21 03:09:25 (7677) [INFO] 
* 2024-09-21 03:09:27 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-21 03:09:27 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-21 03:09:28 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-21 03:09:28 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N7NGyxk4vv/ea_profile.json
* 2024-09-21 03:09:30 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N7NGyxk4vv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-21 03:09:30 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-22 03:09:31 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-22 03:09:31 (9014) [INFO] Script is up to date.
* 2024-09-22 03:09:32 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-22 03:09:32 (7647) [INFO] 
* 2024-09-22 03:09:35 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-22 03:09:35 (7647) [INFO] 
* 2024-09-22 03:09:39 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-22 03:09:39 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-22 03:09:40 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-22 03:09:40 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-22 03:09:40 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-22 03:09:40 (7647) [INFO] 
* 2024-09-22 03:09:40 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-22 03:09:41 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-22 03:09:41 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-22 03:09:41 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-22 03:09:41 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-22 03:09:41 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-22 03:09:41 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-22 03:09:41 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-22 03:09:41 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-22 03:09:41 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-22 03:09:41 (7677) [INFO] 
* 2024-09-22 03:09:43 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-22 03:09:43 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-22 03:09:44 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-22 03:09:45 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/z6beL4XFlw/ea_profile.json
* 2024-09-22 03:09:46 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/z6beL4XFlw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-22 03:09:46 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-23 03:08:41 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-23 03:08:41 (9014) [INFO] Script is up to date.
* 2024-09-23 03:08:42 (7646) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-23 03:08:42 (7647) [INFO] 
* 2024-09-23 03:08:46 (7646) [INFO] Running: /usr/bin/yum list extras
* 2024-09-23 03:08:46 (7647) [INFO] 
* 2024-09-23 03:08:51 (2083) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-23 03:08:51 (231) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-23 03:08:53 (1966) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-23 03:08:53 (1967) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-23 03:08:53 (7646) [INFO] Running: /usr/bin/yum clean all
* 2024-09-23 03:08:53 (7647) [INFO] 
* 2024-09-23 03:08:53 (7660) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-23 03:08:53 (7660) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-23 03:08:53 (7660) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-23 03:08:53 (7660) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-23 03:08:53 (7660) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-23 03:08:53 (7660) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-23 03:08:53 (7660) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-23 03:08:53 (7660) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-23 03:08:53 (7660) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-23 03:08:53 (7660) [INFO] Cleaning up list of fastest mirrors
* 2024-09-23 03:08:53 (7677) [INFO] 
* 2024-09-23 03:08:56 (1976) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-23 03:08:56 (1977) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-23 03:08:57 (995) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-23 03:08:57 (6765) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/38o71B_pNh/ea_profile.json
* 2024-09-23 03:08:59 (391) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/38o71B_pNh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6767.
* 2024-09-23 03:08:59 (355) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-24 03:08:34 (8992) [INFO] Self-update of script version 53 requested.
* 2024-09-24 03:08:34 (8997) [INFO] Newer version of script found. Downloading.
* 2024-09-24 03:08:35 (9006) [INFO] Script update to version 54 successful.
* 2024-09-24 03:08:36 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-24 03:08:36 (7667) [INFO] 
* 2024-09-24 03:08:38 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-24 03:08:38 (7667) [INFO] 
* 2024-09-24 03:08:43 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-24 03:08:43 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-24 03:08:44 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-24 03:08:44 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-24 03:08:44 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-24 03:08:44 (7667) [INFO] 
* 2024-09-24 03:08:44 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-24 03:08:44 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-24 03:08:44 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-24 03:08:44 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-24 03:08:44 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-24 03:08:44 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-24 03:08:44 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-24 03:08:44 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-24 03:08:44 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-24 03:08:44 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-24 03:08:44 (7697) [INFO] 
* 2024-09-24 03:08:48 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-24 03:08:48 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-24 03:08:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-24 03:08:49 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/K79CNQauZf/ea_profile.json
* 2024-09-24 03:08:51 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/K79CNQauZf/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-24 03:08:51 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-25 03:08:33 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-25 03:08:33 (9030) [INFO] Script is up to date.
* 2024-09-25 03:08:34 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-25 03:08:34 (7667) [INFO] 
* 2024-09-25 03:08:37 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-25 03:08:37 (7667) [INFO] 
* 2024-09-25 03:08:40 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-25 03:08:40 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-25 03:08:42 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-25 03:08:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-25 03:08:42 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-25 03:08:42 (7667) [INFO] 
* 2024-09-25 03:08:42 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-25 03:08:43 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-25 03:08:43 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-25 03:08:43 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-25 03:08:43 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-25 03:08:43 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-25 03:08:43 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-25 03:08:43 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-25 03:08:43 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-25 03:08:43 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-25 03:08:43 (7697) [INFO] 
* 2024-09-25 03:08:45 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-25 03:08:45 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-25 03:08:45 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-25 03:08:46 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TvvygE4T7v/ea_profile.json
* 2024-09-25 03:08:48 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TvvygE4T7v/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-25 03:08:48 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-26 03:08:36 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-26 03:08:36 (9030) [INFO] Script is up to date.
* 2024-09-26 03:08:37 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-26 03:08:37 (7667) [INFO] 
* 2024-09-26 03:08:40 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-26 03:08:40 (7667) [INFO] 
* 2024-09-26 03:08:44 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-26 03:08:44 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-26 03:08:45 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-26 03:08:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-26 03:08:45 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-26 03:08:45 (7667) [INFO] 
* 2024-09-26 03:08:45 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-26 03:08:45 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-26 03:08:45 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-26 03:08:45 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-26 03:08:45 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-26 03:08:45 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-26 03:08:45 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-26 03:08:45 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-26 03:08:45 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-26 03:08:45 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-26 03:08:45 (7697) [INFO] 
* 2024-09-26 03:08:47 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-26 03:08:47 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-26 03:08:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-26 03:08:48 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4cwyum058_/ea_profile.json
* 2024-09-26 03:08:49 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4cwyum058_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-26 03:08:49 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-27 03:08:35 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-27 03:08:36 (9030) [INFO] Script is up to date.
* 2024-09-27 03:08:36 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-27 03:08:36 (7667) [INFO] 
* 2024-09-27 03:08:39 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-27 03:08:39 (7667) [INFO] 
* 2024-09-27 03:08:42 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-27 03:08:42 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-27 03:08:44 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-27 03:08:44 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-27 03:08:44 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-27 03:08:44 (7667) [INFO] 
* 2024-09-27 03:08:44 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-27 03:08:44 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-27 03:08:44 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-27 03:08:44 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-27 03:08:44 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-27 03:08:44 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-27 03:08:44 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-27 03:08:44 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-27 03:08:44 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-27 03:08:44 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-27 03:08:44 (7697) [INFO] 
* 2024-09-27 03:08:48 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-27 03:08:48 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-27 03:08:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-27 03:08:49 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/26ibCuFK9A/ea_profile.json
* 2024-09-27 03:08:51 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/26ibCuFK9A/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-27 03:08:51 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-28 03:09:13 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-28 03:09:13 (9030) [INFO] Script is up to date.
* 2024-09-28 03:09:14 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-28 03:09:14 (7667) [INFO] 
* 2024-09-28 03:09:16 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-28 03:09:16 (7667) [INFO] 
* 2024-09-28 03:09:21 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-28 03:09:21 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-28 03:09:23 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-28 03:09:23 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-28 03:09:23 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-28 03:09:23 (7667) [INFO] 
* 2024-09-28 03:09:23 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-28 03:09:23 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-28 03:09:23 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-28 03:09:23 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-28 03:09:23 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-28 03:09:23 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-28 03:09:23 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-28 03:09:23 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-28 03:09:23 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-28 03:09:23 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-28 03:09:23 (7697) [INFO] 
* 2024-09-28 03:09:27 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-28 03:09:27 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-28 03:09:27 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-28 03:09:28 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/htJKccsMBL/ea_profile.json
* 2024-09-28 03:09:30 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/htJKccsMBL/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-28 03:09:30 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-29 03:09:14 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-29 03:09:14 (9030) [INFO] Script is up to date.
* 2024-09-29 03:09:15 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-29 03:09:15 (7667) [INFO] 
* 2024-09-29 03:09:17 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-29 03:09:17 (7667) [INFO] 
* 2024-09-29 03:09:23 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-29 03:09:23 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-29 03:09:24 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-29 03:09:24 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-29 03:09:24 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-29 03:09:24 (7667) [INFO] 
* 2024-09-29 03:09:24 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-29 03:09:25 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-29 03:09:25 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-29 03:09:25 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-29 03:09:25 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-29 03:09:25 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-29 03:09:25 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-29 03:09:25 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-29 03:09:25 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-29 03:09:25 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-29 03:09:25 (7697) [INFO] 
* 2024-09-29 03:09:28 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-29 03:09:28 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-29 03:09:29 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-29 03:09:29 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xhFb8Y1MY6/ea_profile.json
* 2024-09-29 03:09:31 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xhFb8Y1MY6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-29 03:09:31 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-09-30 03:08:43 (9008) [INFO] Self-update of script version 54 requested.
* 2024-09-30 03:08:43 (9030) [INFO] Script is up to date.
* 2024-09-30 03:08:44 (7666) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-09-30 03:08:44 (7667) [INFO] 
* 2024-09-30 03:08:47 (7666) [INFO] Running: /usr/bin/yum list extras
* 2024-09-30 03:08:47 (7667) [INFO] 
* 2024-09-30 03:08:52 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-09-30 03:08:52 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-09-30 03:08:54 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-30 03:08:54 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-09-30 03:08:54 (7666) [INFO] Running: /usr/bin/yum clean all
* 2024-09-30 03:08:54 (7667) [INFO] 
* 2024-09-30 03:08:54 (7680) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-09-30 03:08:54 (7680) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-09-30 03:08:54 (7680) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-09-30 03:08:54 (7680) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-09-30 03:08:54 (7680) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-09-30 03:08:54 (7680) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-09-30 03:08:54 (7680) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-09-30 03:08:54 (7680) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-09-30 03:08:54 (7680) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-09-30 03:08:54 (7680) [INFO] Cleaning up list of fastest mirrors
* 2024-09-30 03:08:54 (7697) [INFO] 
* 2024-09-30 03:08:59 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-09-30 03:08:59 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-09-30 03:08:59 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-09-30 03:09:00 (6802) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rVIevkxf7J/ea_profile.json
* 2024-09-30 03:09:05 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/rVIevkxf7J/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6804.
* 2024-09-30 03:09:05 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-01 03:08:47 (9008) [INFO] Self-update of script version 54 requested.
* 2024-10-01 03:08:47 (9013) [INFO] Newer version of script found. Downloading.
* 2024-10-01 03:08:47 (9022) [INFO] Script update to version 55 successful.
* 2024-10-01 03:08:48 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-01 03:08:48 (7668) [INFO] 
* 2024-10-01 03:08:52 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-01 03:08:52 (7668) [INFO] 
* 2024-10-01 03:08:56 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-01 03:08:56 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-01 03:08:57 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-01 03:08:57 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-01 03:08:57 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-01 03:08:57 (7668) [INFO] 
* 2024-10-01 03:08:57 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-01 03:08:57 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-01 03:08:57 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-01 03:08:57 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-01 03:08:57 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-01 03:08:57 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-01 03:08:57 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-01 03:08:57 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-01 03:08:57 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-01 03:08:57 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-01 03:08:57 (7698) [INFO] 
* 2024-10-01 03:09:00 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-01 03:09:00 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-01 03:09:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-01 03:09:01 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/H5Jh_O7BcQ/ea_profile.json
* 2024-10-01 03:09:04 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/H5Jh_O7BcQ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-01 03:09:04 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-02 03:08:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-02 03:08:37 (9031) [INFO] Script is up to date.
* 2024-10-02 03:08:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-02 03:08:38 (7668) [INFO] 
* 2024-10-02 03:08:42 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-02 03:08:42 (7668) [INFO] 
* 2024-10-02 03:08:46 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-02 03:08:46 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-02 03:08:47 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-02 03:08:47 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-02 03:08:47 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-02 03:08:47 (7668) [INFO] 
* 2024-10-02 03:08:47 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-02 03:08:47 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-02 03:08:47 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-02 03:08:47 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-02 03:08:47 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-02 03:08:47 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-02 03:08:47 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-02 03:08:47 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-02 03:08:47 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-02 03:08:47 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-02 03:08:47 (7698) [INFO] 
* 2024-10-02 03:08:50 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-02 03:08:50 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-02 03:08:51 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-02 03:08:51 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DgpICL6ExG/ea_profile.json
* 2024-10-02 03:08:53 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DgpICL6ExG/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-02 03:08:53 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-03 03:08:59 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-03 03:08:59 (9031) [INFO] Script is up to date.
* 2024-10-03 03:09:00 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-03 03:09:00 (7668) [INFO] 
* 2024-10-03 03:09:04 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-03 03:09:04 (7668) [INFO] 
* 2024-10-03 03:09:08 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-03 03:09:08 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-03 03:09:09 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-03 03:09:09 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-03 03:09:09 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-03 03:09:09 (7668) [INFO] 
* 2024-10-03 03:09:09 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-03 03:09:09 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-03 03:09:09 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-03 03:09:09 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-03 03:09:09 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-03 03:09:09 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-03 03:09:09 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-03 03:09:09 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-03 03:09:09 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-03 03:09:09 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-03 03:09:10 (7698) [INFO] 
* 2024-10-03 03:09:13 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-03 03:09:13 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-03 03:09:13 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-03 03:09:13 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N3hBD6Jho7/ea_profile.json
* 2024-10-03 03:09:15 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N3hBD6Jho7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-03 03:09:15 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-04 03:08:39 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-04 03:08:39 (9031) [INFO] Script is up to date.
* 2024-10-04 03:08:40 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-04 03:08:40 (7668) [INFO] 
* 2024-10-04 03:08:43 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-04 03:08:43 (7668) [INFO] 
* 2024-10-04 03:08:47 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-04 03:08:47 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-04 03:08:49 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-04 03:08:49 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-04 03:08:49 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-04 03:08:49 (7668) [INFO] 
* 2024-10-04 03:08:49 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-04 03:08:49 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-04 03:08:49 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-04 03:08:49 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-04 03:08:49 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-04 03:08:49 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-04 03:08:49 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-04 03:08:49 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-04 03:08:49 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-04 03:08:49 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-04 03:08:49 (7698) [INFO] 
* 2024-10-04 03:08:52 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-04 03:08:52 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-04 03:08:53 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-04 03:08:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Bu8t9WgiUO/ea_profile.json
* 2024-10-04 03:08:55 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Bu8t9WgiUO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-04 03:08:55 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-05 03:09:27 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-05 03:09:28 (9031) [INFO] Script is up to date.
* 2024-10-05 03:09:29 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-05 03:09:29 (7668) [INFO] 
* 2024-10-05 03:09:32 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-05 03:09:32 (7668) [INFO] 
* 2024-10-05 03:09:36 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-05 03:09:36 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-05 03:09:38 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-05 03:09:38 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-05 03:09:38 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-05 03:09:38 (7668) [INFO] 
* 2024-10-05 03:09:38 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-05 03:09:38 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-05 03:09:38 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-05 03:09:38 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-05 03:09:38 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-05 03:09:38 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-05 03:09:38 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-05 03:09:38 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-05 03:09:38 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-05 03:09:38 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-05 03:09:38 (7698) [INFO] 
* 2024-10-05 03:09:41 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-05 03:09:41 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-05 03:09:42 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-05 03:09:42 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2f2JbvS3q5/ea_profile.json
* 2024-10-05 03:09:44 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/2f2JbvS3q5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-05 03:09:44 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-06 03:09:19 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-06 03:09:19 (9031) [INFO] Script is up to date.
* 2024-10-06 03:09:20 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-06 03:09:20 (7668) [INFO] 
* 2024-10-06 03:09:24 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-06 03:09:24 (7668) [INFO] 
* 2024-10-06 03:09:29 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-06 03:09:29 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-06 03:09:31 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-06 03:09:31 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-06 03:09:31 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-06 03:09:31 (7668) [INFO] 
* 2024-10-06 03:09:32 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-06 03:09:32 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-06 03:09:32 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-06 03:09:32 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-06 03:09:32 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-06 03:09:32 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-06 03:09:32 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-06 03:09:32 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-06 03:09:32 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-06 03:09:32 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-06 03:09:32 (7698) [INFO] 
* 2024-10-06 03:09:36 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-06 03:09:36 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-06 03:09:36 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-06 03:09:37 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RBv7DTbLut/ea_profile.json
* 2024-10-06 03:09:41 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RBv7DTbLut/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-06 03:09:41 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-07 03:08:45 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-07 03:08:45 (9031) [INFO] Script is up to date.
* 2024-10-07 03:08:47 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-07 03:08:47 (7668) [INFO] 
* 2024-10-07 03:08:53 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-07 03:08:53 (7668) [INFO] 
* 2024-10-07 03:08:57 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-07 03:08:57 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-07 03:08:59 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-07 03:08:59 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-07 03:08:59 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-07 03:08:59 (7668) [INFO] 
* 2024-10-07 03:08:59 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-07 03:08:59 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-07 03:08:59 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-07 03:08:59 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-07 03:08:59 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-07 03:08:59 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-07 03:08:59 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-07 03:08:59 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-07 03:08:59 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-07 03:08:59 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-07 03:08:59 (7698) [INFO] 
* 2024-10-07 03:09:02 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-07 03:09:02 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-07 03:09:02 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-07 03:09:03 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Rm_drYl6CW/ea_profile.json
* 2024-10-07 03:09:04 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Rm_drYl6CW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-07 03:09:04 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-08 03:09:14 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-08 03:09:14 (9031) [INFO] Script is up to date.
* 2024-10-08 03:09:15 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-08 03:09:15 (7668) [INFO] 
* 2024-10-08 03:09:18 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-08 03:09:18 (7668) [INFO] 
* 2024-10-08 03:09:23 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-08 03:09:23 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-08 03:09:24 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-08 03:09:24 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-08 03:09:24 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-08 03:09:24 (7668) [INFO] 
* 2024-10-08 03:09:24 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-08 03:09:24 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-08 03:09:24 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-08 03:09:24 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-08 03:09:24 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-08 03:09:24 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-08 03:09:24 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-08 03:09:24 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-08 03:09:24 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-08 03:09:24 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-08 03:09:24 (7698) [INFO] 
* 2024-10-08 03:09:26 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-08 03:09:26 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-08 03:09:26 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-08 03:09:27 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Oa48LxhJgl/ea_profile.json
* 2024-10-08 03:09:29 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Oa48LxhJgl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-08 03:09:29 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-09 03:08:40 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-09 03:08:40 (9031) [INFO] Script is up to date.
* 2024-10-09 03:08:41 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-09 03:08:41 (7668) [INFO] 
* 2024-10-09 03:08:44 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-09 03:08:44 (7668) [INFO] 
* 2024-10-09 03:08:48 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-09 03:08:48 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-09 03:08:50 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-09 03:08:50 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-09 03:08:50 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-09 03:08:50 (7668) [INFO] 
* 2024-10-09 03:08:50 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-09 03:08:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-09 03:08:50 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-09 03:08:50 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-09 03:08:50 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-09 03:08:50 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-09 03:08:50 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-09 03:08:50 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-09 03:08:50 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-09 03:08:50 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-09 03:08:50 (7698) [INFO] 
* 2024-10-09 03:08:52 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-09 03:08:52 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-09 03:08:52 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-09 03:08:53 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LwK4KfqE9C/ea_profile.json
* 2024-10-09 03:08:55 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/LwK4KfqE9C/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-09 03:08:55 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-10 03:08:36 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-10 03:08:36 (9031) [INFO] Script is up to date.
* 2024-10-10 03:08:37 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-10 03:08:37 (7668) [INFO] 
* 2024-10-10 03:08:39 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-10 03:08:39 (7668) [INFO] 
* 2024-10-10 03:08:42 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-10 03:08:42 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-10 03:08:44 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-10 03:08:44 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-10 03:08:44 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-10 03:08:44 (7668) [INFO] 
* 2024-10-10 03:08:44 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-10 03:08:44 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-10 03:08:44 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-10 03:08:44 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-10 03:08:44 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-10 03:08:44 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-10 03:08:44 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-10 03:08:44 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-10 03:08:44 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-10 03:08:44 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-10 03:08:44 (7698) [INFO] 
* 2024-10-10 03:08:47 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-10 03:08:47 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-10 03:08:47 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-10 03:08:48 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TDvmbBGMD8/ea_profile.json
* 2024-10-10 03:08:50 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TDvmbBGMD8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-10 03:08:50 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-11 03:08:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-11 03:08:37 (9031) [INFO] Script is up to date.
* 2024-10-11 03:08:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-11 03:08:38 (7668) [INFO] 
* 2024-10-11 03:08:40 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-11 03:08:40 (7668) [INFO] 
* 2024-10-11 03:08:44 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-11 03:08:44 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-11 03:08:45 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-11 03:08:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-11 03:08:45 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-11 03:08:45 (7668) [INFO] 
* 2024-10-11 03:08:45 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-11 03:08:45 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-11 03:08:45 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-11 03:08:45 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-11 03:08:45 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-11 03:08:45 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-11 03:08:45 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-11 03:08:45 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-11 03:08:45 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-11 03:08:45 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-11 03:08:45 (7698) [INFO] 
* 2024-10-11 03:08:47 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-11 03:08:47 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-11 03:08:47 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-11 03:08:48 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EhbYbCTBDy/ea_profile.json
* 2024-10-11 03:08:49 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EhbYbCTBDy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-11 03:08:49 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-12 03:09:22 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-12 03:09:22 (9031) [INFO] Script is up to date.
* 2024-10-12 03:09:23 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-12 03:09:23 (7668) [INFO] 
* 2024-10-12 03:09:25 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-12 03:09:25 (7668) [INFO] 
* 2024-10-12 03:09:28 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-12 03:09:28 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-12 03:09:29 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-12 03:09:29 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-12 03:09:29 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-12 03:09:29 (7668) [INFO] 
* 2024-10-12 03:09:29 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-12 03:09:29 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-12 03:09:29 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-12 03:09:29 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-12 03:09:29 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-12 03:09:29 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-12 03:09:29 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-12 03:09:29 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-12 03:09:29 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-12 03:09:29 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-12 03:09:29 (7698) [INFO] 
* 2024-10-12 03:09:30 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-12 03:09:30 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-12 03:09:31 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-12 03:09:32 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IH8zcZQqpK/ea_profile.json
* 2024-10-12 03:09:33 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/IH8zcZQqpK/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-12 03:09:33 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-13 03:09:25 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-13 03:09:25 (9031) [INFO] Script is up to date.
* 2024-10-13 03:09:26 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-13 03:09:26 (7668) [INFO] 
* 2024-10-13 03:09:29 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-13 03:09:29 (7668) [INFO] 
* 2024-10-13 03:09:31 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-13 03:09:31 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-13 03:09:32 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-13 03:09:32 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-13 03:09:32 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-13 03:09:32 (7668) [INFO] 
* 2024-10-13 03:09:32 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-13 03:09:32 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-13 03:09:32 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-13 03:09:32 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-13 03:09:32 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-13 03:09:32 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-13 03:09:32 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-13 03:09:32 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-13 03:09:32 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-13 03:09:32 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-13 03:09:33 (7698) [INFO] 
* 2024-10-13 03:09:35 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-13 03:09:35 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-13 03:09:35 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-13 03:09:36 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y1qWRj1Zp8/ea_profile.json
* 2024-10-13 03:09:37 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y1qWRj1Zp8/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-13 03:09:37 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-14 03:08:37 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-14 03:08:37 (9031) [INFO] Script is up to date.
* 2024-10-14 03:08:38 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-14 03:08:38 (7668) [INFO] 
* 2024-10-14 03:08:40 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-14 03:08:40 (7668) [INFO] 
* 2024-10-14 03:08:43 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-14 03:08:43 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-14 03:08:45 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-14 03:08:45 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-14 03:08:45 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-14 03:08:45 (7668) [INFO] 
* 2024-10-14 03:08:45 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-14 03:08:45 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-14 03:08:45 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-14 03:08:45 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-14 03:08:45 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-14 03:08:45 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-14 03:08:45 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-14 03:08:45 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-14 03:08:45 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-14 03:08:45 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-14 03:08:45 (7698) [INFO] 
* 2024-10-14 03:08:48 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-14 03:08:48 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-14 03:08:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-14 03:08:49 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/j7M2_Gii_n/ea_profile.json
* 2024-10-14 03:08:51 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/j7M2_Gii_n/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-14 03:08:51 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-15 03:08:38 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-15 03:08:38 (9031) [INFO] Script is up to date.
* 2024-10-15 03:08:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-15 03:08:39 (7668) [INFO] 
* 2024-10-15 03:08:41 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-15 03:08:41 (7668) [INFO] 
* 2024-10-15 03:08:45 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-15 03:08:45 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-15 03:08:46 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-15 03:08:46 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-15 03:08:46 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-15 03:08:46 (7668) [INFO] 
* 2024-10-15 03:08:46 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-15 03:08:46 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-15 03:08:46 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-15 03:08:46 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-15 03:08:46 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-15 03:08:46 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-15 03:08:46 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-15 03:08:46 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-15 03:08:46 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-15 03:08:46 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-15 03:08:46 (7698) [INFO] 
* 2024-10-15 03:08:48 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-15 03:08:48 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-15 03:08:48 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-15 03:08:49 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N3W7zejhwb/ea_profile.json
* 2024-10-15 03:08:50 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/N3W7zejhwb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-15 03:08:50 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-16 03:09:59 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-16 03:09:59 (9031) [INFO] Script is up to date.
* 2024-10-16 03:10:01 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-16 03:10:01 (7668) [INFO] 
* 2024-10-16 03:10:06 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-16 03:10:06 (7668) [INFO] 
* 2024-10-16 03:10:10 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-16 03:10:10 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-16 03:10:11 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-16 03:10:11 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-16 03:10:11 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-16 03:10:11 (7668) [INFO] 
* 2024-10-16 03:10:12 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-16 03:10:12 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-16 03:10:12 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-16 03:10:12 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-16 03:10:12 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-16 03:10:12 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-16 03:10:12 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-16 03:10:12 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-16 03:10:12 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-16 03:10:12 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-16 03:10:12 (7698) [INFO] 
* 2024-10-16 03:10:13 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-16 03:10:13 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-16 03:10:14 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-16 03:10:15 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1pe8kPGMyZ/ea_profile.json
* 2024-10-16 03:10:16 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1pe8kPGMyZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-16 03:10:16 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-17 03:08:40 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-17 03:08:40 (9031) [INFO] Script is up to date.
* 2024-10-17 03:08:41 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-17 03:08:41 (7668) [INFO] 
* 2024-10-17 03:08:44 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-17 03:08:44 (7668) [INFO] 
* 2024-10-17 03:08:47 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-17 03:08:47 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-17 03:08:48 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-17 03:08:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-17 03:08:48 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-17 03:08:48 (7668) [INFO] 
* 2024-10-17 03:08:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-17 03:08:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-17 03:08:48 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-17 03:08:48 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-17 03:08:48 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-17 03:08:48 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-17 03:08:48 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-17 03:08:48 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-17 03:08:48 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-17 03:08:48 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-17 03:08:48 (7698) [INFO] 
* 2024-10-17 03:08:50 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-17 03:08:50 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-17 03:08:50 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-17 03:08:51 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qNqCV5tC4h/ea_profile.json
* 2024-10-17 03:08:52 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qNqCV5tC4h/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-17 03:08:52 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-18 03:09:08 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-18 03:09:08 (9031) [INFO] Script is up to date.
* 2024-10-18 03:09:10 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-18 03:09:10 (7668) [INFO] 
* 2024-10-18 03:09:12 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-18 03:09:12 (7668) [INFO] 
* 2024-10-18 03:09:15 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-18 03:09:15 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-18 03:09:17 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-18 03:09:17 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-18 03:09:17 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-18 03:09:17 (7668) [INFO] 
* 2024-10-18 03:09:17 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-18 03:09:17 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-18 03:09:17 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-18 03:09:17 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-18 03:09:18 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-18 03:09:18 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-18 03:09:18 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-18 03:09:18 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-18 03:09:18 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-18 03:09:18 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-18 03:09:18 (7698) [INFO] 
* 2024-10-18 03:09:20 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-18 03:09:20 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-18 03:09:21 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-18 03:09:21 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DPAlJPsCL1/ea_profile.json
* 2024-10-18 03:09:24 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DPAlJPsCL1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-18 03:09:24 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-19 03:09:04 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-19 03:09:04 (9031) [INFO] Script is up to date.
* 2024-10-19 03:09:05 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-19 03:09:05 (7668) [INFO] 
* 2024-10-19 03:09:05 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-19 03:09:05 (7668) [INFO] 
* 2024-10-19 03:09:08 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-19 03:09:08 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-19 03:09:10 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-19 03:09:10 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-19 03:09:10 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-19 03:09:10 (7668) [INFO] 
* 2024-10-19 03:09:10 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-19 03:09:10 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-19 03:09:10 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-19 03:09:10 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-19 03:09:10 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-19 03:09:10 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-19 03:09:10 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-19 03:09:10 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-19 03:09:10 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-19 03:09:10 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-19 03:09:10 (7698) [INFO] 
* 2024-10-19 03:09:12 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-19 03:09:12 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-19 03:09:13 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-19 03:09:13 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Vl_nUIxhuE/ea_profile.json
* 2024-10-19 03:09:15 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Vl_nUIxhuE/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-19 03:09:15 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-20 03:09:06 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-20 03:09:06 (9031) [INFO] Script is up to date.
* 2024-10-20 03:09:07 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-20 03:09:07 (7668) [INFO] 
* 2024-10-20 03:09:08 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-20 03:09:08 (7668) [INFO] 
* 2024-10-20 03:09:10 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-20 03:09:10 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-20 03:09:12 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-20 03:09:12 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-20 03:09:12 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-20 03:09:12 (7668) [INFO] 
* 2024-10-20 03:09:12 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-20 03:09:12 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-20 03:09:12 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-20 03:09:12 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-20 03:09:12 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-20 03:09:12 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-20 03:09:12 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-20 03:09:12 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-20 03:09:12 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-20 03:09:12 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-20 03:09:12 (7698) [INFO] 
* 2024-10-20 03:09:15 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-20 03:09:15 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-20 03:09:15 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-20 03:09:15 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mAq_nM_H48/ea_profile.json
* 2024-10-20 03:09:18 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mAq_nM_H48/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-20 03:09:18 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-21 03:08:33 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-21 03:08:33 (9031) [INFO] Script is up to date.
* 2024-10-21 03:08:34 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-21 03:08:34 (7668) [INFO] 
* 2024-10-21 03:08:37 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-21 03:08:37 (7668) [INFO] 
* 2024-10-21 03:08:40 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-21 03:08:40 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-21 03:08:42 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-21 03:08:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-21 03:08:42 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-21 03:08:42 (7668) [INFO] 
* 2024-10-21 03:08:42 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-21 03:08:42 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-21 03:08:42 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-21 03:08:42 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-21 03:08:42 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-21 03:08:42 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-21 03:08:42 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-21 03:08:42 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-21 03:08:42 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-21 03:08:42 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-21 03:08:42 (7698) [INFO] 
* 2024-10-21 03:08:44 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-21 03:08:44 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-21 03:08:44 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-21 03:08:44 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GXmEfzAiUW/ea_profile.json
* 2024-10-21 03:08:46 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/GXmEfzAiUW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-21 03:08:46 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-22 03:08:40 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-22 03:08:40 (9031) [INFO] Script is up to date.
* 2024-10-22 03:08:41 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-22 03:08:41 (7668) [INFO] 
* 2024-10-22 03:08:44 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-22 03:08:44 (7668) [INFO] 
* 2024-10-22 03:08:49 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-22 03:08:49 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-22 03:08:50 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-22 03:08:50 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-22 03:08:50 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-22 03:08:50 (7668) [INFO] 
* 2024-10-22 03:08:50 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-22 03:08:50 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-22 03:08:50 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-22 03:08:50 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-22 03:08:50 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-22 03:08:50 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-22 03:08:50 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-22 03:08:50 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-22 03:08:50 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-22 03:08:50 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-22 03:08:50 (7698) [INFO] 
* 2024-10-22 03:08:53 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-22 03:08:53 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-22 03:08:54 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-22 03:08:54 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PYlXRX_Edb/ea_profile.json
* 2024-10-22 03:08:56 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PYlXRX_Edb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-22 03:08:56 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-23 03:08:38 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-23 03:08:38 (9031) [INFO] Script is up to date.
* 2024-10-23 03:08:39 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-23 03:08:39 (7668) [INFO] 
* 2024-10-23 03:08:43 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-23 03:08:43 (7668) [INFO] 
* 2024-10-23 03:08:47 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-23 03:08:47 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-23 03:08:48 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-23 03:08:48 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-23 03:08:48 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-23 03:08:48 (7668) [INFO] 
* 2024-10-23 03:08:48 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-23 03:08:48 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-23 03:08:48 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-23 03:08:48 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-23 03:08:48 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-23 03:08:48 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-23 03:08:48 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-23 03:08:48 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-23 03:08:48 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-23 03:08:48 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-23 03:08:48 (7698) [INFO] 
* 2024-10-23 03:08:50 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-23 03:08:50 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-23 03:08:50 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-23 03:08:51 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y0cZcfnXWw/ea_profile.json
* 2024-10-23 03:08:53 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y0cZcfnXWw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-23 03:08:53 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-24 03:08:33 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-24 03:08:33 (9031) [INFO] Script is up to date.
* 2024-10-24 03:08:34 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-24 03:08:34 (7668) [INFO] 
* 2024-10-24 03:08:36 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-24 03:08:36 (7668) [INFO] 
* 2024-10-24 03:08:41 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-24 03:08:41 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-24 03:08:42 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-24 03:08:42 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-24 03:08:42 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-24 03:08:42 (7668) [INFO] 
* 2024-10-24 03:08:42 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-24 03:08:42 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-24 03:08:42 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-24 03:08:42 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-24 03:08:42 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-24 03:08:42 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-24 03:08:42 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-24 03:08:42 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-24 03:08:42 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-24 03:08:42 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-24 03:08:42 (7698) [INFO] 
* 2024-10-24 03:08:44 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-24 03:08:44 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-24 03:08:44 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-24 03:08:45 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e2fqvP2U8u/ea_profile.json
* 2024-10-24 03:08:47 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/e2fqvP2U8u/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-24 03:08:47 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-25 03:08:51 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-25 03:08:51 (9031) [INFO] Script is up to date.
* 2024-10-25 03:08:52 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-25 03:08:52 (7668) [INFO] 
* 2024-10-25 03:08:54 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-25 03:08:54 (7668) [INFO] 
* 2024-10-25 03:08:57 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-25 03:08:57 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-25 03:08:58 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-25 03:08:58 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-25 03:08:58 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-25 03:08:58 (7668) [INFO] 
* 2024-10-25 03:08:58 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-25 03:08:59 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-25 03:08:59 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-25 03:08:59 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-25 03:08:59 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-25 03:08:59 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-25 03:08:59 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-25 03:08:59 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-25 03:08:59 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-25 03:08:59 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-25 03:08:59 (7698) [INFO] 
* 2024-10-25 03:09:00 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-25 03:09:00 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-25 03:09:00 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-25 03:09:01 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KnDGzL9Rj0/ea_profile.json
* 2024-10-25 03:09:03 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/KnDGzL9Rj0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-25 03:09:03 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-26 03:09:09 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-26 03:09:09 (9031) [INFO] Script is up to date.
* 2024-10-26 03:09:10 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-26 03:09:10 (7668) [INFO] 
* 2024-10-26 03:09:13 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-26 03:09:13 (7668) [INFO] 
* 2024-10-26 03:09:15 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-26 03:09:15 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-26 03:09:17 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-26 03:09:17 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-26 03:09:17 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-26 03:09:17 (7668) [INFO] 
* 2024-10-26 03:09:17 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-26 03:09:17 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-26 03:09:17 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-26 03:09:17 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-26 03:09:17 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-26 03:09:17 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-26 03:09:17 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-26 03:09:17 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-26 03:09:17 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-26 03:09:17 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-26 03:09:17 (7698) [INFO] 
* 2024-10-26 03:09:19 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-26 03:09:19 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-26 03:09:19 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-26 03:09:19 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FvuDwDPTLb/ea_profile.json
* 2024-10-26 03:09:21 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/FvuDwDPTLb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-26 03:09:21 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-27 03:09:02 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-27 03:09:03 (9031) [INFO] Script is up to date.
* 2024-10-27 03:09:03 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-27 03:09:03 (7668) [INFO] 
* 2024-10-27 03:09:06 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-27 03:09:06 (7668) [INFO] 
* 2024-10-27 03:09:08 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-27 03:09:08 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-27 03:09:11 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-27 03:09:11 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-27 03:09:11 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-27 03:09:11 (7668) [INFO] 
* 2024-10-27 03:09:12 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-27 03:09:12 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-27 03:09:12 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-27 03:09:12 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-27 03:09:12 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-27 03:09:12 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-27 03:09:12 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-27 03:09:12 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-27 03:09:12 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-27 03:09:12 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-27 03:09:12 (7698) [INFO] 
* 2024-10-27 03:09:16 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-27 03:09:16 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-27 03:09:16 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-27 03:09:17 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w68XVzAVaz/ea_profile.json
* 2024-10-27 03:09:19 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/w68XVzAVaz/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-27 03:09:19 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-28 03:08:43 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-28 03:08:43 (9031) [INFO] Script is up to date.
* 2024-10-28 03:08:44 (7667) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-28 03:08:44 (7668) [INFO] 
* 2024-10-28 03:08:46 (7667) [INFO] Running: /usr/bin/yum list extras
* 2024-10-28 03:08:46 (7668) [INFO] 
* 2024-10-28 03:08:49 (2112) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-28 03:08:49 (230) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-28 03:08:50 (1995) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-28 03:08:50 (1996) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-28 03:08:50 (7667) [INFO] Running: /usr/bin/yum clean all
* 2024-10-28 03:08:50 (7668) [INFO] 
* 2024-10-28 03:08:51 (7681) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-28 03:08:51 (7681) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-28 03:08:51 (7681) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-28 03:08:51 (7681) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-28 03:08:51 (7681) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-28 03:08:51 (7681) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-28 03:08:51 (7681) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-28 03:08:51 (7681) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-28 03:08:51 (7681) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-28 03:08:51 (7681) [INFO] Cleaning up list of fastest mirrors
* 2024-10-28 03:08:51 (7698) [INFO] 
* 2024-10-28 03:08:53 (2005) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-28 03:08:53 (2006) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-28 03:08:53 (998) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-28 03:08:54 (6803) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kpkOMaG0EY/ea_profile.json
* 2024-10-28 03:08:55 (390) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kpkOMaG0EY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6805.
* 2024-10-28 03:08:55 (354) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-29 03:08:34 (9009) [INFO] Self-update of script version 55 requested.
* 2024-10-29 03:08:34 (9014) [INFO] Newer version of script found. Downloading.
* 2024-10-29 03:08:34 (9023) [INFO] Script update to version 56 successful.
* 2024-10-29 03:08:35 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-29 03:08:35 (7662) [INFO] 
* 2024-10-29 03:08:38 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-29 03:08:38 (7662) [INFO] 
* 2024-10-29 03:08:44 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-29 03:08:44 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-29 03:08:46 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-29 03:08:46 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-29 03:08:46 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-29 03:08:46 (7662) [INFO] 
* 2024-10-29 03:08:47 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-29 03:08:47 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-29 03:08:47 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-29 03:08:47 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-29 03:08:47 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-29 03:08:47 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-29 03:08:47 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-29 03:08:47 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-29 03:08:47 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-29 03:08:47 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-29 03:08:47 (7692) [INFO] 
* 2024-10-29 03:08:48 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-29 03:08:48 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-29 03:08:49 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-29 03:08:50 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9SpRRWR7E6/ea_profile.json
* 2024-10-29 03:08:51 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9SpRRWR7E6/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-29 03:08:51 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-30 03:08:35 (8998) [INFO] Self-update of script version 56 requested.
* 2024-10-30 03:08:35 (9020) [INFO] Script is up to date.
* 2024-10-30 03:08:36 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-30 03:08:36 (7662) [INFO] 
* 2024-10-30 03:08:40 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-30 03:08:40 (7662) [INFO] 
* 2024-10-30 03:08:45 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-30 03:08:45 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-30 03:08:47 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-30 03:08:47 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-30 03:08:47 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-30 03:08:47 (7662) [INFO] 
* 2024-10-30 03:08:47 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-30 03:08:47 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-30 03:08:47 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-30 03:08:47 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-30 03:08:47 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-30 03:08:47 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-30 03:08:47 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-30 03:08:47 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-30 03:08:47 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-30 03:08:47 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-30 03:08:47 (7692) [INFO] 
* 2024-10-30 03:08:50 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-30 03:08:50 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-30 03:08:50 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-30 03:08:51 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pcQdcAuSlh/ea_profile.json
* 2024-10-30 03:08:54 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pcQdcAuSlh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-30 03:08:54 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-10-31 03:08:39 (8998) [INFO] Self-update of script version 56 requested.
* 2024-10-31 03:08:39 (9020) [INFO] Script is up to date.
* 2024-10-31 03:08:40 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-10-31 03:08:40 (7662) [INFO] 
* 2024-10-31 03:08:44 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-10-31 03:08:44 (7662) [INFO] 
* 2024-10-31 03:09:03 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-10-31 03:09:03 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-10-31 03:09:45 (5456) [WARN] Initial run of "yum makecache" failed: https://archive.mariadb.org/mariadb-10.6/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.6/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.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-31 03:09:45 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-10-31 03:09:45 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-10-31 03:09:45 (7662) [INFO] 
* 2024-10-31 03:09:45 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-10-31 03:09:45 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-10-31 03:09:45 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-10-31 03:09:45 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-10-31 03:09:45 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-10-31 03:09:45 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-10-31 03:09:45 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-10-31 03:09:45 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-10-31 03:09:45 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-10-31 03:09:45 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-10-31 03:09:45 (7692) [INFO] 
* 2024-10-31 03:10:43 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-10-31 03:10:43 (5467) [ERROR] https://archive.mariadb.org/mariadb-10.6/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.6/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.6/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.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-10-31 03:10:44 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-10-31 03:10:44 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AuYV6gH8Ac/ea_profile.json
* 2024-10-31 03:10:53 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AuYV6gH8Ac/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-10-31 03:10:53 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-01 03:09:18 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-01 03:09:18 (9020) [INFO] Script is up to date.
* 2024-11-01 03:09:19 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-01 03:09:19 (7662) [INFO] 
* 2024-11-01 03:09:22 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-01 03:09:22 (7662) [INFO] 
* 2024-11-01 03:09:25 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-01 03:09:25 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-01 03:09:27 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-01 03:09:27 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-01 03:09:27 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-01 03:09:27 (7662) [INFO] 
* 2024-11-01 03:09:27 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-01 03:09:27 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-01 03:09:27 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-01 03:09:27 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-01 03:09:27 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-01 03:09:27 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-01 03:09:27 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-01 03:09:27 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-01 03:09:27 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-01 03:09:27 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-01 03:09:27 (7692) [INFO] 
* 2024-11-01 03:09:28 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-01 03:09:28 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-01 03:09:29 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-01 03:09:29 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y_WX8gKyUb/ea_profile.json
* 2024-11-01 03:09:31 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/y_WX8gKyUb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-01 03:09:31 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-02 03:09:36 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-02 03:09:36 (9020) [INFO] Script is up to date.
* 2024-11-02 03:09:37 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-02 03:09:37 (7662) [INFO] 
* 2024-11-02 03:09:41 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-02 03:09:41 (7662) [INFO] 
* 2024-11-02 03:09:46 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-02 03:09:46 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-02 03:09:48 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-02 03:09:48 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-02 03:09:48 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-02 03:09:48 (7662) [INFO] 
* 2024-11-02 03:09:48 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-02 03:09:48 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-02 03:09:48 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-02 03:09:48 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-02 03:09:48 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-02 03:09:48 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-02 03:09:48 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-02 03:09:48 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-02 03:09:48 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-02 03:09:48 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-02 03:09:48 (7692) [INFO] 
* 2024-11-02 03:09:50 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-02 03:09:50 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-02 03:09:51 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-02 03:09:51 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dXGbvBQGKv/ea_profile.json
* 2024-11-02 03:09:53 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/dXGbvBQGKv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-02 03:09:53 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-03 03:09:11 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-03 03:09:11 (9020) [INFO] Script is up to date.
* 2024-11-03 03:09:12 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-03 03:09:12 (7662) [INFO] 
* 2024-11-03 03:09:15 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-03 03:09:15 (7662) [INFO] 
* 2024-11-03 03:09:18 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-03 03:09:18 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-03 03:09:20 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-03 03:09:20 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-03 03:09:20 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-03 03:09:20 (7662) [INFO] 
* 2024-11-03 03:09:20 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-03 03:09:20 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-03 03:09:20 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-03 03:09:20 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-03 03:09:20 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-03 03:09:20 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-03 03:09:20 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-03 03:09:20 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-03 03:09:20 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-03 03:09:20 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-03 03:09:20 (7692) [INFO] 
* 2024-11-03 03:09:23 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-03 03:09:23 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-03 03:09:23 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-03 03:09:24 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/x6_irCiPb1/ea_profile.json
* 2024-11-03 03:09:25 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/x6_irCiPb1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-03 03:09:25 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-04 03:08:35 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-04 03:08:35 (9020) [INFO] Script is up to date.
* 2024-11-04 03:08:36 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-04 03:08:36 (7662) [INFO] 
* 2024-11-04 03:08:39 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-04 03:08:39 (7662) [INFO] 
* 2024-11-04 03:08:42 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-04 03:08:42 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-04 03:08:43 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-04 03:08:43 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-04 03:08:43 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-04 03:08:43 (7662) [INFO] 
* 2024-11-04 03:08:44 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-04 03:08:44 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-04 03:08:44 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-04 03:08:44 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-04 03:08:44 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-04 03:08:44 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-04 03:08:44 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-04 03:08:44 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-04 03:08:44 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-04 03:08:44 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-04 03:08:44 (7692) [INFO] 
* 2024-11-04 03:08:45 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-04 03:08:45 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-04 03:08:46 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-04 03:08:46 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/749bubmRS1/ea_profile.json
* 2024-11-04 03:08:48 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/749bubmRS1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-04 03:08:48 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-05 03:09:03 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-05 03:09:03 (9020) [INFO] Script is up to date.
* 2024-11-05 03:09:04 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-05 03:09:04 (7662) [INFO] 
* 2024-11-05 03:09:05 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-05 03:09:05 (7662) [INFO] 
* 2024-11-05 03:09:07 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-05 03:09:07 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-05 03:09:09 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-05 03:09:09 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-05 03:09:09 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-05 03:09:09 (7662) [INFO] 
* 2024-11-05 03:09:09 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-05 03:09:09 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-05 03:09:09 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-05 03:09:09 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-05 03:09:09 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-05 03:09:09 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-05 03:09:09 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-05 03:09:09 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-05 03:09:09 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-05 03:09:09 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-05 03:09:09 (7692) [INFO] 
* 2024-11-05 03:09:11 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-05 03:09:11 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-05 03:09:11 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-05 03:09:12 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/noY5DlfFQY/ea_profile.json
* 2024-11-05 03:09:14 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/noY5DlfFQY/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-05 03:09:14 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-06 03:08:35 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-06 03:08:36 (9020) [INFO] Script is up to date.
* 2024-11-06 03:08:37 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-06 03:08:37 (7662) [INFO] 
* 2024-11-06 03:08:39 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-06 03:08:39 (7662) [INFO] 
* 2024-11-06 03:08:42 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-06 03:08:42 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-06 03:08:42 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-06 03:08:42 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-06 03:08:42 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-06 03:08:42 (7662) [INFO] 
* 2024-11-06 03:08:42 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-06 03:08:43 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-06 03:08:43 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-06 03:08:43 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-06 03:08:43 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-06 03:08:43 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-06 03:08:43 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-06 03:08:43 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-06 03:08:43 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-06 03:08:43 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-06 03:08:43 (7692) [INFO] 
* 2024-11-06 03:08:44 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-06 03:08:44 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-06 03:08:44 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-06 03:08:45 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5WPZ_wOgvJ/ea_profile.json
* 2024-11-06 03:08:46 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/5WPZ_wOgvJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-06 03:08:46 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-07 03:08:33 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-07 03:08:33 (9020) [INFO] Script is up to date.
* 2024-11-07 03:08:34 (7661) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-07 03:08:34 (7662) [INFO] 
* 2024-11-07 03:08:36 (7661) [INFO] Running: /usr/bin/yum list extras
* 2024-11-07 03:08:36 (7662) [INFO] 
* 2024-11-07 03:08:40 (5573) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-07 03:08:40 (264) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-07 03:08:41 (5456) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-07 03:08:41 (5457) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-07 03:08:41 (7661) [INFO] Running: /usr/bin/yum clean all
* 2024-11-07 03:08:41 (7662) [INFO] 
* 2024-11-07 03:08:41 (7675) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-07 03:08:41 (7675) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-07 03:08:41 (7675) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-07 03:08:41 (7675) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-07 03:08:41 (7675) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-07 03:08:41 (7675) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-07 03:08:41 (7675) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-07 03:08:41 (7675) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-07 03:08:41 (7675) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-07 03:08:41 (7675) [INFO] Cleaning up list of fastest mirrors
* 2024-11-07 03:08:41 (7692) [INFO] 
* 2024-11-07 03:08:43 (5466) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-07 03:08:43 (5467) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-07 03:08:43 (1977) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-07 03:08:44 (6797) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QPXzoTiOfa/ea_profile.json
* 2024-11-07 03:08:45 (488) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QPXzoTiOfa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 6799.
* 2024-11-07 03:08:45 (452) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-08 03:08:36 (8998) [INFO] Self-update of script version 56 requested.
* 2024-11-08 03:08:36 (9003) [INFO] Newer version of script found. Downloading.
* 2024-11-08 03:08:37 (9012) [INFO] Script update to version 57 successful.
* 2024-11-08 03:08:38 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-08 03:08:38 (8441) [INFO] 
* 2024-11-08 03:08:38 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-08 03:08:38 (8441) [INFO] 
* 2024-11-08 03:08:39 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-08 03:08:39 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-08 03:08:39 (8471) [INFO] 
* 2024-11-08 03:08:39 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-08 03:08:39 (8441) [INFO] 
* 2024-11-08 03:08:42 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-08 03:08:42 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-08 03:08:42 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-08 03:08:42 (8441) [INFO] 
* 2024-11-08 03:08:42 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 03:08:42 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-08 03:08:42 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-08 03:08:42 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-08 03:08:42 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-08 03:08:43 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 03:08:43 (8454) [INFO] Trying other mirror.
* 2024-11-08 03:08:43 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-08 03:08:43 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 03:08:43 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 03:08:43 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-08 03:08:43 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-08 03:08:43 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-08 03:08:43 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 03:08:43 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-08 03:08:43 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-08 03:08:43 (8454) [INFO]         or
* 2024-11-08 03:08:43 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 03:08:43 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 03:08:43 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 03:08:43 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 03:08:43 (8454) [INFO]         compromise:
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-08 03:08:43 (8454) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-08 03:08:43 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 03:08:43 (8471) [INFO] 
* 2024-11-08 03:08:43 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 03:08:43 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-08 03:08:43 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-08 03:08:43 (8441) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 03:08:43 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-08 03:08:43 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-08 03:08:43 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-08 03:08:43 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-08 03:08:43 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-08 03:08:43 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-08 03:08:43 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-08 03:08:43 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-08 03:08:43 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-08 03:08:43 (8471) [INFO] 
* 2024-11-08 03:08:43 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-08 03:08:43 (8441) [INFO] 
* 2024-11-08 03:08:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-08 03:08:43 (8454) [INFO] Determining fastest mirrors
* 2024-11-08 03:08:44 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-08 03:08:44 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-08 03:08:44 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-08 03:08:45 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 03:08:45 (8454) [INFO] Trying other mirror.
* 2024-11-08 03:08:45 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-08 03:08:45 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-08 03:08:45 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-08 03:08:45 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-08 03:08:45 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-08 03:08:45 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-08 03:08:45 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-08 03:08:45 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-08 03:08:45 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-08 03:08:45 (8454) [INFO]         or
* 2024-11-08 03:08:45 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-08 03:08:45 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-08 03:08:45 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-08 03:08:45 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-08 03:08:45 (8454) [INFO]         compromise:
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-08 03:08:45 (8454) [INFO] 
* 2024-11-08 03:08:45 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-08 03:08:45 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 03:08:45 (8471) [INFO] 
* 2024-11-08 03:08:45 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-08 03:08:45 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-08 03:08:45 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-08 03:08:46 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AvmghQ3QNZ/ea_profile.json
* 2024-11-08 03:08:47 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AvmghQ3QNZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-08 03:08:47 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-09 03:09:04 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-09 03:09:04 (9513) [INFO] Script is up to date.
* 2024-11-09 03:09:05 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-09 03:09:05 (8441) [INFO] 
* 2024-11-09 03:17:38 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-09 03:17:38 (8441) [INFO] 
* 2024-11-09 03:17:39 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-09 03:17:39 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-09 03:17:39 (8471) [INFO] 
* 2024-11-09 03:17:39 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-09 03:17:39 (8441) [INFO] 
* 2024-11-09 03:17:43 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-09 03:17:43 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-09 03:17:43 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-09 03:17:43 (8441) [INFO] 
* 2024-11-09 03:17:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 03:17:43 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-09 03:17:44 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-09 03:17:44 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-09 03:17:44 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-09 03:17:44 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 03:17:44 (8454) [INFO] Trying other mirror.
* 2024-11-09 03:17:44 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-09 03:17:44 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 03:17:44 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 03:17:44 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-09 03:17:44 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-09 03:17:44 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-09 03:17:44 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 03:17:44 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-09 03:17:44 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-09 03:17:44 (8454) [INFO]         or
* 2024-11-09 03:17:44 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 03:17:44 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 03:17:44 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 03:17:44 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 03:17:44 (8454) [INFO]         compromise:
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-09 03:17:44 (8454) [INFO] 
* 2024-11-09 03:17:44 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-09 03:17:44 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 03:17:44 (8471) [INFO] 
* 2024-11-09 03:17:44 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 03:17:44 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-09 03:17:44 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-09 03:17:44 (8441) [INFO] 
* 2024-11-09 03:17:45 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 03:17:45 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-09 03:17:45 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-09 03:17:45 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-09 03:17:45 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-09 03:17:45 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-09 03:17:45 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-09 03:17:45 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-09 03:17:45 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-09 03:17:45 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-09 03:17:45 (8471) [INFO] 
* 2024-11-09 03:17:45 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-09 03:17:45 (8441) [INFO] 
* 2024-11-09 03:17:45 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-09 03:17:45 (8454) [INFO] Determining fastest mirrors
* 2024-11-09 03:17:46 (8454) [INFO]  * EA4: 185.157.208.252
* 2024-11-09 03:17:46 (8454) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-09 03:17:46 (8454) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-09 03:17:46 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 03:17:46 (8454) [INFO] Trying other mirror.
* 2024-11-09 03:17:46 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-09 03:17:46 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-09 03:17:46 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-09 03:17:46 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-09 03:17:46 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-09 03:17:46 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-09 03:17:46 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-09 03:17:46 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-09 03:17:46 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-09 03:17:46 (8454) [INFO]         or
* 2024-11-09 03:17:46 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-09 03:17:46 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-09 03:17:46 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-09 03:17:46 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-09 03:17:46 (8454) [INFO]         compromise:
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-09 03:17:46 (8454) [INFO] 
* 2024-11-09 03:17:46 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-09 03:17:46 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 03:17:46 (8471) [INFO] 
* 2024-11-09 03:17:46 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-09 03:17:46 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-09 03:17:47 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-09 03:17:47 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EP6ZUS2OoN/ea_profile.json
* 2024-11-09 03:17:49 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EP6ZUS2OoN/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-09 03:17:49 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-10 03:09:08 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-10 03:09:08 (9513) [INFO] Script is up to date.
* 2024-11-10 03:09:09 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-10 03:09:09 (8441) [INFO] 
* 2024-11-10 03:09:11 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-10 03:09:11 (8441) [INFO] 
* 2024-11-10 03:09:12 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-10 03:09:12 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-10 03:09:12 (8471) [INFO] 
* 2024-11-10 03:09:12 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-10 03:09:12 (8441) [INFO] 
* 2024-11-10 03:09:14 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-10 03:09:14 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-10 03:09:14 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-10 03:09:14 (8441) [INFO] 
* 2024-11-10 03:09:14 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 03:09:15 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-10 03:09:15 (8454) [INFO]  * EA4: 185.157.208.252
* 2024-11-10 03:09:15 (8454) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-10 03:09:15 (8454) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-10 03:09:16 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 03:09:16 (8454) [INFO] Trying other mirror.
* 2024-11-10 03:09:16 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-10 03:09:16 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 03:09:16 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 03:09:16 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-10 03:09:16 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-10 03:09:16 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-10 03:09:16 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 03:09:16 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-10 03:09:16 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-10 03:09:16 (8454) [INFO]         or
* 2024-11-10 03:09:16 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 03:09:16 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 03:09:16 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 03:09:16 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 03:09:16 (8454) [INFO]         compromise:
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-10 03:09:16 (8454) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-10 03:09:16 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 03:09:16 (8471) [INFO] 
* 2024-11-10 03:09:16 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 03:09:16 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-10 03:09:16 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-10 03:09:16 (8441) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 03:09:16 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-10 03:09:16 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-10 03:09:16 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-10 03:09:16 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-10 03:09:16 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-10 03:09:16 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-10 03:09:16 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-10 03:09:16 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-10 03:09:16 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-10 03:09:16 (8471) [INFO] 
* 2024-11-10 03:09:16 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-10 03:09:16 (8441) [INFO] 
* 2024-11-10 03:09:16 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-10 03:09:16 (8454) [INFO] Determining fastest mirrors
* 2024-11-10 03:09:19 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-10 03:09:19 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-10 03:09:19 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-10 03:09:19 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 03:09:19 (8454) [INFO] Trying other mirror.
* 2024-11-10 03:09:19 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-10 03:09:19 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-10 03:09:19 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-10 03:09:19 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-10 03:09:19 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-10 03:09:19 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-10 03:09:19 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-10 03:09:19 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-10 03:09:19 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-10 03:09:19 (8454) [INFO]         or
* 2024-11-10 03:09:19 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-10 03:09:19 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-10 03:09:19 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-10 03:09:19 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-10 03:09:19 (8454) [INFO]         compromise:
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-10 03:09:19 (8454) [INFO] 
* 2024-11-10 03:09:19 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-10 03:09:19 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 03:09:19 (8471) [INFO] 
* 2024-11-10 03:09:19 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-10 03:09:19 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-10 03:09:20 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-10 03:09:20 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SiBI64nXLx/ea_profile.json
* 2024-11-10 03:09:22 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SiBI64nXLx/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-10 03:09:22 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-11 03:08:36 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-11 03:08:36 (9513) [INFO] Script is up to date.
* 2024-11-11 03:08:37 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-11 03:08:37 (8441) [INFO] 
* 2024-11-11 03:08:39 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-11 03:08:39 (8441) [INFO] 
* 2024-11-11 03:08:40 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-11 03:08:40 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-11 03:08:40 (8471) [INFO] 
* 2024-11-11 03:08:40 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-11 03:08:40 (8441) [INFO] 
* 2024-11-11 03:08:43 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-11 03:08:43 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-11 03:08:43 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-11 03:08:43 (8441) [INFO] 
* 2024-11-11 03:08:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 03:08:43 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-11 03:08:44 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-11 03:08:44 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-11 03:08:44 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-11 03:08:44 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 03:08:44 (8454) [INFO] Trying other mirror.
* 2024-11-11 03:08:44 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-11 03:08:44 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 03:08:44 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 03:08:44 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-11 03:08:44 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-11 03:08:44 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-11 03:08:44 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 03:08:44 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-11 03:08:44 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-11 03:08:44 (8454) [INFO]         or
* 2024-11-11 03:08:44 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 03:08:44 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 03:08:44 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 03:08:44 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 03:08:44 (8454) [INFO]         compromise:
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-11 03:08:44 (8454) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-11 03:08:44 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 03:08:44 (8471) [INFO] 
* 2024-11-11 03:08:44 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 03:08:44 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-11 03:08:44 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-11 03:08:44 (8441) [INFO] 
* 2024-11-11 03:08:44 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 03:08:44 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-11 03:08:44 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-11 03:08:44 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-11 03:08:44 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-11 03:08:44 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-11 03:08:44 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-11 03:08:44 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-11 03:08:44 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-11 03:08:44 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-11 03:08:44 (8471) [INFO] 
* 2024-11-11 03:08:44 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-11 03:08:44 (8441) [INFO] 
* 2024-11-11 03:08:45 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-11 03:08:45 (8454) [INFO] Determining fastest mirrors
* 2024-11-11 03:08:46 (8454) [INFO]  * EA4: 185.157.208.252
* 2024-11-11 03:08:46 (8454) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-11 03:08:46 (8454) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-11 03:08:46 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 03:08:46 (8454) [INFO] Trying other mirror.
* 2024-11-11 03:08:46 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-11 03:08:46 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-11 03:08:46 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-11 03:08:46 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-11 03:08:46 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-11 03:08:46 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-11 03:08:46 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-11 03:08:46 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-11 03:08:46 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-11 03:08:46 (8454) [INFO]         or
* 2024-11-11 03:08:46 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-11 03:08:46 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-11 03:08:46 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-11 03:08:46 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-11 03:08:46 (8454) [INFO]         compromise:
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-11 03:08:46 (8454) [INFO] 
* 2024-11-11 03:08:46 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-11 03:08:46 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 03:08:46 (8471) [INFO] 
* 2024-11-11 03:08:46 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-11 03:08:46 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-11 03:08:46 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-11 03:08:47 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aJZv0c4AZk/ea_profile.json
* 2024-11-11 03:08:49 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aJZv0c4AZk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-11 03:08:49 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-12 03:08:40 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-12 03:08:40 (9513) [INFO] Script is up to date.
* 2024-11-12 03:08:41 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-12 03:08:41 (8441) [INFO] 
* 2024-11-12 03:08:43 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-12 03:08:43 (8441) [INFO] 
* 2024-11-12 03:08:43 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-12 03:08:43 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-12 03:08:43 (8471) [INFO] 
* 2024-11-12 03:08:43 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-12 03:08:43 (8441) [INFO] 
* 2024-11-12 03:08:47 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-12 03:08:47 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-12 03:08:47 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-12 03:08:47 (8441) [INFO] 
* 2024-11-12 03:08:47 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 03:08:47 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-12 03:08:48 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-12 03:08:48 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-12 03:08:48 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-12 03:08:49 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 03:08:49 (8454) [INFO] Trying other mirror.
* 2024-11-12 03:08:49 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-12 03:08:49 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 03:08:49 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 03:08:49 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-12 03:08:49 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-12 03:08:49 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-12 03:08:49 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 03:08:49 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-12 03:08:49 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-12 03:08:49 (8454) [INFO]         or
* 2024-11-12 03:08:49 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 03:08:49 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 03:08:49 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 03:08:49 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 03:08:49 (8454) [INFO]         compromise:
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-12 03:08:49 (8454) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-12 03:08:49 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 03:08:49 (8471) [INFO] 
* 2024-11-12 03:08:49 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 03:08:49 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-12 03:08:49 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-12 03:08:49 (8441) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 03:08:49 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-12 03:08:49 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-12 03:08:49 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-12 03:08:49 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-12 03:08:49 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-12 03:08:49 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-12 03:08:49 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-12 03:08:49 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-12 03:08:49 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-12 03:08:49 (8471) [INFO] 
* 2024-11-12 03:08:49 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-12 03:08:49 (8441) [INFO] 
* 2024-11-12 03:08:49 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-12 03:08:49 (8454) [INFO] Determining fastest mirrors
* 2024-11-12 03:08:51 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-12 03:08:51 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-12 03:08:51 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-12 03:08:52 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 03:08:52 (8454) [INFO] Trying other mirror.
* 2024-11-12 03:08:52 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-12 03:08:52 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-12 03:08:52 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-12 03:08:52 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-12 03:08:52 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-12 03:08:52 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-12 03:08:52 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-12 03:08:52 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-12 03:08:52 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-12 03:08:52 (8454) [INFO]         or
* 2024-11-12 03:08:52 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-12 03:08:52 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-12 03:08:52 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-12 03:08:52 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-12 03:08:52 (8454) [INFO]         compromise:
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-12 03:08:52 (8454) [INFO] 
* 2024-11-12 03:08:52 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-12 03:08:52 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 03:08:52 (8471) [INFO] 
* 2024-11-12 03:08:52 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-12 03:08:52 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-12 03:08:52 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-12 03:08:53 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QtmyDtPfKc/ea_profile.json
* 2024-11-12 03:08:57 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/QtmyDtPfKc/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-12 03:08:57 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-13 03:08:53 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-13 03:08:53 (9513) [INFO] Script is up to date.
* 2024-11-13 03:08:54 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-13 03:08:54 (8441) [INFO] 
* 2024-11-13 03:08:57 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-13 03:08:57 (8441) [INFO] 
* 2024-11-13 03:08:57 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-13 03:08:57 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-13 03:08:57 (8471) [INFO] 
* 2024-11-13 03:08:57 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-13 03:08:57 (8441) [INFO] 
* 2024-11-13 03:09:05 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-13 03:09:05 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-13 03:09:05 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-13 03:09:05 (8441) [INFO] 
* 2024-11-13 03:09:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 03:09:05 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-13 03:09:05 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-13 03:09:05 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-13 03:09:05 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-13 03:09:06 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-13 03:09:06 (8454) [INFO] Trying other mirror.
* 2024-11-13 03:09:06 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-13 03:09:06 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 03:09:06 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 03:09:06 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-13 03:09:06 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-13 03:09:06 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-13 03:09:06 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 03:09:06 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-13 03:09:06 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-13 03:09:06 (8454) [INFO]         or
* 2024-11-13 03:09:06 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 03:09:06 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 03:09:06 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 03:09:06 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 03:09:06 (8454) [INFO]         compromise:
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-13 03:09:06 (8454) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-13 03:09:06 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-13 03:09:06 (8471) [INFO] 
* 2024-11-13 03:09:06 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-13 03:09:06 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-13 03:09:06 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-13 03:09:06 (8441) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 03:09:06 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-13 03:09:06 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-13 03:09:06 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-13 03:09:06 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-13 03:09:06 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-13 03:09:06 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-13 03:09:06 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-13 03:09:06 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-13 03:09:06 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-13 03:09:06 (8471) [INFO] 
* 2024-11-13 03:09:06 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-13 03:09:06 (8441) [INFO] 
* 2024-11-13 03:09:06 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-13 03:09:07 (8454) [INFO] Determining fastest mirrors
* 2024-11-13 03:09:09 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-13 03:09:09 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-13 03:09:09 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-13 03:09:09 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-13 03:09:09 (8454) [INFO] Trying other mirror.
* 2024-11-13 03:09:09 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-13 03:09:09 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-13 03:09:09 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-13 03:09:09 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-13 03:09:09 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-13 03:09:09 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-13 03:09:09 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-13 03:09:09 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-13 03:09:09 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-13 03:09:09 (8454) [INFO]         or
* 2024-11-13 03:09:09 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-13 03:09:09 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-13 03:09:09 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-13 03:09:09 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-13 03:09:09 (8454) [INFO]         compromise:
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-13 03:09:09 (8454) [INFO] 
* 2024-11-13 03:09:09 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-13 03:09:09 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-13 03:09:09 (8471) [INFO] 
* 2024-11-13 03:09:09 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-13 03:09:09 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-13 03:09:10 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-13 03:09:10 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uGQAPGF6lW/ea_profile.json
* 2024-11-13 03:09:13 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/uGQAPGF6lW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-13 03:09:13 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-14 03:08:47 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-14 03:08:47 (9513) [INFO] Script is up to date.
* 2024-11-14 03:08:49 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-14 03:08:49 (8441) [INFO] 
* 2024-11-14 03:08:53 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-14 03:08:53 (8441) [INFO] 
* 2024-11-14 03:08:54 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-14 03:08:54 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-14 03:08:54 (8471) [INFO] 
* 2024-11-14 03:08:54 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-14 03:08:54 (8441) [INFO] 
* 2024-11-14 03:09:01 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-14 03:09:01 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-14 03:09:01 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-14 03:09:01 (8441) [INFO] 
* 2024-11-14 03:09:01 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 03:09:02 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-14 03:09:04 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-14 03:09:04 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-14 03:09:04 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-14 03:09:04 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 03:09:04 (8454) [INFO] Trying other mirror.
* 2024-11-14 03:09:04 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-14 03:09:04 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 03:09:04 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 03:09:04 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-14 03:09:04 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-14 03:09:04 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-14 03:09:04 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 03:09:04 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-14 03:09:04 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-14 03:09:04 (8454) [INFO]         or
* 2024-11-14 03:09:04 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 03:09:04 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 03:09:04 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 03:09:04 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 03:09:04 (8454) [INFO]         compromise:
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-14 03:09:04 (8454) [INFO] 
* 2024-11-14 03:09:04 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-14 03:09:04 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 03:09:04 (8471) [INFO] 
* 2024-11-14 03:09:04 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 03:09:04 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-14 03:09:04 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-14 03:09:04 (8441) [INFO] 
* 2024-11-14 03:09:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 03:09:05 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-14 03:09:05 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-14 03:09:05 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-14 03:09:05 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-14 03:09:05 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-14 03:09:05 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-14 03:09:05 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-14 03:09:05 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-14 03:09:05 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-14 03:09:05 (8471) [INFO] 
* 2024-11-14 03:09:05 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-14 03:09:05 (8441) [INFO] 
* 2024-11-14 03:09:05 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-14 03:09:05 (8454) [INFO] Determining fastest mirrors
* 2024-11-14 03:09:10 (8454) [INFO]  * EA4: 31.22.112.31
* 2024-11-14 03:09:10 (8454) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-14 03:09:10 (8454) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-14 03:09:10 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 03:09:10 (8454) [INFO] Trying other mirror.
* 2024-11-14 03:09:10 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-14 03:09:10 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-14 03:09:10 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-14 03:09:10 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-14 03:09:10 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-14 03:09:10 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-14 03:09:10 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-14 03:09:10 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-14 03:09:10 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-14 03:09:10 (8454) [INFO]         or
* 2024-11-14 03:09:10 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-14 03:09:10 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-14 03:09:10 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-14 03:09:10 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-14 03:09:10 (8454) [INFO]         compromise:
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-14 03:09:10 (8454) [INFO] 
* 2024-11-14 03:09:10 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-14 03:09:10 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 03:09:10 (8471) [INFO] 
* 2024-11-14 03:09:10 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-14 03:09:10 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-14 03:09:11 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-14 03:09:12 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sXh7k8m8yF/ea_profile.json
* 2024-11-14 03:09:29 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/sXh7k8m8yF/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-14 03:09:29 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-15 03:08:39 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-15 03:08:39 (9513) [INFO] Script is up to date.
* 2024-11-15 03:08:40 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-15 03:08:40 (8441) [INFO] 
* 2024-11-15 03:08:43 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-15 03:08:43 (8441) [INFO] 
* 2024-11-15 03:08:43 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-15 03:08:43 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-15 03:08:43 (8471) [INFO] 
* 2024-11-15 03:08:43 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-15 03:08:43 (8441) [INFO] 
* 2024-11-15 03:08:48 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-15 03:08:48 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-15 03:08:48 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-15 03:08:48 (8441) [INFO] 
* 2024-11-15 03:08:48 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 03:08:48 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-15 03:08:49 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-15 03:08:49 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-15 03:08:49 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-15 03:08:49 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 03:08:49 (8454) [INFO] Trying other mirror.
* 2024-11-15 03:08:49 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-15 03:08:49 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 03:08:49 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 03:08:49 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-15 03:08:49 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-15 03:08:49 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-15 03:08:49 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 03:08:49 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-15 03:08:49 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-15 03:08:49 (8454) [INFO]         or
* 2024-11-15 03:08:49 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 03:08:49 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 03:08:49 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 03:08:49 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 03:08:49 (8454) [INFO]         compromise:
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-15 03:08:49 (8454) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-15 03:08:49 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 03:08:49 (8471) [INFO] 
* 2024-11-15 03:08:49 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 03:08:49 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-15 03:08:49 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-15 03:08:49 (8441) [INFO] 
* 2024-11-15 03:08:49 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 03:08:50 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-15 03:08:50 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-15 03:08:50 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-15 03:08:50 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-15 03:08:50 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-15 03:08:50 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-15 03:08:50 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-15 03:08:50 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-15 03:08:50 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-15 03:08:50 (8471) [INFO] 
* 2024-11-15 03:08:50 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-15 03:08:50 (8441) [INFO] 
* 2024-11-15 03:08:50 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-15 03:08:50 (8454) [INFO] Determining fastest mirrors
* 2024-11-15 03:08:51 (8454) [INFO]  * EA4: 31.22.112.31
* 2024-11-15 03:08:51 (8454) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-15 03:08:51 (8454) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-15 03:08:52 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 03:08:52 (8454) [INFO] Trying other mirror.
* 2024-11-15 03:08:52 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-15 03:08:52 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-15 03:08:52 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-15 03:08:52 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-15 03:08:52 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-15 03:08:52 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-15 03:08:52 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-15 03:08:52 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-15 03:08:52 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-15 03:08:52 (8454) [INFO]         or
* 2024-11-15 03:08:52 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-15 03:08:52 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-15 03:08:52 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-15 03:08:52 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-15 03:08:52 (8454) [INFO]         compromise:
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-15 03:08:52 (8454) [INFO] 
* 2024-11-15 03:08:52 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-15 03:08:52 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 03:08:52 (8471) [INFO] 
* 2024-11-15 03:08:52 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-15 03:08:52 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-15 03:08:52 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-15 03:08:53 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aQ2q4mKkMb/ea_profile.json
* 2024-11-15 03:08:55 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/aQ2q4mKkMb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-15 03:08:55 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-16 03:09:19 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-16 03:09:19 (9513) [INFO] Script is up to date.
* 2024-11-16 03:09:20 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-16 03:09:20 (8441) [INFO] 
* 2024-11-16 03:09:22 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-16 03:09:22 (8441) [INFO] 
* 2024-11-16 03:09:23 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-16 03:09:23 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-16 03:09:23 (8471) [INFO] 
* 2024-11-16 03:09:23 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-16 03:09:23 (8441) [INFO] 
* 2024-11-16 03:09:25 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-16 03:09:25 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-16 03:09:25 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-16 03:09:25 (8441) [INFO] 
* 2024-11-16 03:09:25 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 03:09:26 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-16 03:09:26 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-16 03:09:26 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-16 03:09:26 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-16 03:09:27 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 03:09:27 (8454) [INFO] Trying other mirror.
* 2024-11-16 03:09:27 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-16 03:09:27 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 03:09:27 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 03:09:27 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-16 03:09:27 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-16 03:09:27 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-16 03:09:27 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 03:09:27 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-16 03:09:27 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-16 03:09:27 (8454) [INFO]         or
* 2024-11-16 03:09:27 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 03:09:27 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 03:09:27 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 03:09:27 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 03:09:27 (8454) [INFO]         compromise:
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-16 03:09:27 (8454) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-16 03:09:27 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 03:09:27 (8471) [INFO] 
* 2024-11-16 03:09:27 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 03:09:27 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-16 03:09:27 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-16 03:09:27 (8441) [INFO] 
* 2024-11-16 03:09:27 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 03:09:27 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-16 03:09:27 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-16 03:09:27 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-16 03:09:27 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-16 03:09:27 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-16 03:09:27 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-16 03:09:27 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-16 03:09:27 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-16 03:09:27 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-16 03:09:27 (8471) [INFO] 
* 2024-11-16 03:09:27 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-16 03:09:27 (8441) [INFO] 
* 2024-11-16 03:09:28 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-16 03:09:28 (8454) [INFO] Determining fastest mirrors
* 2024-11-16 03:09:29 (8454) [INFO]  * EA4: 185.157.208.252
* 2024-11-16 03:09:29 (8454) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-16 03:09:29 (8454) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-16 03:09:30 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 03:09:30 (8454) [INFO] Trying other mirror.
* 2024-11-16 03:09:30 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-16 03:09:30 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-16 03:09:30 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-16 03:09:30 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-16 03:09:30 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-16 03:09:30 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-16 03:09:30 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-16 03:09:30 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-16 03:09:30 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-16 03:09:30 (8454) [INFO]         or
* 2024-11-16 03:09:30 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-16 03:09:30 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-16 03:09:30 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-16 03:09:30 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-16 03:09:30 (8454) [INFO]         compromise:
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-16 03:09:30 (8454) [INFO] 
* 2024-11-16 03:09:30 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-16 03:09:30 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 03:09:30 (8471) [INFO] 
* 2024-11-16 03:09:30 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-16 03:09:30 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-16 03:09:30 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-16 03:09:31 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oty1C4Thk0/ea_profile.json
* 2024-11-16 03:09:33 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/oty1C4Thk0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-16 03:09:33 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-17 03:11:04 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-17 03:11:04 (9513) [INFO] Script is up to date.
* 2024-11-17 03:11:07 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-17 03:11:07 (8441) [INFO] 
* 2024-11-17 03:11:17 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-17 03:11:17 (8441) [INFO] 
* 2024-11-17 03:11:17 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-17 03:11:17 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-17 03:11:17 (8471) [INFO] 
* 2024-11-17 03:11:17 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-17 03:11:17 (8441) [INFO] 
* 2024-11-17 03:11:26 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-17 03:11:26 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-17 03:11:26 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-17 03:11:26 (8441) [INFO] 
* 2024-11-17 03:11:27 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 03:11:27 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-17 03:11:28 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-17 03:11:28 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-17 03:11:28 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-17 03:11:29 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 03:11:29 (8454) [INFO] Trying other mirror.
* 2024-11-17 03:11:29 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-17 03:11:29 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 03:11:29 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 03:11:29 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-17 03:11:29 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-17 03:11:29 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-17 03:11:29 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 03:11:29 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-17 03:11:29 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-17 03:11:29 (8454) [INFO]         or
* 2024-11-17 03:11:29 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 03:11:29 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 03:11:29 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 03:11:29 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 03:11:29 (8454) [INFO]         compromise:
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-17 03:11:29 (8454) [INFO] 
* 2024-11-17 03:11:29 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-17 03:11:29 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 03:11:29 (8471) [INFO] 
* 2024-11-17 03:11:29 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 03:11:29 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-17 03:11:29 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-17 03:11:29 (8441) [INFO] 
* 2024-11-17 03:11:30 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 03:11:31 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-17 03:11:31 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-17 03:11:31 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-17 03:11:31 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-17 03:11:31 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-17 03:11:31 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-17 03:11:31 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-17 03:11:31 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-17 03:11:31 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-17 03:11:31 (8471) [INFO] 
* 2024-11-17 03:11:31 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-17 03:11:31 (8441) [INFO] 
* 2024-11-17 03:11:31 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-17 03:11:31 (8454) [INFO] Determining fastest mirrors
* 2024-11-17 03:11:34 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-17 03:11:34 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-17 03:11:34 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-17 03:11:35 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 03:11:35 (8454) [INFO] Trying other mirror.
* 2024-11-17 03:11:35 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-17 03:11:35 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-17 03:11:35 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-17 03:11:35 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-17 03:11:35 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-17 03:11:35 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-17 03:11:35 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-17 03:11:35 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-17 03:11:35 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-17 03:11:35 (8454) [INFO]         or
* 2024-11-17 03:11:35 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-17 03:11:35 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-17 03:11:35 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-17 03:11:35 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-17 03:11:35 (8454) [INFO]         compromise:
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-17 03:11:35 (8454) [INFO] 
* 2024-11-17 03:11:35 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-17 03:11:35 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 03:11:35 (8471) [INFO] 
* 2024-11-17 03:11:35 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-17 03:11:35 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-17 03:11:36 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-17 03:11:38 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NAmAoDQyp7/ea_profile.json
* 2024-11-17 03:11:41 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NAmAoDQyp7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-17 03:11:41 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-18 03:08:34 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-18 03:08:35 (9513) [INFO] Script is up to date.
* 2024-11-18 03:08:36 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-18 03:08:36 (8441) [INFO] 
* 2024-11-18 03:08:38 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-18 03:08:38 (8441) [INFO] 
* 2024-11-18 03:08:39 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-18 03:08:39 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-18 03:08:39 (8471) [INFO] 
* 2024-11-18 03:08:39 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-18 03:08:39 (8441) [INFO] 
* 2024-11-18 03:08:43 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-18 03:08:43 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-18 03:08:43 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-18 03:08:43 (8441) [INFO] 
* 2024-11-18 03:08:43 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 03:08:43 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-18 03:08:43 (8454) [INFO]  * EA4: 185.157.208.252
* 2024-11-18 03:08:43 (8454) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-18 03:08:43 (8454) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-18 03:08:44 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 03:08:44 (8454) [INFO] Trying other mirror.
* 2024-11-18 03:08:44 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-18 03:08:44 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 03:08:44 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 03:08:44 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-18 03:08:44 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-18 03:08:44 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-18 03:08:44 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 03:08:44 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-18 03:08:44 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-18 03:08:44 (8454) [INFO]         or
* 2024-11-18 03:08:44 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 03:08:44 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 03:08:44 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 03:08:44 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 03:08:44 (8454) [INFO]         compromise:
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-18 03:08:44 (8454) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-18 03:08:44 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 03:08:44 (8471) [INFO] 
* 2024-11-18 03:08:44 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 03:08:44 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-18 03:08:44 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-18 03:08:44 (8441) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 03:08:44 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-18 03:08:44 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-18 03:08:44 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-18 03:08:44 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-18 03:08:44 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-18 03:08:44 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-18 03:08:44 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-18 03:08:44 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-18 03:08:44 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-18 03:08:44 (8471) [INFO] 
* 2024-11-18 03:08:44 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-18 03:08:44 (8441) [INFO] 
* 2024-11-18 03:08:44 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-18 03:08:44 (8454) [INFO] Determining fastest mirrors
* 2024-11-18 03:08:47 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-18 03:08:47 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-18 03:08:47 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-18 03:08:47 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 03:08:47 (8454) [INFO] Trying other mirror.
* 2024-11-18 03:08:47 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-18 03:08:47 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-18 03:08:47 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-18 03:08:47 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-18 03:08:47 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-18 03:08:47 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-18 03:08:47 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-18 03:08:47 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-18 03:08:47 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-18 03:08:47 (8454) [INFO]         or
* 2024-11-18 03:08:47 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-18 03:08:47 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-18 03:08:47 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-18 03:08:47 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-18 03:08:47 (8454) [INFO]         compromise:
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-18 03:08:47 (8454) [INFO] 
* 2024-11-18 03:08:47 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-18 03:08:47 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 03:08:47 (8471) [INFO] 
* 2024-11-18 03:08:47 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-18 03:08:47 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-18 03:08:47 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-18 03:08:48 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TZu37jlV2j/ea_profile.json
* 2024-11-18 03:08:49 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TZu37jlV2j/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-18 03:08:49 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-19 03:08:48 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-19 03:08:48 (9513) [INFO] Script is up to date.
* 2024-11-19 03:08:49 (8440) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-19 03:08:49 (8441) [INFO] 
* 2024-11-19 03:08:53 (8440) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-19 03:08:53 (8441) [INFO] 
* 2024-11-19 03:08:53 (8454) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-19 03:08:53 (8454) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-19 03:08:53 (8471) [INFO] 
* 2024-11-19 03:08:53 (8440) [INFO] Running: /usr/bin/yum list extras
* 2024-11-19 03:08:53 (8441) [INFO] 
* 2024-11-19 03:08:57 (5624) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-19 03:08:57 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-19 03:08:57 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-19 03:08:57 (8441) [INFO] 
* 2024-11-19 03:08:57 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 03:08:57 (8454) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-19 03:08:58 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-19 03:08:58 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-19 03:08:58 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-19 03:08:58 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 03:08:58 (8454) [INFO] Trying other mirror.
* 2024-11-19 03:08:58 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-19 03:08:58 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 03:08:58 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 03:08:58 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-19 03:08:58 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-19 03:08:58 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-19 03:08:58 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 03:08:58 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-19 03:08:58 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-19 03:08:58 (8454) [INFO]         or
* 2024-11-19 03:08:58 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 03:08:58 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 03:08:58 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 03:08:58 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 03:08:58 (8454) [INFO]         compromise:
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-19 03:08:58 (8454) [INFO] 
* 2024-11-19 03:08:58 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-19 03:08:58 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 03:08:58 (8471) [INFO] 
* 2024-11-19 03:08:58 (5507) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 03:08:58 (5508) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-19 03:08:58 (8440) [INFO] Running: /usr/bin/yum clean all
* 2024-11-19 03:08:58 (8441) [INFO] 
* 2024-11-19 03:08:59 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 03:08:59 (8454) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-19 03:08:59 (8454) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-19 03:08:59 (8454) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-19 03:08:59 (8454) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-19 03:08:59 (8454) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-19 03:08:59 (8454) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-19 03:08:59 (8454) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-19 03:08:59 (8454) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-19 03:08:59 (8454) [INFO] Cleaning up list of fastest mirrors
* 2024-11-19 03:08:59 (8471) [INFO] 
* 2024-11-19 03:08:59 (8440) [INFO] Running: /usr/bin/yum makecache
* 2024-11-19 03:08:59 (8441) [INFO] 
* 2024-11-19 03:08:59 (8454) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-19 03:08:59 (8454) [INFO] Determining fastest mirrors
* 2024-11-19 03:09:00 (8454) [INFO]  * EA4: 185.15.22.168
* 2024-11-19 03:09:00 (8454) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-19 03:09:00 (8454) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-19 03:09:00 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 03:09:00 (8454) [INFO] Trying other mirror.
* 2024-11-19 03:09:00 (8454) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-19 03:09:00 (8454) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-19 03:09:00 (8454) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-19 03:09:00 (8454) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-19 03:09:00 (8454) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-19 03:09:00 (8454) [INFO]         packages for the previous distribution release still work).
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-19 03:09:00 (8454) [INFO]             yum --disablerepo=base ...
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-19 03:09:00 (8454) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-19 03:09:00 (8454) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]             yum-config-manager --disable base
* 2024-11-19 03:09:00 (8454) [INFO]         or
* 2024-11-19 03:09:00 (8454) [INFO]             subscription-manager repos --disable=base
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-19 03:09:00 (8454) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-19 03:09:00 (8454) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-19 03:09:00 (8454) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-19 03:09:00 (8454) [INFO]         compromise:
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-19 03:09:00 (8454) [INFO] 
* 2024-11-19 03:09:00 (8454) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-19 03:09:00 (8454) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 03:09:00 (8471) [INFO] 
* 2024-11-19 03:09:00 (5517) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-19 03:09:00 (5518) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-19 03:09:02 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-19 03:09:02 (7581) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ibMoK0XdEe/ea_profile.json
* 2024-11-19 03:09:04 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ibMoK0XdEe/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7583.
* 2024-11-19 03:09:04 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-20 03:08:39 (9491) [INFO] Self-update of script version 57 requested.
* 2024-11-20 03:08:39 (9496) [INFO] Newer version of script found. Downloading.
* 2024-11-20 03:08:40 (9505) [INFO] Script update to version 58 successful.
* 2024-11-20 03:08:41 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-20 03:08:41 (8445) [INFO] 
* 2024-11-20 03:08:42 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-20 03:08:42 (8445) [INFO] 
* 2024-11-20 03:08:42 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-20 03:08:42 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-20 03:08:42 (8475) [INFO] 
* 2024-11-20 03:08:42 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-20 03:08:42 (8445) [INFO] 
* 2024-11-20 03:08:46 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-20 03:08:46 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-20 03:08:46 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 03:08:46 (8445) [INFO] 
* 2024-11-20 03:08:46 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 03:08:46 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-20 03:08:47 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-20 03:08:47 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-20 03:08:47 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-20 03:08:47 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 03:08:47 (8458) [INFO] Trying other mirror.
* 2024-11-20 03:08:47 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-20 03:08:47 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 03:08:47 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 03:08:47 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 03:08:47 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 03:08:47 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 03:08:47 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 03:08:47 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 03:08:47 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-20 03:08:47 (8458) [INFO]         or
* 2024-11-20 03:08:47 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 03:08:47 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 03:08:47 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 03:08:47 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 03:08:47 (8458) [INFO]         compromise:
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-20 03:08:47 (8458) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-20 03:08:47 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 03:08:47 (8475) [INFO] 
* 2024-11-20 03:08:47 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 03:08:47 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-20 03:08:47 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-20 03:08:47 (8445) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 03:08:47 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-20 03:08:47 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-20 03:08:47 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-20 03:08:47 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-20 03:08:47 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-20 03:08:47 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-20 03:08:47 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-20 03:08:47 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-20 03:08:47 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-20 03:08:47 (8475) [INFO] 
* 2024-11-20 03:08:47 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-20 03:08:47 (8445) [INFO] 
* 2024-11-20 03:08:47 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-20 03:08:48 (8458) [INFO] Determining fastest mirrors
* 2024-11-20 03:08:49 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-20 03:08:49 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-20 03:08:49 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-20 03:08:49 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 03:08:49 (8458) [INFO] Trying other mirror.
* 2024-11-20 03:08:49 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-20 03:08:49 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-20 03:08:49 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-20 03:08:49 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-20 03:08:49 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-20 03:08:49 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-20 03:08:49 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-20 03:08:49 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-20 03:08:49 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-20 03:08:49 (8458) [INFO]         or
* 2024-11-20 03:08:49 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-20 03:08:49 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-20 03:08:49 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-20 03:08:49 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-20 03:08:49 (8458) [INFO]         compromise:
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-20 03:08:49 (8458) [INFO] 
* 2024-11-20 03:08:49 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-20 03:08:49 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 03:08:49 (8475) [INFO] 
* 2024-11-20 03:08:49 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-20 03:08:49 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-20 03:08:49 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-20 03:08:50 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_i2nAH94ZS/ea_profile.json
* 2024-11-20 03:08:52 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/_i2nAH94ZS/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-20 03:08:52 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-21 00:17:17 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-21 00:17:17 (9517) [INFO] Script is up to date.
* 2024-11-21 00:17:18 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-21 00:17:18 (8445) [INFO] 
* 2024-11-21 00:17:21 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-21 00:17:21 (8445) [INFO] 
* 2024-11-21 00:17:22 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-21 00:17:22 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 00:17:22 (8475) [INFO] 
* 2024-11-21 00:17:22 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-21 00:17:22 (8445) [INFO] 
* 2024-11-21 00:17:27 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-21 00:17:27 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-21 00:17:27 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 00:17:27 (8445) [INFO] 
* 2024-11-21 00:17:27 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 00:17:27 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-21 00:17:27 (8458) [INFO]  * EA4: 185.157.208.252
* 2024-11-21 00:17:27 (8458) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-21 00:17:27 (8458) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-21 00:17:28 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 00:17:28 (8458) [INFO] Trying other mirror.
* 2024-11-21 00:17:28 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-21 00:17:28 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 00:17:28 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 00:17:28 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 00:17:28 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 00:17:28 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 00:17:28 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 00:17:28 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 00:17:28 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-21 00:17:28 (8458) [INFO]         or
* 2024-11-21 00:17:28 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 00:17:28 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 00:17:28 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 00:17:28 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 00:17:28 (8458) [INFO]         compromise:
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-21 00:17:28 (8458) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-21 00:17:28 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 00:17:28 (8475) [INFO] 
* 2024-11-21 00:17:28 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 00:17:28 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-21 00:17:28 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-21 00:17:28 (8445) [INFO] 
* 2024-11-21 00:17:28 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 00:17:28 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-21 00:17:28 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-21 00:17:28 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-21 00:17:28 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-21 00:17:28 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-21 00:17:28 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-21 00:17:28 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-21 00:17:28 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-21 00:17:28 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-21 00:17:28 (8475) [INFO] 
* 2024-11-21 00:17:28 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 00:17:28 (8445) [INFO] 
* 2024-11-21 00:17:29 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 00:17:29 (8458) [INFO] Determining fastest mirrors
* 2024-11-21 00:17:31 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-21 00:17:31 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-21 00:17:31 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-21 00:17:32 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 00:17:32 (8458) [INFO] Trying other mirror.
* 2024-11-21 00:17:32 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-21 00:17:32 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 00:17:32 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 00:17:32 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 00:17:32 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 00:17:32 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 00:17:32 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 00:17:32 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 00:17:32 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-21 00:17:32 (8458) [INFO]         or
* 2024-11-21 00:17:32 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 00:17:32 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 00:17:32 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 00:17:32 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 00:17:32 (8458) [INFO]         compromise:
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-21 00:17:32 (8458) [INFO] 
* 2024-11-21 00:17:32 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-21 00:17:32 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 00:17:32 (8475) [INFO] 
* 2024-11-21 00:17:32 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-21 00:17:32 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 00:17:32 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-21 00:17:33 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RQfIWvjib_/ea_profile.json
* 2024-11-21 00:17:34 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RQfIWvjib_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-21 00:17:34 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-21 03:08:40 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-21 03:08:40 (9517) [INFO] Script is up to date.
* 2024-11-21 03:08:41 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-21 03:08:41 (8445) [INFO] 
* 2024-11-21 03:08:45 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-21 03:08:45 (8445) [INFO] 
* 2024-11-21 03:08:45 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-21 03:08:45 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-21 03:08:45 (8475) [INFO] 
* 2024-11-21 03:08:45 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-21 03:08:45 (8445) [INFO] 
* 2024-11-21 03:08:49 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-21 03:08:49 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-21 03:08:49 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 03:08:49 (8445) [INFO] 
* 2024-11-21 03:08:49 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 03:08:50 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-21 03:08:50 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-21 03:08:50 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-21 03:08:50 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-21 03:08:51 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 03:08:51 (8458) [INFO] Trying other mirror.
* 2024-11-21 03:08:51 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-21 03:08:51 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 03:08:51 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 03:08:51 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 03:08:51 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 03:08:51 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 03:08:51 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 03:08:51 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 03:08:51 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-21 03:08:51 (8458) [INFO]         or
* 2024-11-21 03:08:51 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 03:08:51 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 03:08:51 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 03:08:51 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 03:08:51 (8458) [INFO]         compromise:
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-21 03:08:51 (8458) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-21 03:08:51 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 03:08:51 (8475) [INFO] 
* 2024-11-21 03:08:51 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 03:08:51 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-21 03:08:51 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-21 03:08:51 (8445) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 03:08:51 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-21 03:08:51 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-21 03:08:51 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-21 03:08:51 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-21 03:08:51 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-21 03:08:51 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-21 03:08:51 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-21 03:08:51 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-21 03:08:51 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-21 03:08:51 (8475) [INFO] 
* 2024-11-21 03:08:51 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-21 03:08:51 (8445) [INFO] 
* 2024-11-21 03:08:51 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-21 03:08:51 (8458) [INFO] Determining fastest mirrors
* 2024-11-21 03:08:52 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-21 03:08:52 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-21 03:08:52 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-21 03:08:53 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 03:08:53 (8458) [INFO] Trying other mirror.
* 2024-11-21 03:08:53 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-21 03:08:53 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-21 03:08:53 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-21 03:08:53 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-21 03:08:53 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-21 03:08:53 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-21 03:08:53 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-21 03:08:53 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-21 03:08:53 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-21 03:08:53 (8458) [INFO]         or
* 2024-11-21 03:08:53 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-21 03:08:53 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-21 03:08:53 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-21 03:08:53 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-21 03:08:53 (8458) [INFO]         compromise:
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-21 03:08:53 (8458) [INFO] 
* 2024-11-21 03:08:53 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-21 03:08:53 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 03:08:53 (8475) [INFO] 
* 2024-11-21 03:08:53 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-21 03:08:53 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-21 03:08:53 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-21 03:08:54 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1bJDD1vyed/ea_profile.json
* 2024-11-21 03:08:56 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/1bJDD1vyed/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-21 03:08:56 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-22 03:09:06 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-22 03:09:06 (9517) [INFO] Script is up to date.
* 2024-11-22 03:09:07 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-22 03:09:07 (8445) [INFO] 
* 2024-11-22 03:09:12 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-22 03:09:12 (8445) [INFO] 
* 2024-11-22 03:09:13 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-22 03:09:13 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-22 03:09:13 (8475) [INFO] 
* 2024-11-22 03:09:13 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-22 03:09:13 (8445) [INFO] 
* 2024-11-22 03:09:17 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-22 03:09:17 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-22 03:09:17 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-22 03:09:17 (8445) [INFO] 
* 2024-11-22 03:09:17 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 03:09:18 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-22 03:09:18 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-22 03:09:18 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-22 03:09:18 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-22 03:09:19 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 03:09:19 (8458) [INFO] Trying other mirror.
* 2024-11-22 03:09:19 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-22 03:09:19 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 03:09:19 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 03:09:19 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-22 03:09:19 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-22 03:09:19 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-22 03:09:19 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 03:09:19 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-22 03:09:19 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-22 03:09:19 (8458) [INFO]         or
* 2024-11-22 03:09:19 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 03:09:19 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 03:09:19 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 03:09:19 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 03:09:19 (8458) [INFO]         compromise:
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-22 03:09:19 (8458) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-22 03:09:19 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 03:09:19 (8475) [INFO] 
* 2024-11-22 03:09:19 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 03:09:19 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-22 03:09:19 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-22 03:09:19 (8445) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 03:09:19 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-22 03:09:19 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-22 03:09:19 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-22 03:09:19 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-22 03:09:19 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-22 03:09:19 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-22 03:09:19 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-22 03:09:19 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-22 03:09:19 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-22 03:09:19 (8475) [INFO] 
* 2024-11-22 03:09:19 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-22 03:09:19 (8445) [INFO] 
* 2024-11-22 03:09:19 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-22 03:09:20 (8458) [INFO] Determining fastest mirrors
* 2024-11-22 03:09:21 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-22 03:09:21 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-22 03:09:21 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-22 03:09:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 03:09:21 (8458) [INFO] Trying other mirror.
* 2024-11-22 03:09:21 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-22 03:09:21 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-22 03:09:21 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-22 03:09:21 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-22 03:09:21 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-22 03:09:21 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-22 03:09:21 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-22 03:09:21 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-22 03:09:21 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-22 03:09:21 (8458) [INFO]         or
* 2024-11-22 03:09:21 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-22 03:09:21 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-22 03:09:21 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-22 03:09:21 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-22 03:09:21 (8458) [INFO]         compromise:
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-22 03:09:21 (8458) [INFO] 
* 2024-11-22 03:09:21 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-22 03:09:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 03:09:21 (8475) [INFO] 
* 2024-11-22 03:09:21 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-22 03:09:21 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-22 03:09:22 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-22 03:09:22 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ybab_nbXGJ/ea_profile.json
* 2024-11-22 03:09:24 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ybab_nbXGJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-22 03:09:24 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-23 03:09:48 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-23 03:09:48 (9517) [INFO] Script is up to date.
* 2024-11-23 03:09:49 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-23 03:09:49 (8445) [INFO] 
* 2024-11-23 03:09:53 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-23 03:09:53 (8445) [INFO] 
* 2024-11-23 03:09:53 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-23 03:09:53 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-23 03:09:53 (8475) [INFO] 
* 2024-11-23 03:09:53 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-23 03:09:53 (8445) [INFO] 
* 2024-11-23 03:09:59 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-23 03:09:59 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-23 03:09:59 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-23 03:09:59 (8445) [INFO] 
* 2024-11-23 03:09:59 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 03:09:59 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-23 03:10:02 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-23 03:10:02 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-23 03:10:02 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-23 03:10:02 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 03:10:02 (8458) [INFO] Trying other mirror.
* 2024-11-23 03:10:02 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-23 03:10:02 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 03:10:02 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 03:10:02 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-23 03:10:02 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-23 03:10:02 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-23 03:10:02 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 03:10:02 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-23 03:10:02 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-23 03:10:02 (8458) [INFO]         or
* 2024-11-23 03:10:02 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 03:10:02 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 03:10:02 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 03:10:02 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 03:10:02 (8458) [INFO]         compromise:
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-23 03:10:02 (8458) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-23 03:10:02 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 03:10:02 (8475) [INFO] 
* 2024-11-23 03:10:02 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 03:10:02 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-23 03:10:02 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-23 03:10:02 (8445) [INFO] 
* 2024-11-23 03:10:02 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 03:10:03 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-23 03:10:03 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-23 03:10:03 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-23 03:10:03 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-23 03:10:03 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-23 03:10:03 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-23 03:10:03 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-23 03:10:03 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-23 03:10:03 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-23 03:10:03 (8475) [INFO] 
* 2024-11-23 03:10:03 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-23 03:10:03 (8445) [INFO] 
* 2024-11-23 03:10:03 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-23 03:10:03 (8458) [INFO] Determining fastest mirrors
* 2024-11-23 03:10:07 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-23 03:10:07 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-23 03:10:07 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-23 03:10:08 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 03:10:08 (8458) [INFO] Trying other mirror.
* 2024-11-23 03:10:08 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-23 03:10:08 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-23 03:10:08 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-23 03:10:08 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-23 03:10:08 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-23 03:10:08 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-23 03:10:08 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-23 03:10:08 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-23 03:10:08 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-23 03:10:08 (8458) [INFO]         or
* 2024-11-23 03:10:08 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-23 03:10:08 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-23 03:10:08 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-23 03:10:08 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-23 03:10:08 (8458) [INFO]         compromise:
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-23 03:10:08 (8458) [INFO] 
* 2024-11-23 03:10:08 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-23 03:10:08 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 03:10:08 (8475) [INFO] 
* 2024-11-23 03:10:08 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-23 03:10:08 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-23 03:10:08 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-23 03:10:09 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y1Cd31Iksl/ea_profile.json
* 2024-11-23 03:10:11 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Y1Cd31Iksl/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-23 03:10:11 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-24 03:09:30 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-24 03:09:30 (9517) [INFO] Script is up to date.
* 2024-11-24 03:09:31 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-24 03:09:31 (8445) [INFO] 
* 2024-11-24 03:09:35 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-24 03:09:35 (8445) [INFO] 
* 2024-11-24 03:09:35 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-24 03:09:35 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-24 03:09:35 (8475) [INFO] 
* 2024-11-24 03:09:35 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-24 03:09:35 (8445) [INFO] 
* 2024-11-24 03:09:39 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-24 03:09:39 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-24 03:09:39 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-24 03:09:39 (8445) [INFO] 
* 2024-11-24 03:09:39 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 03:09:39 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-24 03:09:40 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-24 03:09:40 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-24 03:09:40 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-24 03:09:41 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 03:09:41 (8458) [INFO] Trying other mirror.
* 2024-11-24 03:09:41 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-24 03:09:41 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 03:09:41 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 03:09:41 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-24 03:09:41 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-24 03:09:41 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-24 03:09:41 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 03:09:41 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-24 03:09:41 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-24 03:09:41 (8458) [INFO]         or
* 2024-11-24 03:09:41 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 03:09:41 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 03:09:41 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 03:09:41 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 03:09:41 (8458) [INFO]         compromise:
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-24 03:09:41 (8458) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-24 03:09:41 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 03:09:41 (8475) [INFO] 
* 2024-11-24 03:09:41 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 03:09:41 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-24 03:09:41 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-24 03:09:41 (8445) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 03:09:41 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-24 03:09:41 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-24 03:09:41 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-24 03:09:41 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-24 03:09:41 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-24 03:09:41 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-24 03:09:41 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-24 03:09:41 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-24 03:09:41 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-24 03:09:41 (8475) [INFO] 
* 2024-11-24 03:09:41 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-24 03:09:41 (8445) [INFO] 
* 2024-11-24 03:09:41 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-24 03:09:42 (8458) [INFO] Determining fastest mirrors
* 2024-11-24 03:09:43 (8458) [INFO]  * EA4: 185.157.208.252
* 2024-11-24 03:09:43 (8458) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-24 03:09:43 (8458) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-24 03:09:43 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 03:09:43 (8458) [INFO] Trying other mirror.
* 2024-11-24 03:09:43 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-24 03:09:43 (8458) [INFO] 
* 2024-11-24 03:09:43 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-24 03:09:43 (8458) [INFO] 
* 2024-11-24 03:09:43 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-24 03:09:43 (8458) [INFO] 
* 2024-11-24 03:09:43 (8458) [INFO] 
* 2024-11-24 03:09:43 (8458) [INFO] 
* 2024-11-24 03:09:43 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-24 03:09:43 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-24 03:09:43 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-24 03:09:44 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-24 03:09:44 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-24 03:09:44 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-24 03:09:44 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-24 03:09:44 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-24 03:09:44 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-24 03:09:44 (8458) [INFO]         or
* 2024-11-24 03:09:44 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-24 03:09:44 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-24 03:09:44 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-24 03:09:44 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-24 03:09:44 (8458) [INFO]         compromise:
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-24 03:09:44 (8458) [INFO] 
* 2024-11-24 03:09:44 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-24 03:09:44 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 03:09:44 (8475) [INFO] 
* 2024-11-24 03:09:44 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-24 03:09:44 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-24 03:09:44 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-24 03:09:45 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AMAXybFAzk/ea_profile.json
* 2024-11-24 03:09:47 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AMAXybFAzk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-24 03:09:47 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-25 03:08:51 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-25 03:08:51 (9517) [INFO] Script is up to date.
* 2024-11-25 03:08:53 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-25 03:08:53 (8445) [INFO] 
* 2024-11-25 03:08:56 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-25 03:08:56 (8445) [INFO] 
* 2024-11-25 03:08:57 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-25 03:08:57 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-25 03:08:57 (8475) [INFO] 
* 2024-11-25 03:08:57 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-25 03:08:57 (8445) [INFO] 
* 2024-11-25 03:09:02 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-25 03:09:02 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-25 03:09:02 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-25 03:09:02 (8445) [INFO] 
* 2024-11-25 03:09:02 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 03:09:02 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-25 03:09:02 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-25 03:09:02 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-25 03:09:02 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-25 03:09:03 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 03:09:03 (8458) [INFO] Trying other mirror.
* 2024-11-25 03:09:03 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-25 03:09:03 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 03:09:03 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 03:09:03 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-25 03:09:03 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-25 03:09:03 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-25 03:09:03 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 03:09:03 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-25 03:09:03 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-25 03:09:03 (8458) [INFO]         or
* 2024-11-25 03:09:03 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 03:09:03 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 03:09:03 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 03:09:03 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 03:09:03 (8458) [INFO]         compromise:
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-25 03:09:03 (8458) [INFO] 
* 2024-11-25 03:09:03 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-25 03:09:03 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 03:09:03 (8475) [INFO] 
* 2024-11-25 03:09:03 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 03:09:03 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-25 03:09:03 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-25 03:09:03 (8445) [INFO] 
* 2024-11-25 03:09:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 03:09:04 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-25 03:09:04 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-25 03:09:04 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-25 03:09:04 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-25 03:09:04 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-25 03:09:04 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-25 03:09:04 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-25 03:09:04 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-25 03:09:04 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-25 03:09:04 (8475) [INFO] 
* 2024-11-25 03:09:04 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-25 03:09:04 (8445) [INFO] 
* 2024-11-25 03:09:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-25 03:09:05 (8458) [INFO] Determining fastest mirrors
* 2024-11-25 03:09:07 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-25 03:09:07 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-25 03:09:07 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-25 03:09:07 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 03:09:07 (8458) [INFO] Trying other mirror.
* 2024-11-25 03:09:07 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-25 03:09:07 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-25 03:09:07 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-25 03:09:07 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-25 03:09:07 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-25 03:09:07 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-25 03:09:07 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-25 03:09:07 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-25 03:09:07 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-25 03:09:07 (8458) [INFO]         or
* 2024-11-25 03:09:07 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-25 03:09:07 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-25 03:09:07 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-25 03:09:07 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-25 03:09:07 (8458) [INFO]         compromise:
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-25 03:09:07 (8458) [INFO] 
* 2024-11-25 03:09:07 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-25 03:09:07 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 03:09:07 (8475) [INFO] 
* 2024-11-25 03:09:07 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-25 03:09:07 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-25 03:09:07 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-25 03:09:08 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xPHLLcWoD7/ea_profile.json
* 2024-11-25 03:09:10 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xPHLLcWoD7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-25 03:09:10 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-26 03:09:15 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-26 03:09:15 (9517) [INFO] Script is up to date.
* 2024-11-26 03:09:16 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-26 03:09:16 (8445) [INFO] 
* 2024-11-26 03:09:17 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-26 03:09:17 (8445) [INFO] 
* 2024-11-26 03:09:18 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-26 03:09:18 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-26 03:09:18 (8475) [INFO] 
* 2024-11-26 03:09:18 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-26 03:09:18 (8445) [INFO] 
* 2024-11-26 03:09:20 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-26 03:09:20 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-26 03:09:20 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-26 03:09:20 (8445) [INFO] 
* 2024-11-26 03:09:21 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 03:09:21 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-26 03:09:22 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-26 03:09:22 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-26 03:09:22 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-26 03:09:22 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 03:09:22 (8458) [INFO] Trying other mirror.
* 2024-11-26 03:09:22 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-26 03:09:22 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-26 03:09:22 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-26 03:09:22 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-26 03:09:22 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-26 03:09:22 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-26 03:09:22 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-26 03:09:22 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-26 03:09:22 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-26 03:09:22 (8458) [INFO]         or
* 2024-11-26 03:09:22 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-26 03:09:22 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-26 03:09:22 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-26 03:09:22 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-26 03:09:22 (8458) [INFO]         compromise:
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-26 03:09:22 (8458) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-26 03:09:22 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 03:09:22 (8475) [INFO] 
* 2024-11-26 03:09:22 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 03:09:22 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-26 03:09:22 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-26 03:09:22 (8445) [INFO] 
* 2024-11-26 03:09:22 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 03:09:22 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-26 03:09:22 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-26 03:09:22 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-26 03:09:22 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-26 03:09:22 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-26 03:09:22 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-26 03:09:22 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-26 03:09:22 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-26 03:09:22 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-26 03:09:22 (8475) [INFO] 
* 2024-11-26 03:09:22 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-26 03:09:22 (8445) [INFO] 
* 2024-11-26 03:09:23 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-26 03:09:23 (8458) [INFO] Determining fastest mirrors
* 2024-11-26 03:09:25 (8458) [INFO]  * EA4: 185.157.208.252
* 2024-11-26 03:09:25 (8458) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-26 03:09:25 (8458) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-26 03:09:25 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 03:09:25 (8458) [INFO] Trying other mirror.
* 2024-11-26 03:09:25 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-26 03:09:25 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-26 03:09:25 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-26 03:09:25 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-26 03:09:25 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-26 03:09:25 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-26 03:09:25 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-26 03:09:25 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-26 03:09:25 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-26 03:09:25 (8458) [INFO]         or
* 2024-11-26 03:09:25 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-26 03:09:25 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-26 03:09:25 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-26 03:09:25 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-26 03:09:25 (8458) [INFO]         compromise:
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-26 03:09:25 (8458) [INFO] 
* 2024-11-26 03:09:25 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-26 03:09:25 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 03:09:25 (8475) [INFO] 
* 2024-11-26 03:09:25 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-26 03:09:25 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-26 03:09:26 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-26 03:09:27 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qn8DQPaH8e/ea_profile.json
* 2024-11-26 03:09:28 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/qn8DQPaH8e/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-26 03:09:28 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-27 03:08:48 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-27 03:08:48 (9517) [INFO] Script is up to date.
* 2024-11-27 03:08:50 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-27 03:08:50 (8445) [INFO] 
* 2024-11-27 03:08:54 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-27 03:08:54 (8445) [INFO] 
* 2024-11-27 03:08:54 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-27 03:08:54 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-27 03:08:54 (8475) [INFO] 
* 2024-11-27 03:08:54 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-27 03:08:54 (8445) [INFO] 
* 2024-11-27 03:08:59 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-27 03:08:59 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-27 03:08:59 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-27 03:08:59 (8445) [INFO] 
* 2024-11-27 03:09:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 03:09:00 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-27 03:09:00 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-27 03:09:00 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-27 03:09:00 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-27 03:09:01 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 03:09:01 (8458) [INFO] Trying other mirror.
* 2024-11-27 03:09:01 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-27 03:09:01 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-27 03:09:01 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-27 03:09:01 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-27 03:09:01 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-27 03:09:01 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-27 03:09:01 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-27 03:09:01 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-27 03:09:01 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-27 03:09:01 (8458) [INFO]         or
* 2024-11-27 03:09:01 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-27 03:09:01 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-27 03:09:01 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-27 03:09:01 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-27 03:09:01 (8458) [INFO]         compromise:
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-27 03:09:01 (8458) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-27 03:09:01 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 03:09:01 (8475) [INFO] 
* 2024-11-27 03:09:01 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 03:09:01 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-27 03:09:01 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-27 03:09:01 (8445) [INFO] 
* 2024-11-27 03:09:01 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 03:09:02 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-27 03:09:02 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-27 03:09:02 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-27 03:09:02 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-27 03:09:02 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-27 03:09:02 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-27 03:09:02 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-27 03:09:02 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-27 03:09:02 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-27 03:09:02 (8475) [INFO] 
* 2024-11-27 03:09:02 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-27 03:09:02 (8445) [INFO] 
* 2024-11-27 03:09:02 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-27 03:09:02 (8458) [INFO] Determining fastest mirrors
* 2024-11-27 03:09:03 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-27 03:09:03 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-27 03:09:03 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-27 03:09:04 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 03:09:04 (8458) [INFO] Trying other mirror.
* 2024-11-27 03:09:04 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-27 03:09:04 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-27 03:09:04 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-27 03:09:04 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-27 03:09:04 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-27 03:09:04 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-27 03:09:04 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-27 03:09:04 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-27 03:09:04 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-27 03:09:04 (8458) [INFO]         or
* 2024-11-27 03:09:04 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-27 03:09:04 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-27 03:09:04 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-27 03:09:04 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-27 03:09:04 (8458) [INFO]         compromise:
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-27 03:09:04 (8458) [INFO] 
* 2024-11-27 03:09:04 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-27 03:09:04 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 03:09:04 (8475) [INFO] 
* 2024-11-27 03:09:04 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-27 03:09:04 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-27 03:09:04 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-27 03:09:05 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C6nx__Oz6a/ea_profile.json
* 2024-11-27 03:09:07 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/C6nx__Oz6a/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-27 03:09:07 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-28 03:08:38 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-28 03:08:38 (9517) [INFO] Script is up to date.
* 2024-11-28 03:08:39 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-28 03:08:39 (8445) [INFO] 
* 2024-11-28 03:08:40 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-28 03:08:40 (8445) [INFO] 
* 2024-11-28 03:08:40 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-28 03:08:40 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-28 03:08:40 (8475) [INFO] 
* 2024-11-28 03:08:40 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-28 03:08:40 (8445) [INFO] 
* 2024-11-28 03:08:43 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-28 03:08:43 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-28 03:08:43 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-28 03:08:43 (8445) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 03:08:44 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-28 03:08:44 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-28 03:08:44 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-28 03:08:44 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-28 03:08:44 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 03:08:44 (8458) [INFO] Trying other mirror.
* 2024-11-28 03:08:44 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-28 03:08:44 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 03:08:44 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 03:08:44 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-28 03:08:44 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-28 03:08:44 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-28 03:08:44 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 03:08:44 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-28 03:08:44 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-28 03:08:44 (8458) [INFO]         or
* 2024-11-28 03:08:44 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 03:08:44 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 03:08:44 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 03:08:44 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 03:08:44 (8458) [INFO]         compromise:
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-28 03:08:44 (8458) [INFO] 
* 2024-11-28 03:08:44 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-28 03:08:44 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 03:08:44 (8475) [INFO] 
* 2024-11-28 03:08:44 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 03:08:44 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-28 03:08:44 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-28 03:08:44 (8445) [INFO] 
* 2024-11-28 03:08:45 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 03:08:45 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-28 03:08:45 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-28 03:08:45 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-28 03:08:45 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-28 03:08:45 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-28 03:08:45 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-28 03:08:45 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-28 03:08:45 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-28 03:08:45 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-28 03:08:45 (8475) [INFO] 
* 2024-11-28 03:08:45 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-28 03:08:45 (8445) [INFO] 
* 2024-11-28 03:08:45 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-28 03:08:45 (8458) [INFO] Determining fastest mirrors
* 2024-11-28 03:08:47 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-28 03:08:47 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-28 03:08:47 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-28 03:08:48 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 03:08:48 (8458) [INFO] Trying other mirror.
* 2024-11-28 03:08:48 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-28 03:08:48 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-28 03:08:48 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-28 03:08:48 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-28 03:08:48 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-28 03:08:48 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-28 03:08:48 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-28 03:08:48 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-28 03:08:48 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-28 03:08:48 (8458) [INFO]         or
* 2024-11-28 03:08:48 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-28 03:08:48 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-28 03:08:48 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-28 03:08:48 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-28 03:08:48 (8458) [INFO]         compromise:
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-28 03:08:48 (8458) [INFO] 
* 2024-11-28 03:08:48 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-28 03:08:48 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 03:08:48 (8475) [INFO] 
* 2024-11-28 03:08:48 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-28 03:08:48 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-28 03:08:48 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-28 03:08:49 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NSxWt8z5HB/ea_profile.json
* 2024-11-28 03:08:50 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NSxWt8z5HB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-28 03:08:50 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-29 03:08:48 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-29 03:08:48 (9517) [INFO] Script is up to date.
* 2024-11-29 03:08:49 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-29 03:08:49 (8445) [INFO] 
* 2024-11-29 03:08:54 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-29 03:08:54 (8445) [INFO] 
* 2024-11-29 03:08:54 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-29 03:08:54 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-29 03:08:54 (8475) [INFO] 
* 2024-11-29 03:08:54 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-29 03:08:54 (8445) [INFO] 
* 2024-11-29 03:09:01 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-29 03:09:01 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-29 03:09:01 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-29 03:09:01 (8445) [INFO] 
* 2024-11-29 03:09:01 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 03:09:01 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-29 03:09:02 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-29 03:09:02 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-29 03:09:02 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-29 03:09:03 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 03:09:03 (8458) [INFO] Trying other mirror.
* 2024-11-29 03:09:03 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-29 03:09:03 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 03:09:03 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 03:09:03 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-29 03:09:03 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-29 03:09:03 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-29 03:09:03 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 03:09:03 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-29 03:09:03 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-29 03:09:03 (8458) [INFO]         or
* 2024-11-29 03:09:03 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 03:09:03 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 03:09:03 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 03:09:03 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 03:09:03 (8458) [INFO]         compromise:
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-29 03:09:03 (8458) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-29 03:09:03 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 03:09:03 (8475) [INFO] 
* 2024-11-29 03:09:03 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 03:09:03 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-29 03:09:03 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-29 03:09:03 (8445) [INFO] 
* 2024-11-29 03:09:03 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 03:09:03 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-29 03:09:03 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-29 03:09:03 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-29 03:09:03 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-29 03:09:03 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-29 03:09:03 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-29 03:09:03 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-29 03:09:03 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-29 03:09:03 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-29 03:09:03 (8475) [INFO] 
* 2024-11-29 03:09:03 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-29 03:09:03 (8445) [INFO] 
* 2024-11-29 03:09:04 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-29 03:09:04 (8458) [INFO] Determining fastest mirrors
* 2024-11-29 03:09:07 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-11-29 03:09:07 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-11-29 03:09:07 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-11-29 03:09:07 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 03:09:07 (8458) [INFO] Trying other mirror.
* 2024-11-29 03:09:07 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-29 03:09:07 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-29 03:09:07 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-29 03:09:07 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-29 03:09:07 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-29 03:09:07 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-29 03:09:07 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-29 03:09:07 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-29 03:09:07 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-29 03:09:07 (8458) [INFO]         or
* 2024-11-29 03:09:07 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-29 03:09:07 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-29 03:09:07 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-29 03:09:07 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-29 03:09:07 (8458) [INFO]         compromise:
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-29 03:09:07 (8458) [INFO] 
* 2024-11-29 03:09:07 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-29 03:09:07 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 03:09:07 (8475) [INFO] 
* 2024-11-29 03:09:07 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-29 03:09:07 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-29 03:09:08 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-29 03:09:09 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wRZ9t2L5VJ/ea_profile.json
* 2024-11-29 03:09:11 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/wRZ9t2L5VJ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-29 03:09:11 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-11-30 03:10:08 (9495) [INFO] Self-update of script version 58 requested.
* 2024-11-30 03:10:08 (9517) [INFO] Script is up to date.
* 2024-11-30 03:10:09 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-11-30 03:10:09 (8445) [INFO] 
* 2024-11-30 03:10:15 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-11-30 03:10:15 (8445) [INFO] 
* 2024-11-30 03:10:16 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-11-30 03:10:16 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-11-30 03:10:16 (8475) [INFO] 
* 2024-11-30 03:10:16 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-11-30 03:10:16 (8445) [INFO] 
* 2024-11-30 03:10:19 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-11-30 03:10:19 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-11-30 03:10:19 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-30 03:10:19 (8445) [INFO] 
* 2024-11-30 03:10:20 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 03:10:20 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-11-30 03:10:21 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-11-30 03:10:21 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-11-30 03:10:21 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-11-30 03:10:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 03:10:21 (8458) [INFO] Trying other mirror.
* 2024-11-30 03:10:21 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-30 03:10:21 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 03:10:21 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 03:10:21 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-30 03:10:21 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-30 03:10:21 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-30 03:10:21 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 03:10:21 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-30 03:10:21 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-30 03:10:21 (8458) [INFO]         or
* 2024-11-30 03:10:21 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 03:10:21 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 03:10:21 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 03:10:21 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 03:10:21 (8458) [INFO]         compromise:
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-30 03:10:21 (8458) [INFO] 
* 2024-11-30 03:10:21 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-30 03:10:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 03:10:22 (8475) [INFO] 
* 2024-11-30 03:10:22 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 03:10:22 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-11-30 03:10:22 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-11-30 03:10:22 (8445) [INFO] 
* 2024-11-30 03:10:22 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 03:10:22 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-11-30 03:10:22 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-11-30 03:10:22 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-11-30 03:10:22 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-11-30 03:10:22 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-11-30 03:10:22 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-11-30 03:10:22 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-11-30 03:10:22 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-11-30 03:10:22 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-11-30 03:10:22 (8475) [INFO] 
* 2024-11-30 03:10:22 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-11-30 03:10:22 (8445) [INFO] 
* 2024-11-30 03:10:22 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-11-30 03:10:22 (8458) [INFO] Determining fastest mirrors
* 2024-11-30 03:10:26 (8458) [INFO]  * EA4: 185.157.208.252
* 2024-11-30 03:10:26 (8458) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-11-30 03:10:26 (8458) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-11-30 03:10:26 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 03:10:26 (8458) [INFO] Trying other mirror.
* 2024-11-30 03:10:26 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-11-30 03:10:26 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-11-30 03:10:26 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-11-30 03:10:26 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-11-30 03:10:26 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-11-30 03:10:26 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-11-30 03:10:26 (8458) [INFO]             yum --disablerepo=base ...
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-11-30 03:10:26 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-11-30 03:10:26 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]             yum-config-manager --disable base
* 2024-11-30 03:10:26 (8458) [INFO]         or
* 2024-11-30 03:10:26 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-11-30 03:10:26 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-11-30 03:10:26 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-11-30 03:10:26 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-11-30 03:10:26 (8458) [INFO]         compromise:
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-11-30 03:10:26 (8458) [INFO] 
* 2024-11-30 03:10:26 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-11-30 03:10:26 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 03:10:26 (8475) [INFO] 
* 2024-11-30 03:10:26 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-11-30 03:10:26 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-11-30 03:10:27 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-11-30 03:10:27 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lUoJb30pMa/ea_profile.json
* 2024-11-30 03:10:30 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/lUoJb30pMa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-11-30 03:10:30 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-01 03:09:47 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-01 03:09:47 (9517) [INFO] Script is up to date.
* 2024-12-01 03:09:48 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-01 03:09:48 (8445) [INFO] 
* 2024-12-01 03:09:53 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-01 03:09:53 (8445) [INFO] 
* 2024-12-01 03:09:54 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-12-01 03:09:54 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-01 03:09:54 (8475) [INFO] 
* 2024-12-01 03:09:54 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-01 03:09:54 (8445) [INFO] 
* 2024-12-01 03:09:59 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-01 03:09:59 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-01 03:09:59 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-01 03:09:59 (8445) [INFO] 
* 2024-12-01 03:10:00 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 03:10:00 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-01 03:10:01 (8458) [INFO]  * EA4: 31.22.112.31
* 2024-12-01 03:10:01 (8458) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-01 03:10:01 (8458) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-01 03:10:01 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 03:10:01 (8458) [INFO] Trying other mirror.
* 2024-12-01 03:10:01 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-01 03:10:01 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 03:10:01 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 03:10:01 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-01 03:10:01 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-01 03:10:01 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-01 03:10:01 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 03:10:01 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-01 03:10:01 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-01 03:10:01 (8458) [INFO]         or
* 2024-12-01 03:10:01 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 03:10:01 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 03:10:01 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 03:10:01 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 03:10:01 (8458) [INFO]         compromise:
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-01 03:10:01 (8458) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-01 03:10:01 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 03:10:01 (8475) [INFO] 
* 2024-12-01 03:10:01 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 03:10:01 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-01 03:10:01 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-01 03:10:01 (8445) [INFO] 
* 2024-12-01 03:10:01 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 03:10:02 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-01 03:10:02 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-01 03:10:02 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-01 03:10:02 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-01 03:10:02 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-01 03:10:02 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-01 03:10:02 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-01 03:10:02 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-01 03:10:02 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-01 03:10:02 (8475) [INFO] 
* 2024-12-01 03:10:02 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-01 03:10:02 (8445) [INFO] 
* 2024-12-01 03:10:02 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-01 03:10:02 (8458) [INFO] Determining fastest mirrors
* 2024-12-01 03:10:03 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-12-01 03:10:03 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-01 03:10:03 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-01 03:10:04 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 03:10:04 (8458) [INFO] Trying other mirror.
* 2024-12-01 03:10:04 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-01 03:10:04 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-01 03:10:04 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-01 03:10:04 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-01 03:10:04 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-01 03:10:04 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-01 03:10:04 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-01 03:10:04 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-01 03:10:04 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-01 03:10:04 (8458) [INFO]         or
* 2024-12-01 03:10:04 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-01 03:10:04 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-01 03:10:04 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-01 03:10:04 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-01 03:10:04 (8458) [INFO]         compromise:
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-01 03:10:04 (8458) [INFO] 
* 2024-12-01 03:10:04 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-01 03:10:04 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 03:10:04 (8475) [INFO] 
* 2024-12-01 03:10:04 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-01 03:10:04 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-01 03:10:05 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-01 03:10:06 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mu0Unx2Ya3/ea_profile.json
* 2024-12-01 03:10:08 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/mu0Unx2Ya3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-01 03:10:08 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-02 03:09:05 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-02 03:09:05 (9517) [INFO] Script is up to date.
* 2024-12-02 03:09:07 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-02 03:09:07 (8445) [INFO] 
* 2024-12-02 03:09:12 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-02 03:09:12 (8445) [INFO] 
* 2024-12-02 03:09:13 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-12-02 03:09:13 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-02 03:09:13 (8475) [INFO] 
* 2024-12-02 03:09:13 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-02 03:09:13 (8445) [INFO] 
* 2024-12-02 03:09:19 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-02 03:09:19 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-02 03:09:19 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-02 03:09:19 (8445) [INFO] 
* 2024-12-02 03:09:19 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 03:09:19 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-02 03:09:20 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-12-02 03:09:20 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-02 03:09:20 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-02 03:09:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 03:09:21 (8458) [INFO] Trying other mirror.
* 2024-12-02 03:09:21 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-02 03:09:21 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-02 03:09:21 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-02 03:09:21 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-02 03:09:21 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-02 03:09:21 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-02 03:09:21 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-02 03:09:21 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-02 03:09:21 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-02 03:09:21 (8458) [INFO]         or
* 2024-12-02 03:09:21 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-02 03:09:21 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-02 03:09:21 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-02 03:09:21 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-02 03:09:21 (8458) [INFO]         compromise:
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-02 03:09:21 (8458) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-02 03:09:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 03:09:21 (8475) [INFO] 
* 2024-12-02 03:09:21 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 03:09:21 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-02 03:09:21 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-02 03:09:21 (8445) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 03:09:21 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-02 03:09:21 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-02 03:09:21 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-02 03:09:21 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-02 03:09:21 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-02 03:09:21 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-02 03:09:21 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-02 03:09:21 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-02 03:09:21 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-02 03:09:21 (8475) [INFO] 
* 2024-12-02 03:09:21 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-02 03:09:21 (8445) [INFO] 
* 2024-12-02 03:09:21 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-02 03:09:22 (8458) [INFO] Determining fastest mirrors
* 2024-12-02 03:09:24 (8458) [INFO]  * EA4: 185.157.208.252
* 2024-12-02 03:09:24 (8458) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-02 03:09:24 (8458) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-02 03:09:24 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 03:09:24 (8458) [INFO] Trying other mirror.
* 2024-12-02 03:09:24 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-02 03:09:24 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-02 03:09:24 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-02 03:09:24 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-02 03:09:24 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-02 03:09:24 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-02 03:09:24 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-02 03:09:24 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-02 03:09:24 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-02 03:09:24 (8458) [INFO]         or
* 2024-12-02 03:09:24 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-02 03:09:24 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-02 03:09:24 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-02 03:09:24 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-02 03:09:24 (8458) [INFO]         compromise:
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-02 03:09:24 (8458) [INFO] 
* 2024-12-02 03:09:24 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-02 03:09:24 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 03:09:24 (8475) [INFO] 
* 2024-12-02 03:09:24 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-02 03:09:24 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-02 03:09:24 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-02 03:09:26 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AmSVMCh2Ra/ea_profile.json
* 2024-12-02 03:09:28 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/AmSVMCh2Ra/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-02 03:09:28 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-03 03:08:55 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-03 03:08:56 (9517) [INFO] Script is up to date.
* 2024-12-03 03:08:57 (8444) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-03 03:08:57 (8445) [INFO] 
* 2024-12-03 03:09:04 (8444) [INFO] Running: /usr/bin/mysqlcheck -c -m -A --silent
* 2024-12-03 03:09:04 (8445) [INFO] 
* 2024-12-03 03:09:05 (8458) [INFO] trebiaseguros_wp_6ov6o.en84f8lhv_wfls_role_counts
* 2024-12-03 03:09:05 (8458) [INFO] note     : The storage engine for the table doesn't support check
* 2024-12-03 03:09:05 (8475) [INFO] 
* 2024-12-03 03:09:05 (8444) [INFO] Running: /usr/bin/yum list extras
* 2024-12-03 03:09:05 (8445) [INFO] 
* 2024-12-03 03:09:09 (5627) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-03 03:09:09 (249) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-03 03:09:09 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-03 03:09:09 (8445) [INFO] 
* 2024-12-03 03:09:09 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 03:09:10 (8458) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-03 03:09:15 (8458) [INFO]  * EA4: 185.15.22.168
* 2024-12-03 03:09:15 (8458) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-03 03:09:15 (8458) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-03 03:09:16 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 03:09:16 (8458) [INFO] Trying other mirror.
* 2024-12-03 03:09:16 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-03 03:09:16 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 03:09:16 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 03:09:16 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-03 03:09:16 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-03 03:09:16 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-03 03:09:16 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 03:09:16 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-03 03:09:16 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-03 03:09:16 (8458) [INFO]         or
* 2024-12-03 03:09:16 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 03:09:16 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 03:09:16 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 03:09:16 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 03:09:16 (8458) [INFO]         compromise:
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-03 03:09:16 (8458) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-03 03:09:16 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 03:09:16 (8475) [INFO] 
* 2024-12-03 03:09:16 (5510) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 03:09:16 (5511) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-03 03:09:16 (8444) [INFO] Running: /usr/bin/yum clean all
* 2024-12-03 03:09:16 (8445) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 03:09:16 (8458) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-03 03:09:16 (8458) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-03 03:09:16 (8458) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-03 03:09:16 (8458) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-03 03:09:16 (8458) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-03 03:09:16 (8458) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-03 03:09:16 (8458) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-03 03:09:16 (8458) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-03 03:09:16 (8458) [INFO] Cleaning up list of fastest mirrors
* 2024-12-03 03:09:16 (8475) [INFO] 
* 2024-12-03 03:09:16 (8444) [INFO] Running: /usr/bin/yum makecache
* 2024-12-03 03:09:16 (8445) [INFO] 
* 2024-12-03 03:09:16 (8458) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-03 03:09:16 (8458) [INFO] Determining fastest mirrors
* 2024-12-03 03:09:20 (8458) [INFO]  * EA4: 185.157.208.252
* 2024-12-03 03:09:20 (8458) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-03 03:09:20 (8458) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-03 03:09:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 03:09:21 (8458) [INFO] Trying other mirror.
* 2024-12-03 03:09:21 (8458) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-03 03:09:21 (8458) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-03 03:09:21 (8458) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-03 03:09:21 (8458) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-03 03:09:21 (8458) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-03 03:09:21 (8458) [INFO]         packages for the previous distribution release still work).
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-03 03:09:21 (8458) [INFO]             yum --disablerepo=base ...
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-03 03:09:21 (8458) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-03 03:09:21 (8458) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]             yum-config-manager --disable base
* 2024-12-03 03:09:21 (8458) [INFO]         or
* 2024-12-03 03:09:21 (8458) [INFO]             subscription-manager repos --disable=base
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-03 03:09:21 (8458) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-03 03:09:21 (8458) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-03 03:09:21 (8458) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-03 03:09:21 (8458) [INFO]         compromise:
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-03 03:09:21 (8458) [INFO] 
* 2024-12-03 03:09:21 (8458) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-03 03:09:21 (8458) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 03:09:21 (8475) [INFO] 
* 2024-12-03 03:09:21 (5520) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-03 03:09:21 (5521) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-03 03:09:21 (1967) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-03 03:09:22 (7585) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iF0iUWK2S1/ea_profile.json
* 2024-12-03 03:09:24 (475) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iF0iUWK2S1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 7587.
* 2024-12-03 03:09:24 (439) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-04 03:09:09 (9495) [INFO] Self-update of script version 58 requested.
* 2024-12-04 03:09:09 (9500) [INFO] Newer version of script found. Downloading.
* 2024-12-04 03:09:10 (9509) [INFO] Script update to version 59 successful.
* 2024-12-04 03:09:12 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-04 03:09:12 (9238) [INFO] 
* 2024-12-04 03:09:17 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-04 03:09:17 (9238) [INFO] 
* 2024-12-04 03:09:23 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-04 03:09:23 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-04 03:09:23 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-04 03:09:23 (9238) [INFO] 
* 2024-12-04 03:09:23 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 03:09:23 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-04 03:09:24 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-04 03:09:24 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-04 03:09:24 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-04 03:09:25 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 03:09:25 (9251) [INFO] Trying other mirror.
* 2024-12-04 03:09:25 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-04 03:09:25 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 03:09:25 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 03:09:25 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-04 03:09:25 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-04 03:09:25 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-04 03:09:25 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 03:09:25 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-04 03:09:25 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-04 03:09:25 (9251) [INFO]         or
* 2024-12-04 03:09:25 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 03:09:25 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 03:09:25 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 03:09:25 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 03:09:25 (9251) [INFO]         compromise:
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-04 03:09:25 (9251) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-04 03:09:25 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 03:09:25 (9268) [INFO] 
* 2024-12-04 03:09:25 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 03:09:25 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-04 03:09:25 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-04 03:09:25 (9238) [INFO] 
* 2024-12-04 03:09:25 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 03:09:25 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-04 03:09:25 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-04 03:09:25 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-04 03:09:25 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-04 03:09:25 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-04 03:09:25 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-04 03:09:25 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-04 03:09:25 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-04 03:09:25 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-04 03:09:25 (9268) [INFO] 
* 2024-12-04 03:09:25 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-04 03:09:25 (9238) [INFO] 
* 2024-12-04 03:09:26 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-04 03:09:26 (9251) [INFO] Determining fastest mirrors
* 2024-12-04 03:09:28 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-04 03:09:28 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-04 03:09:28 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-04 03:09:29 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 03:09:29 (9251) [INFO] Trying other mirror.
* 2024-12-04 03:09:29 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-04 03:09:29 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-04 03:09:29 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-04 03:09:29 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-04 03:09:29 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-04 03:09:29 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-04 03:09:29 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-04 03:09:29 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-04 03:09:29 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-04 03:09:29 (9251) [INFO]         or
* 2024-12-04 03:09:29 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-04 03:09:29 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-04 03:09:29 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-04 03:09:29 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-04 03:09:29 (9251) [INFO]         compromise:
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-04 03:09:29 (9251) [INFO] 
* 2024-12-04 03:09:29 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-04 03:09:29 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 03:09:29 (9268) [INFO] 
* 2024-12-04 03:09:29 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-04 03:09:29 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-04 03:09:29 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-04 03:09:30 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7II5MdLnU1/ea_profile.json
* 2024-12-04 03:09:32 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/7II5MdLnU1/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-04 03:09:32 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-05 03:09:12 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-05 03:09:13 (10313) [INFO] Script is up to date.
* 2024-12-05 03:09:14 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-05 03:09:14 (9238) [INFO] 
* 2024-12-05 03:09:22 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-05 03:09:22 (9238) [INFO] 
* 2024-12-05 03:09:28 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-05 03:09:28 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-05 03:09:28 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-05 03:09:28 (9238) [INFO] 
* 2024-12-05 03:09:29 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 03:09:29 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-05 03:09:30 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-05 03:09:30 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-05 03:09:30 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-05 03:09:30 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 03:09:30 (9251) [INFO] Trying other mirror.
* 2024-12-05 03:09:30 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-05 03:09:30 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-05 03:09:30 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-05 03:09:30 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-05 03:09:30 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-05 03:09:30 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-05 03:09:30 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-05 03:09:30 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-05 03:09:30 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-05 03:09:30 (9251) [INFO]         or
* 2024-12-05 03:09:30 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-05 03:09:30 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-05 03:09:30 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-05 03:09:30 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-05 03:09:30 (9251) [INFO]         compromise:
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-05 03:09:30 (9251) [INFO] 
* 2024-12-05 03:09:30 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-05 03:09:30 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 03:09:30 (9268) [INFO] 
* 2024-12-05 03:09:30 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 03:09:30 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-05 03:09:30 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-05 03:09:30 (9238) [INFO] 
* 2024-12-05 03:09:31 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 03:09:31 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-05 03:09:31 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-05 03:09:31 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-05 03:09:31 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-05 03:09:31 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-05 03:09:31 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-05 03:09:31 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-05 03:09:31 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-05 03:09:31 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-05 03:09:31 (9268) [INFO] 
* 2024-12-05 03:09:31 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-05 03:09:31 (9238) [INFO] 
* 2024-12-05 03:09:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-05 03:09:32 (9251) [INFO] Determining fastest mirrors
* 2024-12-05 03:09:34 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-05 03:09:34 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-05 03:09:34 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-05 03:09:35 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 03:09:35 (9251) [INFO] Trying other mirror.
* 2024-12-05 03:09:35 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-05 03:09:35 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-05 03:09:35 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-05 03:09:35 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-05 03:09:35 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-05 03:09:35 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-05 03:09:35 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-05 03:09:35 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-05 03:09:35 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-05 03:09:35 (9251) [INFO]         or
* 2024-12-05 03:09:35 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-05 03:09:35 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-05 03:09:35 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-05 03:09:35 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-05 03:09:35 (9251) [INFO]         compromise:
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-05 03:09:35 (9251) [INFO] 
* 2024-12-05 03:09:35 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-05 03:09:35 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 03:09:35 (9268) [INFO] 
* 2024-12-05 03:09:35 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-05 03:09:35 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-05 03:09:35 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-05 03:09:36 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MRky5vgQ_q/ea_profile.json
* 2024-12-05 03:09:39 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/MRky5vgQ_q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-05 03:09:39 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-06 03:09:00 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-06 03:09:00 (10313) [INFO] Script is up to date.
* 2024-12-06 03:09:03 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-06 03:09:03 (9238) [INFO] 
* 2024-12-06 03:09:09 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-06 03:09:09 (9238) [INFO] 
* 2024-12-06 03:09:13 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-06 03:09:13 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-06 03:09:13 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-06 03:09:13 (9238) [INFO] 
* 2024-12-06 03:09:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 03:09:14 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-06 03:09:15 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-06 03:09:15 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-06 03:09:15 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-06 03:09:15 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 03:09:15 (9251) [INFO] Trying other mirror.
* 2024-12-06 03:09:15 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-06 03:09:15 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-06 03:09:15 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-06 03:09:15 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-06 03:09:15 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-06 03:09:15 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-06 03:09:15 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-06 03:09:15 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-06 03:09:15 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-06 03:09:15 (9251) [INFO]         or
* 2024-12-06 03:09:15 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-06 03:09:15 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-06 03:09:15 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-06 03:09:15 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-06 03:09:15 (9251) [INFO]         compromise:
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-06 03:09:15 (9251) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-06 03:09:15 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 03:09:15 (9268) [INFO] 
* 2024-12-06 03:09:15 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 03:09:15 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-06 03:09:15 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-06 03:09:15 (9238) [INFO] 
* 2024-12-06 03:09:15 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 03:09:15 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-06 03:09:15 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-06 03:09:15 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-06 03:09:15 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-06 03:09:15 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-06 03:09:15 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-06 03:09:15 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-06 03:09:15 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-06 03:09:15 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-06 03:09:16 (9268) [INFO] 
* 2024-12-06 03:09:16 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-06 03:09:16 (9238) [INFO] 
* 2024-12-06 03:09:16 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-06 03:09:16 (9251) [INFO] Determining fastest mirrors
* 2024-12-06 03:09:17 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-06 03:09:17 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-06 03:09:17 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-06 03:09:17 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 03:09:17 (9251) [INFO] Trying other mirror.
* 2024-12-06 03:09:17 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-06 03:09:17 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-06 03:09:17 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-06 03:09:17 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-06 03:09:17 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-06 03:09:17 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-06 03:09:17 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-06 03:09:17 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-06 03:09:17 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-06 03:09:17 (9251) [INFO]         or
* 2024-12-06 03:09:17 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-06 03:09:17 (9251) [INFO] 
* 2024-12-06 03:09:17 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-06 03:09:17 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-06 03:09:17 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-06 03:09:17 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-06 03:09:17 (9251) [INFO]         compromise:
* 2024-12-06 03:09:18 (9251) [INFO] 
* 2024-12-06 03:09:18 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-06 03:09:18 (9251) [INFO] 
* 2024-12-06 03:09:18 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-06 03:09:18 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 03:09:18 (9268) [INFO] 
* 2024-12-06 03:09:18 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-06 03:09:18 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-06 03:09:18 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-06 03:09:19 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eqetwBR23f/ea_profile.json
* 2024-12-06 03:09:21 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eqetwBR23f/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-06 03:09:21 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-07 03:10:05 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-07 03:10:05 (10313) [INFO] Script is up to date.
* 2024-12-07 03:10:06 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-07 03:10:06 (9238) [INFO] 
* 2024-12-07 03:10:13 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-07 03:10:13 (9238) [INFO] 
* 2024-12-07 03:10:16 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-07 03:10:16 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-07 03:10:16 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-07 03:10:16 (9238) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 03:10:17 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-07 03:10:17 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-07 03:10:17 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-07 03:10:17 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-07 03:10:17 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 03:10:17 (9251) [INFO] Trying other mirror.
* 2024-12-07 03:10:17 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-07 03:10:17 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-07 03:10:17 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-07 03:10:17 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-07 03:10:17 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-07 03:10:17 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-07 03:10:17 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-07 03:10:17 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-07 03:10:17 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-07 03:10:17 (9251) [INFO]         or
* 2024-12-07 03:10:17 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-07 03:10:17 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-07 03:10:17 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-07 03:10:17 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-07 03:10:17 (9251) [INFO]         compromise:
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-07 03:10:17 (9251) [INFO] 
* 2024-12-07 03:10:17 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-07 03:10:17 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 03:10:17 (9268) [INFO] 
* 2024-12-07 03:10:17 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 03:10:17 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-07 03:10:17 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-07 03:10:17 (9238) [INFO] 
* 2024-12-07 03:10:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 03:10:18 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-07 03:10:18 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-07 03:10:18 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-07 03:10:18 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-07 03:10:18 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-07 03:10:18 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-07 03:10:18 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-07 03:10:18 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-07 03:10:18 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-07 03:10:18 (9268) [INFO] 
* 2024-12-07 03:10:18 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-07 03:10:18 (9238) [INFO] 
* 2024-12-07 03:10:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-07 03:10:19 (9251) [INFO] Determining fastest mirrors
* 2024-12-07 03:10:21 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-07 03:10:21 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-07 03:10:21 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-07 03:10:21 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 03:10:21 (9251) [INFO] Trying other mirror.
* 2024-12-07 03:10:21 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-07 03:10:21 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-07 03:10:21 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-07 03:10:21 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-07 03:10:21 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-07 03:10:21 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-07 03:10:21 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-07 03:10:21 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-07 03:10:21 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-07 03:10:21 (9251) [INFO]         or
* 2024-12-07 03:10:21 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-07 03:10:21 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-07 03:10:21 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-07 03:10:21 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-07 03:10:21 (9251) [INFO]         compromise:
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-07 03:10:21 (9251) [INFO] 
* 2024-12-07 03:10:21 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-07 03:10:21 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 03:10:21 (9268) [INFO] 
* 2024-12-07 03:10:21 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-07 03:10:21 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-07 03:10:22 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-07 03:10:23 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UYSxaw5YOw/ea_profile.json
* 2024-12-07 03:10:25 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/UYSxaw5YOw/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-07 03:10:25 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-08 03:10:17 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-08 03:10:17 (10313) [INFO] Script is up to date.
* 2024-12-08 03:10:19 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-08 03:10:19 (9238) [INFO] 
* 2024-12-08 03:10:23 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-08 03:10:23 (9238) [INFO] 
* 2024-12-08 03:10:28 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-08 03:10:28 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-08 03:10:28 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-08 03:10:28 (9238) [INFO] 
* 2024-12-08 03:10:28 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 03:10:28 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-08 03:10:29 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-08 03:10:29 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-08 03:10:29 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-08 03:10:29 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 03:10:29 (9251) [INFO] Trying other mirror.
* 2024-12-08 03:10:29 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-08 03:10:29 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-08 03:10:29 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-08 03:10:29 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-08 03:10:29 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-08 03:10:29 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-08 03:10:29 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-08 03:10:29 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-08 03:10:29 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-08 03:10:29 (9251) [INFO]         or
* 2024-12-08 03:10:29 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-08 03:10:29 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-08 03:10:29 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-08 03:10:29 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-08 03:10:29 (9251) [INFO]         compromise:
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-08 03:10:29 (9251) [INFO] 
* 2024-12-08 03:10:29 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-08 03:10:29 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 03:10:30 (9268) [INFO] 
* 2024-12-08 03:10:30 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 03:10:30 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-08 03:10:30 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-08 03:10:30 (9238) [INFO] 
* 2024-12-08 03:10:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 03:10:30 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-08 03:10:30 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-08 03:10:30 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-08 03:10:30 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-08 03:10:30 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-08 03:10:30 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-08 03:10:30 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-08 03:10:30 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-08 03:10:30 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-08 03:10:30 (9268) [INFO] 
* 2024-12-08 03:10:30 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-08 03:10:30 (9238) [INFO] 
* 2024-12-08 03:10:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-08 03:10:30 (9251) [INFO] Determining fastest mirrors
* 2024-12-08 03:10:31 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-08 03:10:31 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-08 03:10:31 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-08 03:10:32 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 03:10:32 (9251) [INFO] Trying other mirror.
* 2024-12-08 03:10:32 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-08 03:10:32 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-08 03:10:32 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-08 03:10:32 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-08 03:10:32 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-08 03:10:32 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-08 03:10:32 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-08 03:10:32 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-08 03:10:32 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-08 03:10:32 (9251) [INFO]         or
* 2024-12-08 03:10:32 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-08 03:10:32 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-08 03:10:32 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-08 03:10:32 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-08 03:10:32 (9251) [INFO]         compromise:
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-08 03:10:32 (9251) [INFO] 
* 2024-12-08 03:10:32 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-08 03:10:32 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 03:10:32 (9268) [INFO] 
* 2024-12-08 03:10:32 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-08 03:10:32 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-08 03:10:33 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-08 03:10:34 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RvyyDRwUYO/ea_profile.json
* 2024-12-08 03:10:36 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/RvyyDRwUYO/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-08 03:10:36 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-09 03:09:01 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-09 03:09:01 (10313) [INFO] Script is up to date.
* 2024-12-09 03:09:03 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-09 03:09:03 (9238) [INFO] 
* 2024-12-09 03:09:07 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-09 03:09:07 (9238) [INFO] 
* 2024-12-09 03:09:12 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-09 03:09:12 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-09 03:09:12 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-09 03:09:12 (9238) [INFO] 
* 2024-12-09 03:09:12 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 03:09:12 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-09 03:09:13 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-09 03:09:13 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-09 03:09:13 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-09 03:09:14 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 03:09:14 (9251) [INFO] Trying other mirror.
* 2024-12-09 03:09:14 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-09 03:09:14 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 03:09:14 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 03:09:14 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-09 03:09:14 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-09 03:09:14 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-09 03:09:14 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 03:09:14 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-09 03:09:14 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-09 03:09:14 (9251) [INFO]         or
* 2024-12-09 03:09:14 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 03:09:14 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 03:09:14 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 03:09:14 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 03:09:14 (9251) [INFO]         compromise:
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-09 03:09:14 (9251) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-09 03:09:14 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 03:09:14 (9268) [INFO] 
* 2024-12-09 03:09:14 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 03:09:14 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-09 03:09:14 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-09 03:09:14 (9238) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 03:09:14 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-09 03:09:14 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-09 03:09:14 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-09 03:09:14 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-09 03:09:14 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-09 03:09:14 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-09 03:09:14 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-09 03:09:14 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-09 03:09:14 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-09 03:09:14 (9268) [INFO] 
* 2024-12-09 03:09:14 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-09 03:09:14 (9238) [INFO] 
* 2024-12-09 03:09:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-09 03:09:15 (9251) [INFO] Determining fastest mirrors
* 2024-12-09 03:09:16 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-09 03:09:16 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-09 03:09:16 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-09 03:09:17 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 03:09:17 (9251) [INFO] Trying other mirror.
* 2024-12-09 03:09:17 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-09 03:09:17 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-09 03:09:17 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-09 03:09:17 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-09 03:09:17 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-09 03:09:17 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-09 03:09:17 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-09 03:09:17 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-09 03:09:17 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-09 03:09:17 (9251) [INFO]         or
* 2024-12-09 03:09:17 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-09 03:09:17 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-09 03:09:17 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-09 03:09:17 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-09 03:09:17 (9251) [INFO]         compromise:
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-09 03:09:17 (9251) [INFO] 
* 2024-12-09 03:09:17 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-09 03:09:17 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 03:09:17 (9268) [INFO] 
* 2024-12-09 03:09:17 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-09 03:09:17 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-09 03:09:17 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-09 03:09:18 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/loiLxllKAa/ea_profile.json
* 2024-12-09 03:09:20 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/loiLxllKAa/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-09 03:09:20 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-10 03:09:04 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-10 03:09:04 (10313) [INFO] Script is up to date.
* 2024-12-10 03:09:05 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-10 03:09:05 (9238) [INFO] 
* 2024-12-10 03:09:11 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-10 03:09:11 (9238) [INFO] 
* 2024-12-10 03:09:17 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-10 03:09:17 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-10 03:09:17 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-10 03:09:17 (9238) [INFO] 
* 2024-12-10 03:09:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 03:09:18 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-10 03:09:19 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-10 03:09:19 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-10 03:09:19 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-10 03:09:19 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 03:09:19 (9251) [INFO] Trying other mirror.
* 2024-12-10 03:09:19 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-10 03:09:19 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 03:09:19 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 03:09:19 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-10 03:09:19 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-10 03:09:19 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-10 03:09:19 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 03:09:19 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-10 03:09:19 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-10 03:09:19 (9251) [INFO]         or
* 2024-12-10 03:09:19 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 03:09:19 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 03:09:19 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 03:09:19 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 03:09:19 (9251) [INFO]         compromise:
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-10 03:09:19 (9251) [INFO] 
* 2024-12-10 03:09:19 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-10 03:09:19 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 03:09:19 (9268) [INFO] 
* 2024-12-10 03:09:19 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 03:09:19 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-10 03:09:19 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-10 03:09:19 (9238) [INFO] 
* 2024-12-10 03:09:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 03:09:20 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-10 03:09:20 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-10 03:09:20 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-10 03:09:20 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-10 03:09:20 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-10 03:09:20 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-10 03:09:20 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-10 03:09:20 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-10 03:09:20 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-10 03:09:20 (9268) [INFO] 
* 2024-12-10 03:09:20 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-10 03:09:20 (9238) [INFO] 
* 2024-12-10 03:09:20 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-10 03:09:20 (9251) [INFO] Determining fastest mirrors
* 2024-12-10 03:09:22 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-10 03:09:22 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-10 03:09:22 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-10 03:09:23 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 03:09:23 (9251) [INFO] Trying other mirror.
* 2024-12-10 03:09:23 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-10 03:09:23 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-10 03:09:23 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-10 03:09:23 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-10 03:09:23 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-10 03:09:23 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-10 03:09:23 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-10 03:09:23 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-10 03:09:23 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-10 03:09:23 (9251) [INFO]         or
* 2024-12-10 03:09:23 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-10 03:09:23 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-10 03:09:23 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-10 03:09:23 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-10 03:09:23 (9251) [INFO]         compromise:
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-10 03:09:23 (9251) [INFO] 
* 2024-12-10 03:09:23 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-10 03:09:23 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 03:09:23 (9268) [INFO] 
* 2024-12-10 03:09:23 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-10 03:09:23 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-10 03:09:23 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-10 03:09:24 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ONYGN12ZLp/ea_profile.json
* 2024-12-10 03:09:27 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/ONYGN12ZLp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-10 03:09:27 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-11 03:09:41 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-11 03:09:41 (10313) [INFO] Script is up to date.
* 2024-12-11 03:09:43 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-11 03:09:43 (9238) [INFO] 
* 2024-12-11 03:09:44 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-11 03:09:44 (9238) [INFO] 
* 2024-12-11 03:09:51 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-11 03:09:51 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-11 03:09:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-11 03:09:51 (9238) [INFO] 
* 2024-12-11 03:09:51 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 03:09:51 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-11 03:09:52 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-11 03:09:52 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-11 03:09:52 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-11 03:09:53 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 03:09:53 (9251) [INFO] Trying other mirror.
* 2024-12-11 03:09:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-11 03:09:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 03:09:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 03:09:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-11 03:09:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-11 03:09:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-11 03:09:53 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 03:09:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-11 03:09:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-11 03:09:53 (9251) [INFO]         or
* 2024-12-11 03:09:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 03:09:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 03:09:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 03:09:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 03:09:53 (9251) [INFO]         compromise:
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-11 03:09:53 (9251) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-11 03:09:53 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 03:09:53 (9268) [INFO] 
* 2024-12-11 03:09:53 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 03:09:53 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-11 03:09:53 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-11 03:09:53 (9238) [INFO] 
* 2024-12-11 03:09:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 03:09:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-11 03:09:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-11 03:09:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-11 03:09:53 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-11 03:09:53 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-11 03:09:53 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-11 03:09:53 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-11 03:09:53 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-11 03:09:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-11 03:09:53 (9268) [INFO] 
* 2024-12-11 03:09:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-11 03:09:53 (9238) [INFO] 
* 2024-12-11 03:09:54 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-11 03:09:54 (9251) [INFO] Determining fastest mirrors
* 2024-12-11 03:09:56 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-11 03:09:56 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-11 03:09:56 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-11 03:09:56 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 03:09:56 (9251) [INFO] Trying other mirror.
* 2024-12-11 03:09:56 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-11 03:09:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-11 03:09:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-11 03:09:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-11 03:09:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-11 03:09:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-11 03:09:56 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-11 03:09:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-11 03:09:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-11 03:09:56 (9251) [INFO]         or
* 2024-12-11 03:09:56 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-11 03:09:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-11 03:09:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-11 03:09:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-11 03:09:56 (9251) [INFO]         compromise:
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-11 03:09:56 (9251) [INFO] 
* 2024-12-11 03:09:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-11 03:09:57 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 03:09:57 (9268) [INFO] 
* 2024-12-11 03:09:57 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-11 03:09:57 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-11 03:09:57 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-11 03:09:58 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HMDLiMQEMH/ea_profile.json
* 2024-12-11 03:10:00 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HMDLiMQEMH/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-11 03:10:00 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-12 03:08:50 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-12 03:08:50 (10313) [INFO] Script is up to date.
* 2024-12-12 03:08:51 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-12 03:08:51 (9238) [INFO] 
* 2024-12-12 03:08:56 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-12 03:08:56 (9238) [INFO] 
* 2024-12-12 03:09:00 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-12 03:09:00 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-12 03:09:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-12 03:09:00 (9238) [INFO] 
* 2024-12-12 03:09:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 03:09:01 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-12 03:09:01 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-12 03:09:01 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-12 03:09:01 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-12 03:09:02 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 03:09:02 (9251) [INFO] Trying other mirror.
* 2024-12-12 03:09:02 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-12 03:09:02 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 03:09:02 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 03:09:02 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-12 03:09:02 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-12 03:09:02 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-12 03:09:02 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 03:09:02 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-12 03:09:02 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-12 03:09:02 (9251) [INFO]         or
* 2024-12-12 03:09:02 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 03:09:02 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 03:09:02 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 03:09:02 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 03:09:02 (9251) [INFO]         compromise:
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-12 03:09:02 (9251) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-12 03:09:02 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 03:09:02 (9268) [INFO] 
* 2024-12-12 03:09:02 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 03:09:02 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-12 03:09:02 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-12 03:09:02 (9238) [INFO] 
* 2024-12-12 03:09:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 03:09:03 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-12 03:09:03 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-12 03:09:03 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-12 03:09:03 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-12 03:09:03 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-12 03:09:03 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-12 03:09:03 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-12 03:09:03 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-12 03:09:03 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-12 03:09:03 (9268) [INFO] 
* 2024-12-12 03:09:03 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-12 03:09:03 (9238) [INFO] 
* 2024-12-12 03:09:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-12 03:09:03 (9251) [INFO] Determining fastest mirrors
* 2024-12-12 03:09:05 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-12 03:09:05 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-12 03:09:05 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-12 03:09:05 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 03:09:05 (9251) [INFO] Trying other mirror.
* 2024-12-12 03:09:05 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-12 03:09:05 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-12 03:09:05 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-12 03:09:05 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-12 03:09:05 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-12 03:09:05 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-12 03:09:05 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-12 03:09:05 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-12 03:09:05 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-12 03:09:05 (9251) [INFO]         or
* 2024-12-12 03:09:05 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-12 03:09:05 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-12 03:09:05 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-12 03:09:05 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-12 03:09:05 (9251) [INFO]         compromise:
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-12 03:09:05 (9251) [INFO] 
* 2024-12-12 03:09:05 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-12 03:09:05 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 03:09:05 (9268) [INFO] 
* 2024-12-12 03:09:05 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-12 03:09:05 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-12 03:09:06 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-12 03:09:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pHji23gztn/ea_profile.json
* 2024-12-12 03:09:09 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/pHji23gztn/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-12 03:09:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-13 03:08:54 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-13 03:08:55 (10313) [INFO] Script is up to date.
* 2024-12-13 03:08:56 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-13 03:08:56 (9238) [INFO] 
* 2024-12-13 03:09:00 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-13 03:09:00 (9238) [INFO] 
* 2024-12-13 03:09:06 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-13 03:09:06 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-13 03:09:06 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-13 03:09:06 (9238) [INFO] 
* 2024-12-13 03:09:06 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 03:09:06 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-13 03:09:07 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-13 03:09:07 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-13 03:09:07 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-13 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 03:09:07 (9251) [INFO] Trying other mirror.
* 2024-12-13 03:09:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-13 03:09:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 03:09:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 03:09:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-13 03:09:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-13 03:09:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-13 03:09:07 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 03:09:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-13 03:09:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-13 03:09:07 (9251) [INFO]         or
* 2024-12-13 03:09:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 03:09:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 03:09:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 03:09:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 03:09:07 (9251) [INFO]         compromise:
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-13 03:09:07 (9251) [INFO] 
* 2024-12-13 03:09:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-13 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 03:09:07 (9268) [INFO] 
* 2024-12-13 03:09:07 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 03:09:07 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-13 03:09:07 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-13 03:09:07 (9238) [INFO] 
* 2024-12-13 03:09:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 03:09:08 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-13 03:09:08 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-13 03:09:08 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-13 03:09:08 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-13 03:09:08 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-13 03:09:08 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-13 03:09:08 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-13 03:09:08 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-13 03:09:08 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-13 03:09:08 (9268) [INFO] 
* 2024-12-13 03:09:08 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-13 03:09:08 (9238) [INFO] 
* 2024-12-13 03:09:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-13 03:09:09 (9251) [INFO] Determining fastest mirrors
* 2024-12-13 03:09:10 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-13 03:09:10 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-13 03:09:10 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-13 03:09:10 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 03:09:10 (9251) [INFO] Trying other mirror.
* 2024-12-13 03:09:10 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-13 03:09:10 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-13 03:09:10 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-13 03:09:10 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-13 03:09:10 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-13 03:09:10 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-13 03:09:10 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-13 03:09:10 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-13 03:09:10 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-13 03:09:10 (9251) [INFO]         or
* 2024-12-13 03:09:10 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-13 03:09:10 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-13 03:09:10 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-13 03:09:10 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-13 03:09:10 (9251) [INFO]         compromise:
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-13 03:09:10 (9251) [INFO] 
* 2024-12-13 03:09:10 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-13 03:09:10 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 03:09:10 (9268) [INFO] 
* 2024-12-13 03:09:10 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-13 03:09:10 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-13 03:09:11 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-13 03:09:11 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Nppsm1vVL7/ea_profile.json
* 2024-12-13 03:09:14 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Nppsm1vVL7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-13 03:09:14 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-14 03:12:10 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-14 03:12:10 (10313) [INFO] Script is up to date.
* 2024-12-14 03:12:13 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-14 03:12:13 (9238) [INFO] 
* 2024-12-14 03:12:22 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-14 03:12:22 (9238) [INFO] 
* 2024-12-14 03:12:30 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-14 03:12:30 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-14 03:12:30 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-14 03:12:30 (9238) [INFO] 
* 2024-12-14 03:12:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 03:12:31 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-14 03:12:31 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-14 03:12:31 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-14 03:12:31 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-14 03:12:32 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 03:12:32 (9251) [INFO] Trying other mirror.
* 2024-12-14 03:12:32 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-14 03:12:32 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 03:12:32 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 03:12:32 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-14 03:12:32 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-14 03:12:32 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-14 03:12:32 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 03:12:32 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-14 03:12:32 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-14 03:12:32 (9251) [INFO]         or
* 2024-12-14 03:12:32 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 03:12:32 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 03:12:32 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 03:12:32 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 03:12:32 (9251) [INFO]         compromise:
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-14 03:12:32 (9251) [INFO] 
* 2024-12-14 03:12:32 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-14 03:12:32 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 03:12:32 (9268) [INFO] 
* 2024-12-14 03:12:32 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 03:12:32 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-14 03:12:32 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-14 03:12:32 (9238) [INFO] 
* 2024-12-14 03:12:33 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 03:12:33 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-14 03:12:33 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-14 03:12:33 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-14 03:12:33 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-14 03:12:33 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-14 03:12:33 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-14 03:12:33 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-14 03:12:33 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-14 03:12:33 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-14 03:12:33 (9268) [INFO] 
* 2024-12-14 03:12:33 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-14 03:12:33 (9238) [INFO] 
* 2024-12-14 03:12:34 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-14 03:12:34 (9251) [INFO] Determining fastest mirrors
* 2024-12-14 03:12:36 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-14 03:12:36 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-14 03:12:36 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-14 03:12:36 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 03:12:36 (9251) [INFO] Trying other mirror.
* 2024-12-14 03:12:36 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-14 03:12:36 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-14 03:12:36 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-14 03:12:36 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-14 03:12:36 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-14 03:12:36 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-14 03:12:36 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-14 03:12:36 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-14 03:12:36 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-14 03:12:36 (9251) [INFO]         or
* 2024-12-14 03:12:36 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-14 03:12:36 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-14 03:12:36 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-14 03:12:36 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-14 03:12:36 (9251) [INFO]         compromise:
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-14 03:12:36 (9251) [INFO] 
* 2024-12-14 03:12:36 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-14 03:12:36 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 03:12:37 (9268) [INFO] 
* 2024-12-14 03:12:37 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-14 03:12:37 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-14 03:12:37 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-14 03:12:39 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cPd6jnLZMW/ea_profile.json
* 2024-12-14 03:12:42 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cPd6jnLZMW/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-14 03:12:42 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-15 03:10:37 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-15 03:10:37 (10313) [INFO] Script is up to date.
* 2024-12-15 03:10:38 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-15 03:10:38 (9238) [INFO] 
* 2024-12-15 03:10:43 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-15 03:10:43 (9238) [INFO] 
* 2024-12-15 03:10:47 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-15 03:10:47 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-15 03:10:47 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-15 03:10:47 (9238) [INFO] 
* 2024-12-15 03:10:48 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 03:10:48 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-15 03:10:49 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-15 03:10:49 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-15 03:10:49 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-15 03:10:49 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 03:10:49 (9251) [INFO] Trying other mirror.
* 2024-12-15 03:10:49 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-15 03:10:49 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 03:10:49 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 03:10:49 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-15 03:10:49 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-15 03:10:49 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-15 03:10:49 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 03:10:49 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-15 03:10:49 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-15 03:10:49 (9251) [INFO]         or
* 2024-12-15 03:10:49 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 03:10:49 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 03:10:49 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 03:10:49 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 03:10:49 (9251) [INFO]         compromise:
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-15 03:10:49 (9251) [INFO] 
* 2024-12-15 03:10:49 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-15 03:10:49 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 03:10:49 (9268) [INFO] 
* 2024-12-15 03:10:49 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 03:10:49 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-15 03:10:49 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-15 03:10:49 (9238) [INFO] 
* 2024-12-15 03:10:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 03:10:50 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-15 03:10:50 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-15 03:10:50 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-15 03:10:50 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-15 03:10:50 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-15 03:10:50 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-15 03:10:50 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-15 03:10:50 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-15 03:10:50 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-15 03:10:50 (9268) [INFO] 
* 2024-12-15 03:10:50 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-15 03:10:50 (9238) [INFO] 
* 2024-12-15 03:10:50 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-15 03:10:51 (9251) [INFO] Determining fastest mirrors
* 2024-12-15 03:10:53 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-15 03:10:53 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-15 03:10:53 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-15 03:10:53 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 03:10:53 (9251) [INFO] Trying other mirror.
* 2024-12-15 03:10:53 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-15 03:10:53 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-15 03:10:53 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-15 03:10:53 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-15 03:10:53 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-15 03:10:53 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-15 03:10:53 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-15 03:10:53 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-15 03:10:53 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-15 03:10:53 (9251) [INFO]         or
* 2024-12-15 03:10:53 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-15 03:10:53 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-15 03:10:53 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-15 03:10:53 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-15 03:10:53 (9251) [INFO]         compromise:
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-15 03:10:53 (9251) [INFO] 
* 2024-12-15 03:10:53 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-15 03:10:53 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 03:10:53 (9268) [INFO] 
* 2024-12-15 03:10:53 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-15 03:10:53 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-15 03:10:53 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-15 03:10:55 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HZL1jO7Ig4/ea_profile.json
* 2024-12-15 03:10:57 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/HZL1jO7Ig4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-15 03:10:57 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-16 03:09:47 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-16 03:09:47 (10313) [INFO] Script is up to date.
* 2024-12-16 03:09:49 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-16 03:09:49 (9238) [INFO] 
* 2024-12-16 03:09:53 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-16 03:09:53 (9238) [INFO] 
* 2024-12-16 03:09:57 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-16 03:09:57 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-16 03:09:57 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-16 03:09:57 (9238) [INFO] 
* 2024-12-16 03:09:57 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 03:09:57 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-16 03:09:58 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-16 03:09:58 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-16 03:09:58 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-16 03:09:58 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 03:09:58 (9251) [INFO] Trying other mirror.
* 2024-12-16 03:09:58 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-16 03:09:58 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 03:09:58 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 03:09:58 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-16 03:09:58 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-16 03:09:58 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-16 03:09:58 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 03:09:58 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-16 03:09:58 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-16 03:09:58 (9251) [INFO]         or
* 2024-12-16 03:09:58 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 03:09:58 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 03:09:58 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 03:09:58 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 03:09:58 (9251) [INFO]         compromise:
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-16 03:09:58 (9251) [INFO] 
* 2024-12-16 03:09:58 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-16 03:09:58 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 03:09:58 (9268) [INFO] 
* 2024-12-16 03:09:58 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 03:09:58 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-16 03:09:58 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-16 03:09:58 (9238) [INFO] 
* 2024-12-16 03:09:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 03:09:59 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-16 03:09:59 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-16 03:09:59 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-16 03:09:59 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-16 03:09:59 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-16 03:09:59 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-16 03:09:59 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-16 03:09:59 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-16 03:09:59 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-16 03:09:59 (9268) [INFO] 
* 2024-12-16 03:09:59 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-16 03:09:59 (9238) [INFO] 
* 2024-12-16 03:09:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-16 03:09:59 (9251) [INFO] Determining fastest mirrors
* 2024-12-16 03:10:00 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-16 03:10:00 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-16 03:10:00 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-16 03:10:01 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 03:10:01 (9251) [INFO] Trying other mirror.
* 2024-12-16 03:10:01 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-16 03:10:01 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-16 03:10:01 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-16 03:10:01 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-16 03:10:01 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-16 03:10:01 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-16 03:10:01 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-16 03:10:01 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-16 03:10:01 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-16 03:10:01 (9251) [INFO]         or
* 2024-12-16 03:10:01 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-16 03:10:01 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-16 03:10:01 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-16 03:10:01 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-16 03:10:01 (9251) [INFO]         compromise:
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-16 03:10:01 (9251) [INFO] 
* 2024-12-16 03:10:01 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-16 03:10:01 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 03:10:01 (9268) [INFO] 
* 2024-12-16 03:10:01 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-16 03:10:01 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-16 03:10:02 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-16 03:10:03 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q8fbabGUfp/ea_profile.json
* 2024-12-16 03:10:06 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/q8fbabGUfp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-16 03:10:06 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-17 03:09:12 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-17 03:09:12 (10313) [INFO] Script is up to date.
* 2024-12-17 03:09:14 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-17 03:09:14 (9238) [INFO] 
* 2024-12-17 03:09:19 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-17 03:09:19 (9238) [INFO] 
* 2024-12-17 03:09:25 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-17 03:09:25 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-17 03:09:25 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-17 03:09:25 (9238) [INFO] 
* 2024-12-17 03:09:25 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 03:09:25 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-17 03:09:26 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-17 03:09:26 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-17 03:09:26 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-17 03:09:26 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 03:09:26 (9251) [INFO] Trying other mirror.
* 2024-12-17 03:09:26 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-17 03:09:26 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 03:09:26 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 03:09:26 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-17 03:09:26 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-17 03:09:26 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-17 03:09:26 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 03:09:26 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-17 03:09:26 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-17 03:09:26 (9251) [INFO]         or
* 2024-12-17 03:09:26 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 03:09:26 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 03:09:26 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 03:09:26 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 03:09:26 (9251) [INFO]         compromise:
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-17 03:09:26 (9251) [INFO] 
* 2024-12-17 03:09:26 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-17 03:09:26 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 03:09:26 (9268) [INFO] 
* 2024-12-17 03:09:26 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 03:09:26 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-17 03:09:26 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-17 03:09:26 (9238) [INFO] 
* 2024-12-17 03:09:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 03:09:27 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-17 03:09:27 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-17 03:09:27 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-17 03:09:27 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-17 03:09:27 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-17 03:09:27 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-17 03:09:27 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-17 03:09:27 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-17 03:09:27 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-17 03:09:27 (9268) [INFO] 
* 2024-12-17 03:09:27 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-17 03:09:27 (9238) [INFO] 
* 2024-12-17 03:09:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-17 03:09:27 (9251) [INFO] Determining fastest mirrors
* 2024-12-17 03:09:29 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-17 03:09:29 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-17 03:09:29 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-17 03:09:30 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 03:09:30 (9251) [INFO] Trying other mirror.
* 2024-12-17 03:09:30 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-17 03:09:30 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-17 03:09:30 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-17 03:09:30 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-17 03:09:30 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-17 03:09:30 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-17 03:09:30 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-17 03:09:30 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-17 03:09:30 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-17 03:09:30 (9251) [INFO]         or
* 2024-12-17 03:09:30 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-17 03:09:30 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-17 03:09:30 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-17 03:09:30 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-17 03:09:30 (9251) [INFO]         compromise:
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-17 03:09:30 (9251) [INFO] 
* 2024-12-17 03:09:30 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-17 03:09:30 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 03:09:30 (9268) [INFO] 
* 2024-12-17 03:09:30 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-17 03:09:30 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-17 03:09:31 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-17 03:09:32 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YqO7OnvAgh/ea_profile.json
* 2024-12-17 03:09:34 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/YqO7OnvAgh/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-17 03:09:34 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-18 03:08:53 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-18 03:08:53 (10313) [INFO] Script is up to date.
* 2024-12-18 03:08:54 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-18 03:08:54 (9238) [INFO] 
* 2024-12-18 03:08:58 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-18 03:08:58 (9238) [INFO] 
* 2024-12-18 03:09:05 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-18 03:09:05 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-18 03:09:05 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-18 03:09:05 (9238) [INFO] 
* 2024-12-18 03:09:06 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 03:09:06 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-18 03:09:06 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-18 03:09:06 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-18 03:09:06 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-18 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 03:09:07 (9251) [INFO] Trying other mirror.
* 2024-12-18 03:09:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-18 03:09:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 03:09:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 03:09:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-18 03:09:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-18 03:09:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-18 03:09:07 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 03:09:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-18 03:09:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-18 03:09:07 (9251) [INFO]         or
* 2024-12-18 03:09:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 03:09:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 03:09:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 03:09:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 03:09:07 (9251) [INFO]         compromise:
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-18 03:09:07 (9251) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-18 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 03:09:07 (9268) [INFO] 
* 2024-12-18 03:09:07 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 03:09:07 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-18 03:09:07 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-18 03:09:07 (9238) [INFO] 
* 2024-12-18 03:09:07 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 03:09:07 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-18 03:09:07 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-18 03:09:07 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-18 03:09:07 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-18 03:09:07 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-18 03:09:07 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-18 03:09:07 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-18 03:09:07 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-18 03:09:07 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-18 03:09:07 (9268) [INFO] 
* 2024-12-18 03:09:07 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-18 03:09:07 (9238) [INFO] 
* 2024-12-18 03:09:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-18 03:09:08 (9251) [INFO] Determining fastest mirrors
* 2024-12-18 03:09:09 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-18 03:09:09 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-18 03:09:09 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-18 03:09:09 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 03:09:09 (9251) [INFO] Trying other mirror.
* 2024-12-18 03:09:09 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-18 03:09:09 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-18 03:09:09 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-18 03:09:09 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-18 03:09:09 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-18 03:09:09 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-18 03:09:09 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-18 03:09:09 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-18 03:09:09 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-18 03:09:09 (9251) [INFO]         or
* 2024-12-18 03:09:09 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-18 03:09:09 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-18 03:09:09 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-18 03:09:09 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-18 03:09:09 (9251) [INFO]         compromise:
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-18 03:09:09 (9251) [INFO] 
* 2024-12-18 03:09:09 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-18 03:09:09 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 03:09:09 (9268) [INFO] 
* 2024-12-18 03:09:09 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-18 03:09:09 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-18 03:09:10 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-18 03:09:11 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eqwY2a6rxp/ea_profile.json
* 2024-12-18 03:09:13 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/eqwY2a6rxp/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-18 03:09:13 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-19 03:09:06 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-19 03:09:06 (10313) [INFO] Script is up to date.
* 2024-12-19 03:09:07 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-19 03:09:07 (9238) [INFO] 
* 2024-12-19 03:09:12 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-19 03:09:12 (9238) [INFO] 
* 2024-12-19 03:09:17 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-19 03:09:17 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-19 03:09:17 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-19 03:09:17 (9238) [INFO] 
* 2024-12-19 03:09:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 03:09:17 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-19 03:09:17 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-19 03:09:17 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-19 03:09:17 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-19 03:09:18 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 03:09:18 (9251) [INFO] Trying other mirror.
* 2024-12-19 03:09:18 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-19 03:09:18 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 03:09:18 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 03:09:18 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-19 03:09:18 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-19 03:09:18 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-19 03:09:18 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 03:09:18 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-19 03:09:18 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-19 03:09:18 (9251) [INFO]         or
* 2024-12-19 03:09:18 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 03:09:18 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 03:09:18 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 03:09:18 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 03:09:18 (9251) [INFO]         compromise:
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-19 03:09:18 (9251) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-19 03:09:18 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 03:09:18 (9268) [INFO] 
* 2024-12-19 03:09:18 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 03:09:18 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-19 03:09:18 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-19 03:09:18 (9238) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 03:09:18 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-19 03:09:18 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-19 03:09:18 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-19 03:09:18 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-19 03:09:18 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-19 03:09:18 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-19 03:09:18 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-19 03:09:18 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-19 03:09:18 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-19 03:09:18 (9268) [INFO] 
* 2024-12-19 03:09:18 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-19 03:09:18 (9238) [INFO] 
* 2024-12-19 03:09:18 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-19 03:09:18 (9251) [INFO] Determining fastest mirrors
* 2024-12-19 03:09:20 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-19 03:09:20 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-19 03:09:20 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-19 03:09:20 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 03:09:20 (9251) [INFO] Trying other mirror.
* 2024-12-19 03:09:20 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-19 03:09:20 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-19 03:09:20 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-19 03:09:20 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-19 03:09:20 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-19 03:09:20 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-19 03:09:20 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-19 03:09:20 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-19 03:09:20 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-19 03:09:20 (9251) [INFO]         or
* 2024-12-19 03:09:20 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-19 03:09:20 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-19 03:09:20 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-19 03:09:20 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-19 03:09:20 (9251) [INFO]         compromise:
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-19 03:09:20 (9251) [INFO] 
* 2024-12-19 03:09:20 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-19 03:09:20 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 03:09:20 (9268) [INFO] 
* 2024-12-19 03:09:20 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-19 03:09:20 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-19 03:09:21 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-19 03:09:22 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hxzijbztSk/ea_profile.json
* 2024-12-19 03:09:23 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hxzijbztSk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-19 03:09:23 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-20 03:08:52 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-20 03:08:53 (10313) [INFO] Script is up to date.
* 2024-12-20 03:08:54 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-20 03:08:54 (9238) [INFO] 
* 2024-12-20 03:08:55 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-20 03:08:55 (9238) [INFO] 
* 2024-12-20 03:09:00 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-20 03:09:00 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-20 03:09:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-20 03:09:00 (9238) [INFO] 
* 2024-12-20 03:09:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 03:09:00 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-20 03:09:01 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-20 03:09:01 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-20 03:09:01 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-20 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 03:09:03 (9251) [INFO] Trying other mirror.
* 2024-12-20 03:09:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-20 03:09:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 03:09:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 03:09:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-20 03:09:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-20 03:09:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-20 03:09:03 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 03:09:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-20 03:09:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-20 03:09:03 (9251) [INFO]         or
* 2024-12-20 03:09:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 03:09:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 03:09:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 03:09:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 03:09:03 (9251) [INFO]         compromise:
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-20 03:09:03 (9251) [INFO] 
* 2024-12-20 03:09:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-20 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 03:09:03 (9268) [INFO] 
* 2024-12-20 03:09:03 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 03:09:03 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-20 03:09:03 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-20 03:09:03 (9238) [INFO] 
* 2024-12-20 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 03:09:04 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-20 03:09:04 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-20 03:09:04 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-20 03:09:04 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-20 03:09:04 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-20 03:09:04 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-20 03:09:04 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-20 03:09:04 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-20 03:09:04 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-20 03:09:04 (9268) [INFO] 
* 2024-12-20 03:09:04 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-20 03:09:04 (9238) [INFO] 
* 2024-12-20 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-20 03:09:04 (9251) [INFO] Determining fastest mirrors
* 2024-12-20 03:09:07 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-20 03:09:07 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-20 03:09:07 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-20 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 03:09:07 (9251) [INFO] Trying other mirror.
* 2024-12-20 03:09:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-20 03:09:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-20 03:09:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-20 03:09:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-20 03:09:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-20 03:09:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-20 03:09:07 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-20 03:09:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-20 03:09:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-20 03:09:07 (9251) [INFO]         or
* 2024-12-20 03:09:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-20 03:09:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-20 03:09:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-20 03:09:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-20 03:09:07 (9251) [INFO]         compromise:
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-20 03:09:07 (9251) [INFO] 
* 2024-12-20 03:09:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-20 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 03:09:07 (9268) [INFO] 
* 2024-12-20 03:09:07 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-20 03:09:07 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-20 03:09:07 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-20 03:09:08 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tsxHoMrTMX/ea_profile.json
* 2024-12-20 03:09:11 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/tsxHoMrTMX/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-20 03:09:11 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-21 03:09:54 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-21 03:09:54 (10313) [INFO] Script is up to date.
* 2024-12-21 03:09:55 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-21 03:09:55 (9238) [INFO] 
* 2024-12-21 03:09:59 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-21 03:09:59 (9238) [INFO] 
* 2024-12-21 03:10:04 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-21 03:10:04 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-21 03:10:04 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-21 03:10:04 (9238) [INFO] 
* 2024-12-21 03:10:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 03:10:05 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-21 03:10:06 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-21 03:10:06 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-21 03:10:06 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-21 03:10:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 03:10:07 (9251) [INFO] Trying other mirror.
* 2024-12-21 03:10:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-21 03:10:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 03:10:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 03:10:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-21 03:10:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-21 03:10:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-21 03:10:07 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 03:10:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-21 03:10:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-21 03:10:07 (9251) [INFO]         or
* 2024-12-21 03:10:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 03:10:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 03:10:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 03:10:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 03:10:07 (9251) [INFO]         compromise:
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-21 03:10:07 (9251) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-21 03:10:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 03:10:07 (9268) [INFO] 
* 2024-12-21 03:10:07 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 03:10:07 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-21 03:10:07 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-21 03:10:07 (9238) [INFO] 
* 2024-12-21 03:10:07 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 03:10:07 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-21 03:10:07 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-21 03:10:07 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-21 03:10:07 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-21 03:10:07 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-21 03:10:07 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-21 03:10:07 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-21 03:10:07 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-21 03:10:07 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-21 03:10:08 (9268) [INFO] 
* 2024-12-21 03:10:08 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-21 03:10:08 (9238) [INFO] 
* 2024-12-21 03:10:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-21 03:10:08 (9251) [INFO] Determining fastest mirrors
* 2024-12-21 03:10:11 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-21 03:10:11 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-21 03:10:11 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-21 03:10:12 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 03:10:12 (9251) [INFO] Trying other mirror.
* 2024-12-21 03:10:12 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-21 03:10:12 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-21 03:10:12 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-21 03:10:12 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-21 03:10:12 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-21 03:10:12 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-21 03:10:12 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-21 03:10:12 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-21 03:10:12 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-21 03:10:12 (9251) [INFO]         or
* 2024-12-21 03:10:12 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-21 03:10:12 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-21 03:10:12 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-21 03:10:12 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-21 03:10:12 (9251) [INFO]         compromise:
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-21 03:10:12 (9251) [INFO] 
* 2024-12-21 03:10:12 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-21 03:10:12 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 03:10:12 (9268) [INFO] 
* 2024-12-21 03:10:12 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-21 03:10:12 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-21 03:10:12 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-21 03:10:13 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8DLrvUCqhv/ea_profile.json
* 2024-12-21 03:10:16 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/8DLrvUCqhv/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-21 03:10:16 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-22 03:09:52 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-22 03:09:53 (10313) [INFO] Script is up to date.
* 2024-12-22 03:09:54 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-22 03:09:54 (9238) [INFO] 
* 2024-12-22 03:09:58 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-22 03:09:58 (9238) [INFO] 
* 2024-12-22 03:10:03 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-22 03:10:03 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-22 03:10:03 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-22 03:10:03 (9238) [INFO] 
* 2024-12-22 03:10:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 03:10:03 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-22 03:10:04 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-22 03:10:04 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-22 03:10:04 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-22 03:10:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 03:10:04 (9251) [INFO] Trying other mirror.
* 2024-12-22 03:10:04 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-22 03:10:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 03:10:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 03:10:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-22 03:10:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-22 03:10:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-22 03:10:04 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 03:10:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-22 03:10:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-22 03:10:04 (9251) [INFO]         or
* 2024-12-22 03:10:04 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 03:10:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 03:10:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 03:10:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 03:10:04 (9251) [INFO]         compromise:
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-22 03:10:04 (9251) [INFO] 
* 2024-12-22 03:10:04 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-22 03:10:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 03:10:04 (9268) [INFO] 
* 2024-12-22 03:10:04 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 03:10:04 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-22 03:10:04 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-22 03:10:04 (9238) [INFO] 
* 2024-12-22 03:10:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 03:10:05 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-22 03:10:05 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-22 03:10:05 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-22 03:10:05 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-22 03:10:05 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-22 03:10:05 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-22 03:10:05 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-22 03:10:05 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-22 03:10:05 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-22 03:10:05 (9268) [INFO] 
* 2024-12-22 03:10:05 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-22 03:10:05 (9238) [INFO] 
* 2024-12-22 03:10:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-22 03:10:05 (9251) [INFO] Determining fastest mirrors
* 2024-12-22 03:10:07 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-22 03:10:07 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-22 03:10:07 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-22 03:10:08 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 03:10:08 (9251) [INFO] Trying other mirror.
* 2024-12-22 03:10:08 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-22 03:10:08 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-22 03:10:08 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-22 03:10:08 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-22 03:10:08 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-22 03:10:08 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-22 03:10:08 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-22 03:10:08 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-22 03:10:08 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-22 03:10:08 (9251) [INFO]         or
* 2024-12-22 03:10:08 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-22 03:10:08 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-22 03:10:08 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-22 03:10:08 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-22 03:10:08 (9251) [INFO]         compromise:
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-22 03:10:08 (9251) [INFO] 
* 2024-12-22 03:10:08 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-22 03:10:08 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 03:10:08 (9268) [INFO] 
* 2024-12-22 03:10:08 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-22 03:10:08 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-22 03:10:08 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-22 03:10:09 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4kKsLlQziP/ea_profile.json
* 2024-12-22 03:10:11 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/4kKsLlQziP/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-22 03:10:11 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-23 03:08:56 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-23 03:08:56 (10313) [INFO] Script is up to date.
* 2024-12-23 03:08:58 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-23 03:08:58 (9238) [INFO] 
* 2024-12-23 03:09:03 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-23 03:09:03 (9238) [INFO] 
* 2024-12-23 03:09:06 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-23 03:09:06 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-23 03:09:06 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-23 03:09:06 (9238) [INFO] 
* 2024-12-23 03:09:07 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 03:09:07 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-23 03:09:07 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-23 03:09:07 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-23 03:09:07 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-23 03:09:08 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 03:09:08 (9251) [INFO] Trying other mirror.
* 2024-12-23 03:09:08 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-23 03:09:08 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 03:09:08 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 03:09:08 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-23 03:09:08 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-23 03:09:08 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-23 03:09:08 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 03:09:08 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-23 03:09:08 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-23 03:09:08 (9251) [INFO]         or
* 2024-12-23 03:09:08 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 03:09:08 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 03:09:08 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 03:09:08 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 03:09:08 (9251) [INFO]         compromise:
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-23 03:09:08 (9251) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-23 03:09:08 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 03:09:08 (9268) [INFO] 
* 2024-12-23 03:09:08 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 03:09:08 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-23 03:09:08 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-23 03:09:08 (9238) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 03:09:08 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-23 03:09:08 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-23 03:09:08 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-23 03:09:08 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-23 03:09:08 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-23 03:09:08 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-23 03:09:08 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-23 03:09:08 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-23 03:09:08 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-23 03:09:08 (9268) [INFO] 
* 2024-12-23 03:09:08 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-23 03:09:08 (9238) [INFO] 
* 2024-12-23 03:09:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-23 03:09:08 (9251) [INFO] Determining fastest mirrors
* 2024-12-23 03:09:09 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-23 03:09:09 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-23 03:09:09 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-23 03:09:10 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 03:09:10 (9251) [INFO] Trying other mirror.
* 2024-12-23 03:09:10 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-23 03:09:10 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-23 03:09:10 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-23 03:09:10 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-23 03:09:10 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-23 03:09:10 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-23 03:09:10 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-23 03:09:10 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-23 03:09:10 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-23 03:09:10 (9251) [INFO]         or
* 2024-12-23 03:09:10 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-23 03:09:10 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-23 03:09:10 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-23 03:09:10 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-23 03:09:10 (9251) [INFO]         compromise:
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-23 03:09:10 (9251) [INFO] 
* 2024-12-23 03:09:10 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-23 03:09:10 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 03:09:10 (9268) [INFO] 
* 2024-12-23 03:09:10 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-23 03:09:10 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-23 03:09:10 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-23 03:09:11 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CtCEp7_wu0/ea_profile.json
* 2024-12-23 03:09:13 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/CtCEp7_wu0/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-23 03:09:13 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-24 03:09:08 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-24 03:09:08 (10313) [INFO] Script is up to date.
* 2024-12-24 03:09:09 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-24 03:09:09 (9238) [INFO] 
* 2024-12-24 03:09:14 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-24 03:09:14 (9238) [INFO] 
* 2024-12-24 03:09:19 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-24 03:09:19 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-24 03:09:19 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-24 03:09:19 (9238) [INFO] 
* 2024-12-24 03:09:19 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 03:09:20 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-24 03:09:20 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-24 03:09:20 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-24 03:09:20 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-24 03:09:20 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 03:09:20 (9251) [INFO] Trying other mirror.
* 2024-12-24 03:09:20 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-24 03:09:20 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 03:09:20 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 03:09:20 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-24 03:09:20 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-24 03:09:20 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-24 03:09:20 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 03:09:20 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-24 03:09:20 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-24 03:09:20 (9251) [INFO]         or
* 2024-12-24 03:09:20 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 03:09:20 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 03:09:20 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 03:09:20 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 03:09:20 (9251) [INFO]         compromise:
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-24 03:09:20 (9251) [INFO] 
* 2024-12-24 03:09:20 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-24 03:09:20 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 03:09:21 (9268) [INFO] 
* 2024-12-24 03:09:21 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 03:09:21 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-24 03:09:21 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-24 03:09:21 (9238) [INFO] 
* 2024-12-24 03:09:21 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 03:09:21 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-24 03:09:21 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-24 03:09:21 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-24 03:09:21 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-24 03:09:21 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-24 03:09:21 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-24 03:09:21 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-24 03:09:21 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-24 03:09:21 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-24 03:09:21 (9268) [INFO] 
* 2024-12-24 03:09:21 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-24 03:09:21 (9238) [INFO] 
* 2024-12-24 03:09:21 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-24 03:09:21 (9251) [INFO] Determining fastest mirrors
* 2024-12-24 03:09:22 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-24 03:09:22 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-24 03:09:22 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-24 03:09:23 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 03:09:23 (9251) [INFO] Trying other mirror.
* 2024-12-24 03:09:23 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-24 03:09:23 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-24 03:09:23 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-24 03:09:23 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-24 03:09:23 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-24 03:09:23 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-24 03:09:23 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-24 03:09:23 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-24 03:09:23 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-24 03:09:23 (9251) [INFO]         or
* 2024-12-24 03:09:23 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-24 03:09:23 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-24 03:09:23 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-24 03:09:23 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-24 03:09:23 (9251) [INFO]         compromise:
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-24 03:09:23 (9251) [INFO] 
* 2024-12-24 03:09:23 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-24 03:09:23 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 03:09:23 (9268) [INFO] 
* 2024-12-24 03:09:23 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-24 03:09:23 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-24 03:09:23 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-24 03:09:24 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EyQi5xNzxU/ea_profile.json
* 2024-12-24 03:09:26 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EyQi5xNzxU/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-24 03:09:26 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-25 03:08:56 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-25 03:08:56 (10313) [INFO] Script is up to date.
* 2024-12-25 03:08:57 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-25 03:08:57 (9238) [INFO] 
* 2024-12-25 03:09:02 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-25 03:09:02 (9238) [INFO] 
* 2024-12-25 03:09:07 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-25 03:09:07 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-25 03:09:07 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-25 03:09:07 (9238) [INFO] 
* 2024-12-25 03:09:07 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 03:09:08 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-25 03:09:08 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-25 03:09:08 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-25 03:09:08 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-25 03:09:09 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 03:09:09 (9251) [INFO] Trying other mirror.
* 2024-12-25 03:09:09 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-25 03:09:09 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 03:09:09 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 03:09:09 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-25 03:09:09 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-25 03:09:09 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-25 03:09:09 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 03:09:09 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-25 03:09:09 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-25 03:09:09 (9251) [INFO]         or
* 2024-12-25 03:09:09 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 03:09:09 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 03:09:09 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 03:09:09 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 03:09:09 (9251) [INFO]         compromise:
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-25 03:09:09 (9251) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-25 03:09:09 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 03:09:09 (9268) [INFO] 
* 2024-12-25 03:09:09 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 03:09:09 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-25 03:09:09 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-25 03:09:09 (9238) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 03:09:09 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-25 03:09:09 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-25 03:09:09 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-25 03:09:09 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-25 03:09:09 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-25 03:09:09 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-25 03:09:09 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-25 03:09:09 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-25 03:09:09 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-25 03:09:09 (9268) [INFO] 
* 2024-12-25 03:09:09 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-25 03:09:09 (9238) [INFO] 
* 2024-12-25 03:09:09 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-25 03:09:10 (9251) [INFO] Determining fastest mirrors
* 2024-12-25 03:09:11 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-25 03:09:11 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-25 03:09:11 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-25 03:09:11 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 03:09:11 (9251) [INFO] Trying other mirror.
* 2024-12-25 03:09:11 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-25 03:09:11 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-25 03:09:11 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-25 03:09:11 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-25 03:09:11 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-25 03:09:11 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-25 03:09:11 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-25 03:09:11 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-25 03:09:11 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-25 03:09:11 (9251) [INFO]         or
* 2024-12-25 03:09:11 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-25 03:09:11 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-25 03:09:11 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-25 03:09:11 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-25 03:09:11 (9251) [INFO]         compromise:
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-25 03:09:11 (9251) [INFO] 
* 2024-12-25 03:09:11 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-25 03:09:11 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 03:09:11 (9268) [INFO] 
* 2024-12-25 03:09:11 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-25 03:09:11 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-25 03:09:12 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-25 03:09:13 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hUeWRVUz8_/ea_profile.json
* 2024-12-25 03:09:15 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/hUeWRVUz8_/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-25 03:09:15 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-26 03:08:57 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-26 03:08:57 (10313) [INFO] Script is up to date.
* 2024-12-26 03:08:59 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-26 03:08:59 (9238) [INFO] 
* 2024-12-26 03:09:07 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-26 03:09:07 (9238) [INFO] 
* 2024-12-26 03:09:14 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-26 03:09:14 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-26 03:09:14 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-26 03:09:14 (9238) [INFO] 
* 2024-12-26 03:09:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 03:09:14 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-26 03:09:15 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-26 03:09:15 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-26 03:09:15 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-26 03:09:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 03:09:16 (9251) [INFO] Trying other mirror.
* 2024-12-26 03:09:16 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-26 03:09:16 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 03:09:16 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 03:09:16 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-26 03:09:16 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-26 03:09:16 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-26 03:09:16 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 03:09:16 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-26 03:09:16 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-26 03:09:16 (9251) [INFO]         or
* 2024-12-26 03:09:16 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 03:09:16 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 03:09:16 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 03:09:16 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 03:09:16 (9251) [INFO]         compromise:
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-26 03:09:16 (9251) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-26 03:09:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 03:09:16 (9268) [INFO] 
* 2024-12-26 03:09:16 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 03:09:16 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-26 03:09:16 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-26 03:09:16 (9238) [INFO] 
* 2024-12-26 03:09:16 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 03:09:16 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-26 03:09:16 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-26 03:09:16 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-26 03:09:16 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-26 03:09:16 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-26 03:09:16 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-26 03:09:16 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-26 03:09:16 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-26 03:09:16 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-26 03:09:16 (9268) [INFO] 
* 2024-12-26 03:09:16 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-26 03:09:16 (9238) [INFO] 
* 2024-12-26 03:09:17 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-26 03:09:17 (9251) [INFO] Determining fastest mirrors
* 2024-12-26 03:09:18 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-26 03:09:18 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-26 03:09:18 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-26 03:09:19 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 03:09:19 (9251) [INFO] Trying other mirror.
* 2024-12-26 03:09:19 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-26 03:09:19 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-26 03:09:19 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-26 03:09:19 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-26 03:09:19 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-26 03:09:19 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-26 03:09:19 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-26 03:09:19 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-26 03:09:19 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-26 03:09:19 (9251) [INFO]         or
* 2024-12-26 03:09:19 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-26 03:09:19 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-26 03:09:19 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-26 03:09:19 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-26 03:09:19 (9251) [INFO]         compromise:
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-26 03:09:19 (9251) [INFO] 
* 2024-12-26 03:09:19 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-26 03:09:19 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 03:09:19 (9268) [INFO] 
* 2024-12-26 03:09:19 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-26 03:09:19 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-26 03:09:20 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-26 03:09:22 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TzvZ6EXEvB/ea_profile.json
* 2024-12-26 03:09:25 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/TzvZ6EXEvB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-26 03:09:25 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-27 03:08:55 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-27 03:08:56 (10313) [INFO] Script is up to date.
* 2024-12-27 03:08:57 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-27 03:08:57 (9238) [INFO] 
* 2024-12-27 03:09:04 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-27 03:09:04 (9238) [INFO] 
* 2024-12-27 03:09:09 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-27 03:09:09 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-27 03:09:09 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-27 03:09:09 (9238) [INFO] 
* 2024-12-27 03:09:09 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 03:09:10 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-27 03:09:12 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-27 03:09:12 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-27 03:09:12 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-27 03:09:13 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 03:09:13 (9251) [INFO] Trying other mirror.
* 2024-12-27 03:09:13 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-27 03:09:13 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 03:09:13 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 03:09:13 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-27 03:09:13 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-27 03:09:13 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-27 03:09:13 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 03:09:13 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-27 03:09:13 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-27 03:09:13 (9251) [INFO]         or
* 2024-12-27 03:09:13 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 03:09:13 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 03:09:13 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 03:09:13 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 03:09:13 (9251) [INFO]         compromise:
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-27 03:09:13 (9251) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-27 03:09:13 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 03:09:13 (9268) [INFO] 
* 2024-12-27 03:09:13 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 03:09:13 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-27 03:09:13 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-27 03:09:13 (9238) [INFO] 
* 2024-12-27 03:09:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 03:09:13 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-27 03:09:13 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-27 03:09:13 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-27 03:09:13 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-27 03:09:13 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-27 03:09:13 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-27 03:09:13 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-27 03:09:13 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-27 03:09:13 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-27 03:09:14 (9268) [INFO] 
* 2024-12-27 03:09:14 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-27 03:09:14 (9238) [INFO] 
* 2024-12-27 03:09:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-27 03:09:14 (9251) [INFO] Determining fastest mirrors
* 2024-12-27 03:09:15 (9251) [INFO]  * EA4: 185.157.208.252
* 2024-12-27 03:09:15 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2024-12-27 03:09:15 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2024-12-27 03:09:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 03:09:16 (9251) [INFO] Trying other mirror.
* 2024-12-27 03:09:16 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-27 03:09:16 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-27 03:09:16 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-27 03:09:16 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-27 03:09:16 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-27 03:09:16 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-27 03:09:16 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-27 03:09:16 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-27 03:09:16 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-27 03:09:16 (9251) [INFO]         or
* 2024-12-27 03:09:16 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-27 03:09:16 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-27 03:09:16 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-27 03:09:16 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-27 03:09:16 (9251) [INFO]         compromise:
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-27 03:09:16 (9251) [INFO] 
* 2024-12-27 03:09:16 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-27 03:09:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 03:09:16 (9268) [INFO] 
* 2024-12-27 03:09:16 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-27 03:09:16 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-27 03:09:16 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-27 03:09:17 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/J_ilBkLKcq/ea_profile.json
* 2024-12-27 03:09:21 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/J_ilBkLKcq/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-27 03:09:21 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-28 03:09:55 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-28 03:09:55 (10313) [INFO] Script is up to date.
* 2024-12-28 03:09:56 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-28 03:09:56 (9238) [INFO] 
* 2024-12-28 03:10:03 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-28 03:10:03 (9238) [INFO] 
* 2024-12-28 03:10:07 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-28 03:10:07 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-28 03:10:07 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-28 03:10:07 (9238) [INFO] 
* 2024-12-28 03:10:07 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 03:10:07 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-28 03:10:07 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-28 03:10:07 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-28 03:10:07 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-28 03:10:08 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 03:10:08 (9251) [INFO] Trying other mirror.
* 2024-12-28 03:10:08 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-28 03:10:08 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 03:10:08 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 03:10:08 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-28 03:10:08 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-28 03:10:08 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-28 03:10:08 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 03:10:08 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-28 03:10:08 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-28 03:10:08 (9251) [INFO]         or
* 2024-12-28 03:10:08 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 03:10:08 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 03:10:08 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 03:10:08 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 03:10:08 (9251) [INFO]         compromise:
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-28 03:10:08 (9251) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-28 03:10:08 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 03:10:08 (9268) [INFO] 
* 2024-12-28 03:10:08 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 03:10:08 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-28 03:10:08 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-28 03:10:08 (9238) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 03:10:08 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-28 03:10:08 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-28 03:10:08 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-28 03:10:08 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-28 03:10:08 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-28 03:10:08 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-28 03:10:08 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-28 03:10:08 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-28 03:10:08 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-28 03:10:08 (9268) [INFO] 
* 2024-12-28 03:10:08 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-28 03:10:08 (9238) [INFO] 
* 2024-12-28 03:10:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-28 03:10:09 (9251) [INFO] Determining fastest mirrors
* 2024-12-28 03:10:09 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-28 03:10:09 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-28 03:10:09 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-28 03:10:10 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 03:10:10 (9251) [INFO] Trying other mirror.
* 2024-12-28 03:10:10 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-28 03:10:10 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-28 03:10:10 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-28 03:10:10 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-28 03:10:10 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-28 03:10:10 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-28 03:10:10 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-28 03:10:10 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-28 03:10:10 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-28 03:10:10 (9251) [INFO]         or
* 2024-12-28 03:10:10 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-28 03:10:10 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-28 03:10:10 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-28 03:10:10 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-28 03:10:10 (9251) [INFO]         compromise:
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-28 03:10:10 (9251) [INFO] 
* 2024-12-28 03:10:10 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-28 03:10:10 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 03:10:10 (9268) [INFO] 
* 2024-12-28 03:10:10 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-28 03:10:10 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-28 03:10:10 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-28 03:10:12 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DvaTxTSUq3/ea_profile.json
* 2024-12-28 03:10:13 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/DvaTxTSUq3/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-28 03:10:13 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-29 03:09:48 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-29 03:09:48 (10313) [INFO] Script is up to date.
* 2024-12-29 03:09:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-29 03:09:50 (9238) [INFO] 
* 2024-12-29 03:09:54 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-29 03:09:54 (9238) [INFO] 
* 2024-12-29 03:09:58 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-29 03:09:58 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-29 03:09:58 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-29 03:09:58 (9238) [INFO] 
* 2024-12-29 03:09:58 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 03:09:58 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-29 03:09:59 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-29 03:09:59 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-29 03:09:59 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-29 03:10:00 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 03:10:00 (9251) [INFO] Trying other mirror.
* 2024-12-29 03:10:00 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-29 03:10:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 03:10:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 03:10:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-29 03:10:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-29 03:10:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-29 03:10:00 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 03:10:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-29 03:10:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-29 03:10:00 (9251) [INFO]         or
* 2024-12-29 03:10:00 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 03:10:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 03:10:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 03:10:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 03:10:00 (9251) [INFO]         compromise:
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-29 03:10:00 (9251) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-29 03:10:00 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 03:10:00 (9268) [INFO] 
* 2024-12-29 03:10:00 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 03:10:00 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-29 03:10:00 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-29 03:10:00 (9238) [INFO] 
* 2024-12-29 03:10:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 03:10:00 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-29 03:10:00 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-29 03:10:00 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-29 03:10:00 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-29 03:10:00 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-29 03:10:00 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-29 03:10:00 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-29 03:10:00 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-29 03:10:00 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-29 03:10:00 (9268) [INFO] 
* 2024-12-29 03:10:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-29 03:10:00 (9238) [INFO] 
* 2024-12-29 03:10:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-29 03:10:01 (9251) [INFO] Determining fastest mirrors
* 2024-12-29 03:10:02 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-29 03:10:02 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-29 03:10:02 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-29 03:10:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 03:10:03 (9251) [INFO] Trying other mirror.
* 2024-12-29 03:10:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-29 03:10:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-29 03:10:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-29 03:10:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-29 03:10:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-29 03:10:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-29 03:10:03 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-29 03:10:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-29 03:10:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-29 03:10:03 (9251) [INFO]         or
* 2024-12-29 03:10:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-29 03:10:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-29 03:10:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-29 03:10:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-29 03:10:03 (9251) [INFO]         compromise:
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-29 03:10:03 (9251) [INFO] 
* 2024-12-29 03:10:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-29 03:10:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 03:10:03 (9268) [INFO] 
* 2024-12-29 03:10:03 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-29 03:10:03 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-29 03:10:03 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-29 03:10:04 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NKgabfrhxk/ea_profile.json
* 2024-12-29 03:10:07 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/NKgabfrhxk/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-29 03:10:07 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-30 03:08:58 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-30 03:08:58 (10313) [INFO] Script is up to date.
* 2024-12-30 03:09:00 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-30 03:09:00 (9238) [INFO] 
* 2024-12-30 03:09:06 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-30 03:09:06 (9238) [INFO] 
* 2024-12-30 03:09:11 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-30 03:09:11 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-30 03:09:11 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-30 03:09:11 (9238) [INFO] 
* 2024-12-30 03:09:11 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 03:09:11 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-30 03:09:12 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-30 03:09:12 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-30 03:09:12 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-30 03:09:13 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 03:09:13 (9251) [INFO] Trying other mirror.
* 2024-12-30 03:09:13 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-30 03:09:13 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 03:09:13 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 03:09:13 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-30 03:09:13 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-30 03:09:13 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-30 03:09:13 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 03:09:13 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-30 03:09:13 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-30 03:09:13 (9251) [INFO]         or
* 2024-12-30 03:09:13 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 03:09:13 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 03:09:13 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 03:09:13 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 03:09:13 (9251) [INFO]         compromise:
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-30 03:09:13 (9251) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-30 03:09:13 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 03:09:13 (9268) [INFO] 
* 2024-12-30 03:09:13 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 03:09:13 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-30 03:09:13 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-30 03:09:13 (9238) [INFO] 
* 2024-12-30 03:09:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 03:09:13 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-30 03:09:13 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-30 03:09:13 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-30 03:09:13 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-30 03:09:13 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-30 03:09:13 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-30 03:09:13 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-30 03:09:13 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-30 03:09:13 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-30 03:09:13 (9268) [INFO] 
* 2024-12-30 03:09:13 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-30 03:09:13 (9238) [INFO] 
* 2024-12-30 03:09:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-30 03:09:14 (9251) [INFO] Determining fastest mirrors
* 2024-12-30 03:09:15 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-30 03:09:15 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-30 03:09:15 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-30 03:09:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 03:09:16 (9251) [INFO] Trying other mirror.
* 2024-12-30 03:09:16 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-30 03:09:16 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-30 03:09:16 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-30 03:09:16 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-30 03:09:16 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-30 03:09:16 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-30 03:09:16 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-30 03:09:16 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-30 03:09:16 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-30 03:09:16 (9251) [INFO]         or
* 2024-12-30 03:09:16 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-30 03:09:16 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-30 03:09:16 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-30 03:09:16 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-30 03:09:16 (9251) [INFO]         compromise:
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-30 03:09:16 (9251) [INFO] 
* 2024-12-30 03:09:16 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-30 03:09:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 03:09:16 (9268) [INFO] 
* 2024-12-30 03:09:16 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-30 03:09:16 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-30 03:09:16 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-30 03:09:18 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kmE_33_9y4/ea_profile.json
* 2024-12-30 03:09:20 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kmE_33_9y4/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-30 03:09:20 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2024-12-31 03:08:53 (10291) [INFO] Self-update of script version 59 requested.
* 2024-12-31 03:08:53 (10313) [INFO] Script is up to date.
* 2024-12-31 03:08:55 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2024-12-31 03:08:55 (9238) [INFO] 
* 2024-12-31 03:08:56 (9237) [INFO] Running: /usr/bin/yum list extras
* 2024-12-31 03:08:56 (9238) [INFO] 
* 2024-12-31 03:09:00 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2024-12-31 03:09:00 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2024-12-31 03:09:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-31 03:09:00 (9238) [INFO] 
* 2024-12-31 03:09:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 03:09:01 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2024-12-31 03:09:01 (9251) [INFO]  * EA4: 31.22.112.31
* 2024-12-31 03:09:01 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2024-12-31 03:09:01 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2024-12-31 03:09:02 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 03:09:02 (9251) [INFO] Trying other mirror.
* 2024-12-31 03:09:02 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-31 03:09:02 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 03:09:02 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 03:09:02 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-31 03:09:02 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-31 03:09:02 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-31 03:09:02 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 03:09:02 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-31 03:09:02 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-31 03:09:02 (9251) [INFO]         or
* 2024-12-31 03:09:02 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 03:09:02 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 03:09:02 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 03:09:02 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 03:09:02 (9251) [INFO]         compromise:
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-31 03:09:02 (9251) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-31 03:09:02 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 03:09:02 (9268) [INFO] 
* 2024-12-31 03:09:02 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 03:09:02 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2024-12-31 03:09:02 (9237) [INFO] Running: /usr/bin/yum clean all
* 2024-12-31 03:09:02 (9238) [INFO] 
* 2024-12-31 03:09:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 03:09:03 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2024-12-31 03:09:03 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2024-12-31 03:09:03 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2024-12-31 03:09:03 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2024-12-31 03:09:03 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2024-12-31 03:09:03 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2024-12-31 03:09:03 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2024-12-31 03:09:03 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2024-12-31 03:09:03 (9251) [INFO] Cleaning up list of fastest mirrors
* 2024-12-31 03:09:03 (9268) [INFO] 
* 2024-12-31 03:09:03 (9237) [INFO] Running: /usr/bin/yum makecache
* 2024-12-31 03:09:03 (9238) [INFO] 
* 2024-12-31 03:09:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2024-12-31 03:09:03 (9251) [INFO] Determining fastest mirrors
* 2024-12-31 03:09:05 (9251) [INFO]  * EA4: 185.15.22.168
* 2024-12-31 03:09:05 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2024-12-31 03:09:05 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2024-12-31 03:09:05 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 03:09:05 (9251) [INFO] Trying other mirror.
* 2024-12-31 03:09:05 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2024-12-31 03:09:05 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2024-12-31 03:09:05 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2024-12-31 03:09:05 (9251) [INFO] 
* 2024-12-31 03:09:05 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2024-12-31 03:09:05 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2024-12-31 03:09:05 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2024-12-31 03:09:05 (9251) [INFO]         packages for the previous distribution release still work).
* 2024-12-31 03:09:06 (9251) [INFO] 
* 2024-12-31 03:09:06 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2024-12-31 03:09:06 (9251) [INFO]             yum --disablerepo=base ...
* 2024-12-31 03:09:06 (9251) [INFO] 
* 2024-12-31 03:09:06 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2024-12-31 03:09:06 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2024-12-31 03:09:06 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2024-12-31 03:09:06 (9251) [INFO] 
* 2024-12-31 03:09:06 (9251) [INFO]             yum-config-manager --disable base
* 2024-12-31 03:09:06 (9251) [INFO]         or
* 2024-12-31 03:09:06 (9251) [INFO]             subscription-manager repos --disable=base
* 2024-12-31 03:09:06 (9251) [INFO] 
* 2024-12-31 03:09:06 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2024-12-31 03:09:06 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2024-12-31 03:09:06 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2024-12-31 03:09:06 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2024-12-31 03:09:06 (9251) [INFO]         compromise:
* 2024-12-31 03:09:06 (9251) [INFO] 
* 2024-12-31 03:09:06 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2024-12-31 03:09:06 (9251) [INFO] 
* 2024-12-31 03:09:06 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2024-12-31 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 03:09:06 (9268) [INFO] 
* 2024-12-31 03:09:06 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2024-12-31 03:09:06 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2024-12-31 03:09:06 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2024-12-31 03:09:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qlb9o9N9wm/ea_profile.json
* 2024-12-31 03:09:09 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qlb9o9N9wm/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2024-12-31 03:09:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-01 03:08:49 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-01 03:08:49 (10313) [INFO] Script is up to date.
* 2025-01-01 03:08:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-01 03:08:50 (9238) [INFO] 
* 2025-01-01 03:08:55 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-01 03:08:55 (9238) [INFO] 
* 2025-01-01 03:09:01 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-01 03:09:01 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-01 03:09:01 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-01 03:09:01 (9238) [INFO] 
* 2025-01-01 03:09:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 03:09:02 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-01 03:09:03 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-01 03:09:03 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-01 03:09:03 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-01 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 03:09:03 (9251) [INFO] Trying other mirror.
* 2025-01-01 03:09:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-01 03:09:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 03:09:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 03:09:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-01 03:09:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-01 03:09:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-01 03:09:03 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 03:09:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-01 03:09:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-01 03:09:03 (9251) [INFO]         or
* 2025-01-01 03:09:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 03:09:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 03:09:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 03:09:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 03:09:03 (9251) [INFO]         compromise:
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-01 03:09:03 (9251) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-01 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 03:09:03 (9268) [INFO] 
* 2025-01-01 03:09:03 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 03:09:03 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-01 03:09:03 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-01 03:09:03 (9238) [INFO] 
* 2025-01-01 03:09:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 03:09:03 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-01 03:09:03 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-01 03:09:03 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-01 03:09:03 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-01 03:09:03 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-01 03:09:03 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-01 03:09:03 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-01 03:09:03 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-01 03:09:04 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-01 03:09:04 (9268) [INFO] 
* 2025-01-01 03:09:04 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-01 03:09:04 (9238) [INFO] 
* 2025-01-01 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-01 03:09:04 (9251) [INFO] Determining fastest mirrors
* 2025-01-01 03:09:05 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-01 03:09:05 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-01 03:09:05 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-01 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 03:09:06 (9251) [INFO] Trying other mirror.
* 2025-01-01 03:09:06 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-01 03:09:06 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-01 03:09:06 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-01 03:09:06 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-01 03:09:06 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-01 03:09:06 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-01 03:09:06 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-01 03:09:06 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-01 03:09:06 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-01 03:09:06 (9251) [INFO]         or
* 2025-01-01 03:09:06 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-01 03:09:06 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-01 03:09:06 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-01 03:09:06 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-01 03:09:06 (9251) [INFO]         compromise:
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-01 03:09:06 (9251) [INFO] 
* 2025-01-01 03:09:06 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-01 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 03:09:06 (9268) [INFO] 
* 2025-01-01 03:09:06 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-01 03:09:06 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-01 03:09:06 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-01 03:09:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BJAzFt_nrT/ea_profile.json
* 2025-01-01 03:09:10 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/BJAzFt_nrT/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-01 03:09:10 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-02 03:09:16 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-02 03:09:16 (10313) [INFO] Script is up to date.
* 2025-01-02 03:09:18 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-02 03:09:18 (9238) [INFO] 
* 2025-01-02 03:09:25 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-02 03:09:25 (9238) [INFO] 
* 2025-01-02 03:09:30 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-02 03:09:30 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-02 03:09:30 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-02 03:09:30 (9238) [INFO] 
* 2025-01-02 03:09:30 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 03:09:30 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-02 03:09:31 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-02 03:09:31 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-02 03:09:31 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-02 03:09:31 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 03:09:31 (9251) [INFO] Trying other mirror.
* 2025-01-02 03:09:31 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-02 03:09:31 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 03:09:31 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 03:09:31 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-02 03:09:31 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-02 03:09:31 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-02 03:09:31 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 03:09:31 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-02 03:09:31 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-02 03:09:31 (9251) [INFO]         or
* 2025-01-02 03:09:31 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 03:09:31 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 03:09:31 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 03:09:31 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 03:09:31 (9251) [INFO]         compromise:
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-02 03:09:31 (9251) [INFO] 
* 2025-01-02 03:09:31 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-02 03:09:31 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 03:09:31 (9268) [INFO] 
* 2025-01-02 03:09:31 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 03:09:31 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-02 03:09:31 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-02 03:09:31 (9238) [INFO] 
* 2025-01-02 03:09:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 03:09:32 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-02 03:09:32 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-02 03:09:32 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-02 03:09:32 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-02 03:09:32 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-02 03:09:32 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-02 03:09:32 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-02 03:09:32 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-02 03:09:32 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-02 03:09:32 (9268) [INFO] 
* 2025-01-02 03:09:32 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-02 03:09:32 (9238) [INFO] 
* 2025-01-02 03:09:32 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-02 03:09:32 (9251) [INFO] Determining fastest mirrors
* 2025-01-02 03:09:33 (9251) [INFO]  * EA4: 185.157.208.252
* 2025-01-02 03:09:33 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-01-02 03:09:33 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-01-02 03:09:34 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 03:09:34 (9251) [INFO] Trying other mirror.
* 2025-01-02 03:09:34 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-02 03:09:34 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-02 03:09:34 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-02 03:09:34 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-02 03:09:34 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-02 03:09:34 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-02 03:09:34 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-02 03:09:34 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-02 03:09:34 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-02 03:09:34 (9251) [INFO]         or
* 2025-01-02 03:09:34 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-02 03:09:34 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-02 03:09:34 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-02 03:09:34 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-02 03:09:34 (9251) [INFO]         compromise:
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-02 03:09:34 (9251) [INFO] 
* 2025-01-02 03:09:34 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-02 03:09:34 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 03:09:34 (9268) [INFO] 
* 2025-01-02 03:09:34 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-02 03:09:34 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-02 03:09:34 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-02 03:09:36 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/emwDsgsCIy/ea_profile.json
* 2025-01-02 03:09:38 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/emwDsgsCIy/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-02 03:09:38 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-03 03:08:50 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-03 03:08:50 (10313) [INFO] Script is up to date.
* 2025-01-03 03:08:52 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-03 03:08:52 (9238) [INFO] 
* 2025-01-03 03:08:55 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-03 03:08:55 (9238) [INFO] 
* 2025-01-03 03:09:00 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-03 03:09:00 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-03 03:09:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-03 03:09:00 (9238) [INFO] 
* 2025-01-03 03:09:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 03:09:01 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-03 03:09:02 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-03 03:09:02 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-03 03:09:02 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-03 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 03:09:03 (9251) [INFO] Trying other mirror.
* 2025-01-03 03:09:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-03 03:09:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 03:09:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 03:09:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-03 03:09:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-03 03:09:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-03 03:09:03 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 03:09:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-03 03:09:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-03 03:09:03 (9251) [INFO]         or
* 2025-01-03 03:09:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 03:09:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 03:09:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 03:09:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 03:09:03 (9251) [INFO]         compromise:
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-03 03:09:03 (9251) [INFO] 
* 2025-01-03 03:09:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-03 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 03:09:03 (9268) [INFO] 
* 2025-01-03 03:09:03 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 03:09:03 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-03 03:09:03 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-03 03:09:03 (9238) [INFO] 
* 2025-01-03 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 03:09:04 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-03 03:09:04 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-03 03:09:04 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-03 03:09:04 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-03 03:09:04 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-03 03:09:04 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-03 03:09:04 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-03 03:09:04 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-03 03:09:04 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-03 03:09:04 (9268) [INFO] 
* 2025-01-03 03:09:04 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-03 03:09:04 (9238) [INFO] 
* 2025-01-03 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-03 03:09:04 (9251) [INFO] Determining fastest mirrors
* 2025-01-03 03:09:07 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-03 03:09:07 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-03 03:09:07 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-03 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 03:09:07 (9251) [INFO] Trying other mirror.
* 2025-01-03 03:09:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-03 03:09:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-03 03:09:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-03 03:09:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-03 03:09:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-03 03:09:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-03 03:09:07 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-03 03:09:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-03 03:09:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-03 03:09:07 (9251) [INFO]         or
* 2025-01-03 03:09:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-03 03:09:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-03 03:09:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-03 03:09:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-03 03:09:07 (9251) [INFO]         compromise:
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-03 03:09:07 (9251) [INFO] 
* 2025-01-03 03:09:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-03 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 03:09:07 (9268) [INFO] 
* 2025-01-03 03:09:07 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-03 03:09:07 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-03 03:09:08 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-03 03:09:09 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Mhw9RQeGnR/ea_profile.json
* 2025-01-03 03:09:11 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Mhw9RQeGnR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-03 03:09:11 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-04 03:09:48 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-04 03:09:48 (10313) [INFO] Script is up to date.
* 2025-01-04 03:09:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-04 03:09:50 (9238) [INFO] 
* 2025-01-04 03:09:56 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-04 03:09:56 (9238) [INFO] 
* 2025-01-04 03:10:01 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-04 03:10:01 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-04 03:10:01 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-04 03:10:01 (9238) [INFO] 
* 2025-01-04 03:10:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 03:10:02 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-04 03:10:04 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-04 03:10:04 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-04 03:10:04 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-04 03:10:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 03:10:04 (9251) [INFO] Trying other mirror.
* 2025-01-04 03:10:04 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-04 03:10:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 03:10:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 03:10:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-04 03:10:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-04 03:10:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-04 03:10:04 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 03:10:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-04 03:10:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-04 03:10:04 (9251) [INFO]         or
* 2025-01-04 03:10:04 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 03:10:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 03:10:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 03:10:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 03:10:04 (9251) [INFO]         compromise:
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-04 03:10:04 (9251) [INFO] 
* 2025-01-04 03:10:04 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-04 03:10:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 03:10:04 (9268) [INFO] 
* 2025-01-04 03:10:04 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 03:10:04 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-04 03:10:04 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-04 03:10:04 (9238) [INFO] 
* 2025-01-04 03:10:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 03:10:05 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-04 03:10:05 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-04 03:10:05 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-04 03:10:05 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-04 03:10:05 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-04 03:10:05 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-04 03:10:05 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-04 03:10:05 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-04 03:10:05 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-04 03:10:05 (9268) [INFO] 
* 2025-01-04 03:10:05 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-04 03:10:05 (9238) [INFO] 
* 2025-01-04 03:10:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-04 03:10:05 (9251) [INFO] Determining fastest mirrors
* 2025-01-04 03:10:07 (9251) [INFO]  * EA4: 185.157.208.252
* 2025-01-04 03:10:07 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-01-04 03:10:07 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-01-04 03:10:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 03:10:07 (9251) [INFO] Trying other mirror.
* 2025-01-04 03:10:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-04 03:10:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-04 03:10:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-04 03:10:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-04 03:10:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-04 03:10:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-04 03:10:07 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-04 03:10:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-04 03:10:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-04 03:10:07 (9251) [INFO]         or
* 2025-01-04 03:10:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-04 03:10:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-04 03:10:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-04 03:10:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-04 03:10:07 (9251) [INFO]         compromise:
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-04 03:10:07 (9251) [INFO] 
* 2025-01-04 03:10:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-04 03:10:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 03:10:08 (9268) [INFO] 
* 2025-01-04 03:10:08 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-04 03:10:08 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-04 03:10:08 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-04 03:10:09 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PQDwgLtlx5/ea_profile.json
* 2025-01-04 03:10:12 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PQDwgLtlx5/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-04 03:10:12 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-05 03:09:58 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-05 03:09:58 (10313) [INFO] Script is up to date.
* 2025-01-05 03:09:59 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-05 03:09:59 (9238) [INFO] 
* 2025-01-05 03:10:05 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-05 03:10:05 (9238) [INFO] 
* 2025-01-05 03:10:11 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-05 03:10:11 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-05 03:10:11 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-05 03:10:11 (9238) [INFO] 
* 2025-01-05 03:10:12 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 03:10:12 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-05 03:10:13 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-05 03:10:13 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-05 03:10:13 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-05 03:10:14 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 03:10:14 (9251) [INFO] Trying other mirror.
* 2025-01-05 03:10:14 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-05 03:10:14 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 03:10:14 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 03:10:14 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-05 03:10:14 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-05 03:10:14 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-05 03:10:14 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 03:10:14 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-05 03:10:14 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-05 03:10:14 (9251) [INFO]         or
* 2025-01-05 03:10:14 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 03:10:14 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 03:10:14 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 03:10:14 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 03:10:14 (9251) [INFO]         compromise:
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-05 03:10:14 (9251) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-05 03:10:14 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 03:10:14 (9268) [INFO] 
* 2025-01-05 03:10:14 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 03:10:14 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-05 03:10:14 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-05 03:10:14 (9238) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 03:10:14 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-05 03:10:14 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-05 03:10:14 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-05 03:10:14 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-05 03:10:14 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-05 03:10:14 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-05 03:10:14 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-05 03:10:14 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-05 03:10:14 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-05 03:10:14 (9268) [INFO] 
* 2025-01-05 03:10:14 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-05 03:10:14 (9238) [INFO] 
* 2025-01-05 03:10:14 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-05 03:10:14 (9251) [INFO] Determining fastest mirrors
* 2025-01-05 03:10:16 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-05 03:10:16 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-05 03:10:16 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-05 03:10:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 03:10:16 (9251) [INFO] Trying other mirror.
* 2025-01-05 03:10:16 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-05 03:10:16 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-05 03:10:16 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-05 03:10:16 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-05 03:10:16 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-05 03:10:16 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-05 03:10:16 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-05 03:10:16 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-05 03:10:16 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-05 03:10:16 (9251) [INFO]         or
* 2025-01-05 03:10:16 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-05 03:10:16 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-05 03:10:16 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-05 03:10:16 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-05 03:10:16 (9251) [INFO]         compromise:
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-05 03:10:16 (9251) [INFO] 
* 2025-01-05 03:10:16 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-05 03:10:16 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 03:10:16 (9268) [INFO] 
* 2025-01-05 03:10:16 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-05 03:10:16 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-05 03:10:17 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-05 03:10:18 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/c8zAFPdo4k/ea_profile.json
* 2025-01-05 03:10:20 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/c8zAFPdo4k/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-05 03:10:20 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-06 03:08:57 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-06 03:08:58 (10313) [INFO] Script is up to date.
* 2025-01-06 03:08:59 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-06 03:08:59 (9238) [INFO] 
* 2025-01-06 03:09:03 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-06 03:09:03 (9238) [INFO] 
* 2025-01-06 03:09:08 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-06 03:09:08 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-06 03:09:08 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-06 03:09:08 (9238) [INFO] 
* 2025-01-06 03:09:08 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 03:09:08 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-06 03:09:09 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-06 03:09:09 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-06 03:09:09 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-06 03:09:09 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 03:09:09 (9251) [INFO] Trying other mirror.
* 2025-01-06 03:09:09 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-06 03:09:09 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 03:09:09 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 03:09:09 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-06 03:09:09 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-06 03:09:09 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-06 03:09:09 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 03:09:09 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-06 03:09:09 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-06 03:09:09 (9251) [INFO]         or
* 2025-01-06 03:09:09 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 03:09:09 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 03:09:09 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 03:09:09 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 03:09:09 (9251) [INFO]         compromise:
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-06 03:09:09 (9251) [INFO] 
* 2025-01-06 03:09:09 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-06 03:09:09 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 03:09:09 (9268) [INFO] 
* 2025-01-06 03:09:09 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 03:09:09 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-06 03:09:09 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-06 03:09:09 (9238) [INFO] 
* 2025-01-06 03:09:10 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 03:09:10 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-06 03:09:10 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-06 03:09:10 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-06 03:09:10 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-06 03:09:10 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-06 03:09:10 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-06 03:09:10 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-06 03:09:10 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-06 03:09:10 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-06 03:09:10 (9268) [INFO] 
* 2025-01-06 03:09:10 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-06 03:09:10 (9238) [INFO] 
* 2025-01-06 03:09:10 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-06 03:09:10 (9251) [INFO] Determining fastest mirrors
* 2025-01-06 03:09:11 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-06 03:09:11 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-06 03:09:11 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-06 03:09:11 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 03:09:11 (9251) [INFO] Trying other mirror.
* 2025-01-06 03:09:11 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-06 03:09:11 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-06 03:09:11 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-06 03:09:11 (9251) [INFO] 
* 2025-01-06 03:09:11 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-06 03:09:12 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-06 03:09:12 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-06 03:09:12 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-06 03:09:12 (9251) [INFO] 
* 2025-01-06 03:09:12 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-06 03:09:12 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-06 03:09:12 (9251) [INFO] 
* 2025-01-06 03:09:12 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-06 03:09:12 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-06 03:09:12 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-06 03:09:12 (9251) [INFO] 
* 2025-01-06 03:09:12 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-06 03:09:12 (9251) [INFO]         or
* 2025-01-06 03:09:12 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-06 03:09:12 (9251) [INFO] 
* 2025-01-06 03:09:12 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-06 03:09:12 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-06 03:09:12 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-06 03:09:12 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-06 03:09:12 (9251) [INFO]         compromise:
* 2025-01-06 03:09:12 (9251) [INFO] 
* 2025-01-06 03:09:12 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-06 03:09:12 (9251) [INFO] 
* 2025-01-06 03:09:12 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-06 03:09:12 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 03:09:12 (9268) [INFO] 
* 2025-01-06 03:09:12 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-06 03:09:12 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-06 03:09:12 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-06 03:09:13 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EyfYfXFISt/ea_profile.json
* 2025-01-06 03:09:15 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/EyfYfXFISt/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-06 03:09:15 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-07 03:08:52 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-07 03:08:52 (10313) [INFO] Script is up to date.
* 2025-01-07 03:08:54 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-07 03:08:54 (9238) [INFO] 
* 2025-01-07 03:08:58 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-07 03:08:58 (9238) [INFO] 
* 2025-01-07 03:09:03 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-07 03:09:03 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-07 03:09:03 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-07 03:09:03 (9238) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 03:09:04 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-07 03:09:04 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-07 03:09:04 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-07 03:09:04 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-07 03:09:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 03:09:04 (9251) [INFO] Trying other mirror.
* 2025-01-07 03:09:04 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-07 03:09:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 03:09:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 03:09:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-07 03:09:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-07 03:09:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-07 03:09:04 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 03:09:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-07 03:09:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-07 03:09:04 (9251) [INFO]         or
* 2025-01-07 03:09:04 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 03:09:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 03:09:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 03:09:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 03:09:04 (9251) [INFO]         compromise:
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-07 03:09:04 (9251) [INFO] 
* 2025-01-07 03:09:04 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-07 03:09:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 03:09:04 (9268) [INFO] 
* 2025-01-07 03:09:04 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 03:09:04 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-07 03:09:04 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-07 03:09:04 (9238) [INFO] 
* 2025-01-07 03:09:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 03:09:05 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-07 03:09:05 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-07 03:09:05 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-07 03:09:05 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-07 03:09:05 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-07 03:09:05 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-07 03:09:05 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-07 03:09:05 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-07 03:09:05 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-07 03:09:05 (9268) [INFO] 
* 2025-01-07 03:09:05 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-07 03:09:05 (9238) [INFO] 
* 2025-01-07 03:09:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-07 03:09:05 (9251) [INFO] Determining fastest mirrors
* 2025-01-07 03:09:06 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-07 03:09:06 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-07 03:09:06 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-07 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 03:09:07 (9251) [INFO] Trying other mirror.
* 2025-01-07 03:09:07 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-07 03:09:07 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-07 03:09:07 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-07 03:09:07 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-07 03:09:07 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-07 03:09:07 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-07 03:09:07 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-07 03:09:07 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-07 03:09:07 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-07 03:09:07 (9251) [INFO]         or
* 2025-01-07 03:09:07 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-07 03:09:07 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-07 03:09:07 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-07 03:09:07 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-07 03:09:07 (9251) [INFO]         compromise:
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-07 03:09:07 (9251) [INFO] 
* 2025-01-07 03:09:07 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-07 03:09:07 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 03:09:07 (9268) [INFO] 
* 2025-01-07 03:09:07 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-07 03:09:07 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-07 03:09:07 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-07 03:09:08 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cKWmxTox62/ea_profile.json
* 2025-01-07 03:09:10 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/cKWmxTox62/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-07 03:09:10 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-08 03:09:00 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-08 03:09:00 (10313) [INFO] Script is up to date.
* 2025-01-08 03:09:02 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-08 03:09:02 (9238) [INFO] 
* 2025-01-08 03:09:08 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-08 03:09:08 (9238) [INFO] 
* 2025-01-08 03:09:13 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-08 03:09:13 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-08 03:09:13 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-08 03:09:13 (9238) [INFO] 
* 2025-01-08 03:09:13 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 03:09:13 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-08 03:09:14 (9251) [INFO]  * EA4: 185.90.57.221
* 2025-01-08 03:09:14 (9251) [INFO]  * cpanel-addons-production-feed: 185.90.57.221
* 2025-01-08 03:09:14 (9251) [INFO]  * cpanel-plugins: 185.90.57.221
* 2025-01-08 03:09:15 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 03:09:15 (9251) [INFO] Trying other mirror.
* 2025-01-08 03:09:15 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-08 03:09:15 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 03:09:15 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 03:09:15 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-08 03:09:15 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-08 03:09:15 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-08 03:09:15 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 03:09:15 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-08 03:09:15 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-08 03:09:15 (9251) [INFO]         or
* 2025-01-08 03:09:15 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 03:09:15 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 03:09:15 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 03:09:15 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 03:09:15 (9251) [INFO]         compromise:
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-08 03:09:15 (9251) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-08 03:09:15 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 03:09:15 (9268) [INFO] 
* 2025-01-08 03:09:15 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 03:09:15 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-08 03:09:15 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-08 03:09:15 (9238) [INFO] 
* 2025-01-08 03:09:15 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 03:09:15 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-08 03:09:15 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-08 03:09:15 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-08 03:09:15 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-08 03:09:15 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-08 03:09:15 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-08 03:09:15 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-08 03:09:15 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-08 03:09:15 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-08 03:09:16 (9268) [INFO] 
* 2025-01-08 03:09:16 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-08 03:09:16 (9238) [INFO] 
* 2025-01-08 03:09:16 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-08 03:09:16 (9251) [INFO] Determining fastest mirrors
* 2025-01-08 03:09:18 (9251) [INFO]  * EA4: 185.157.208.252
* 2025-01-08 03:09:18 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-01-08 03:09:18 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-01-08 03:09:19 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 03:09:19 (9251) [INFO] Trying other mirror.
* 2025-01-08 03:09:19 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-08 03:09:19 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-08 03:09:19 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-08 03:09:19 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-08 03:09:19 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-08 03:09:19 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-08 03:09:19 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-08 03:09:19 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-08 03:09:19 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-08 03:09:19 (9251) [INFO]         or
* 2025-01-08 03:09:19 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-08 03:09:19 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-08 03:09:19 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-08 03:09:19 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-08 03:09:19 (9251) [INFO]         compromise:
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-08 03:09:19 (9251) [INFO] 
* 2025-01-08 03:09:19 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-08 03:09:19 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 03:09:19 (9268) [INFO] 
* 2025-01-08 03:09:19 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-08 03:09:19 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-08 03:09:19 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-08 03:09:20 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PPIFCGgfWB/ea_profile.json
* 2025-01-08 03:09:22 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/PPIFCGgfWB/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-08 03:09:22 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-09 03:08:55 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-09 03:08:55 (10313) [INFO] Script is up to date.
* 2025-01-09 03:08:56 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-09 03:08:56 (9238) [INFO] 
* 2025-01-09 03:09:02 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-09 03:09:02 (9238) [INFO] 
* 2025-01-09 03:09:09 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-09 03:09:09 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-09 03:09:09 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-09 03:09:09 (9238) [INFO] 
* 2025-01-09 03:09:09 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 03:09:10 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-09 03:09:10 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-09 03:09:10 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-09 03:09:10 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-09 03:09:11 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 03:09:11 (9251) [INFO] Trying other mirror.
* 2025-01-09 03:09:11 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-09 03:09:11 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 03:09:11 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 03:09:11 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-09 03:09:11 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-09 03:09:11 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-09 03:09:11 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 03:09:11 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-09 03:09:11 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-09 03:09:11 (9251) [INFO]         or
* 2025-01-09 03:09:11 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 03:09:11 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 03:09:11 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 03:09:11 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 03:09:11 (9251) [INFO]         compromise:
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-09 03:09:11 (9251) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-09 03:09:11 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 03:09:11 (9268) [INFO] 
* 2025-01-09 03:09:11 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 03:09:11 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-09 03:09:11 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-09 03:09:11 (9238) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 03:09:11 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-09 03:09:11 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-09 03:09:11 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-09 03:09:11 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-09 03:09:11 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-09 03:09:11 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-09 03:09:11 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-09 03:09:11 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-09 03:09:11 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-09 03:09:11 (9268) [INFO] 
* 2025-01-09 03:09:11 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-09 03:09:11 (9238) [INFO] 
* 2025-01-09 03:09:11 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-09 03:09:12 (9251) [INFO] Determining fastest mirrors
* 2025-01-09 03:09:13 (9251) [INFO]  * EA4: 185.157.208.252
* 2025-01-09 03:09:13 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-01-09 03:09:13 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-01-09 03:09:13 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 03:09:13 (9251) [INFO] Trying other mirror.
* 2025-01-09 03:09:13 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-09 03:09:13 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-09 03:09:13 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-09 03:09:13 (9251) [INFO] 
* 2025-01-09 03:09:13 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-09 03:09:13 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-09 03:09:14 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-09 03:09:14 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-09 03:09:14 (9251) [INFO] 
* 2025-01-09 03:09:14 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-09 03:09:14 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-09 03:09:14 (9251) [INFO] 
* 2025-01-09 03:09:14 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-09 03:09:14 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-09 03:09:14 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-09 03:09:14 (9251) [INFO] 
* 2025-01-09 03:09:14 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-09 03:09:14 (9251) [INFO]         or
* 2025-01-09 03:09:14 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-09 03:09:14 (9251) [INFO] 
* 2025-01-09 03:09:14 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-09 03:09:14 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-09 03:09:14 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-09 03:09:14 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-09 03:09:14 (9251) [INFO]         compromise:
* 2025-01-09 03:09:14 (9251) [INFO] 
* 2025-01-09 03:09:14 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-09 03:09:14 (9251) [INFO] 
* 2025-01-09 03:09:14 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-09 03:09:14 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 03:09:14 (9268) [INFO] 
* 2025-01-09 03:09:14 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-09 03:09:14 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-09 03:09:14 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-09 03:09:16 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/njVfPtDd91/ea_profile.json
* 2025-01-09 03:09:18 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/njVfPtDd91/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-09 03:09:18 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-10 03:08:49 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-10 03:08:49 (10313) [INFO] Script is up to date.
* 2025-01-10 03:08:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-10 03:08:50 (9238) [INFO] 
* 2025-01-10 03:08:55 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-10 03:08:55 (9238) [INFO] 
* 2025-01-10 03:08:59 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-10 03:08:59 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-10 03:08:59 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-10 03:08:59 (9238) [INFO] 
* 2025-01-10 03:08:59 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 03:08:59 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-10 03:09:00 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-10 03:09:00 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-10 03:09:00 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-10 03:09:00 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 03:09:00 (9251) [INFO] Trying other mirror.
* 2025-01-10 03:09:00 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-10 03:09:00 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 03:09:00 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 03:09:00 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-10 03:09:00 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-10 03:09:00 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-10 03:09:00 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 03:09:00 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-10 03:09:00 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-10 03:09:00 (9251) [INFO]         or
* 2025-01-10 03:09:00 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 03:09:00 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 03:09:00 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 03:09:00 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 03:09:00 (9251) [INFO]         compromise:
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-10 03:09:00 (9251) [INFO] 
* 2025-01-10 03:09:00 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-10 03:09:00 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 03:09:00 (9268) [INFO] 
* 2025-01-10 03:09:00 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 03:09:00 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-10 03:09:00 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-10 03:09:00 (9238) [INFO] 
* 2025-01-10 03:09:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 03:09:01 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-10 03:09:01 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-10 03:09:01 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-10 03:09:01 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-10 03:09:01 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-10 03:09:01 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-10 03:09:01 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-10 03:09:01 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-10 03:09:01 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-10 03:09:01 (9268) [INFO] 
* 2025-01-10 03:09:01 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-10 03:09:01 (9238) [INFO] 
* 2025-01-10 03:09:01 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-10 03:09:01 (9251) [INFO] Determining fastest mirrors
* 2025-01-10 03:09:03 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-10 03:09:03 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-10 03:09:03 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-10 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 03:09:03 (9251) [INFO] Trying other mirror.
* 2025-01-10 03:09:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-10 03:09:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-10 03:09:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-10 03:09:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-10 03:09:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-10 03:09:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-10 03:09:03 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-10 03:09:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-10 03:09:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-10 03:09:03 (9251) [INFO]         or
* 2025-01-10 03:09:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-10 03:09:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-10 03:09:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-10 03:09:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-10 03:09:03 (9251) [INFO]         compromise:
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-10 03:09:03 (9251) [INFO] 
* 2025-01-10 03:09:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-10 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 03:09:03 (9268) [INFO] 
* 2025-01-10 03:09:03 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-10 03:09:03 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-10 03:09:03 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-10 03:09:04 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iwMvjuDq_Q/ea_profile.json
* 2025-01-10 03:09:06 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/iwMvjuDq_Q/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-10 03:09:06 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-11 03:09:43 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-11 03:09:43 (10313) [INFO] Script is up to date.
* 2025-01-11 03:09:45 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-11 03:09:45 (9238) [INFO] 
* 2025-01-11 03:09:46 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-11 03:09:46 (9238) [INFO] 
* 2025-01-11 03:09:51 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-11 03:09:51 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-11 03:09:51 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-11 03:09:51 (9238) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 03:09:52 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-11 03:09:52 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-11 03:09:52 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-11 03:09:52 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-11 03:09:52 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 03:09:52 (9251) [INFO] Trying other mirror.
* 2025-01-11 03:09:52 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-11 03:09:52 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 03:09:52 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 03:09:52 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-11 03:09:52 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-11 03:09:52 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-11 03:09:52 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 03:09:52 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-11 03:09:52 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-11 03:09:52 (9251) [INFO]         or
* 2025-01-11 03:09:52 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 03:09:52 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 03:09:52 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 03:09:52 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 03:09:52 (9251) [INFO]         compromise:
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-11 03:09:52 (9251) [INFO] 
* 2025-01-11 03:09:52 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-11 03:09:52 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 03:09:52 (9268) [INFO] 
* 2025-01-11 03:09:52 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 03:09:52 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-11 03:09:52 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-11 03:09:52 (9238) [INFO] 
* 2025-01-11 03:09:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 03:09:53 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-11 03:09:53 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-11 03:09:53 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-11 03:09:53 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-11 03:09:53 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-11 03:09:53 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-11 03:09:53 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-11 03:09:53 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-11 03:09:53 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-11 03:09:53 (9268) [INFO] 
* 2025-01-11 03:09:53 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-11 03:09:53 (9238) [INFO] 
* 2025-01-11 03:09:53 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-11 03:09:53 (9251) [INFO] Determining fastest mirrors
* 2025-01-11 03:09:56 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-11 03:09:56 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-11 03:09:56 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-11 03:09:56 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 03:09:56 (9251) [INFO] Trying other mirror.
* 2025-01-11 03:09:56 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-11 03:09:56 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-11 03:09:56 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-11 03:09:56 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-11 03:09:56 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-11 03:09:56 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-11 03:09:56 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-11 03:09:56 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-11 03:09:56 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-11 03:09:56 (9251) [INFO]         or
* 2025-01-11 03:09:56 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-11 03:09:56 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-11 03:09:56 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-11 03:09:56 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-11 03:09:56 (9251) [INFO]         compromise:
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-11 03:09:56 (9251) [INFO] 
* 2025-01-11 03:09:56 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-11 03:09:56 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 03:09:56 (9268) [INFO] 
* 2025-01-11 03:09:56 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-11 03:09:56 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-11 03:09:56 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-11 03:09:57 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/T5fnTflUie/ea_profile.json
* 2025-01-11 03:09:59 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/T5fnTflUie/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-11 03:09:59 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-12 03:09:49 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-12 03:09:49 (10313) [INFO] Script is up to date.
* 2025-01-12 03:09:50 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-12 03:09:50 (9238) [INFO] 
* 2025-01-12 03:09:55 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-12 03:09:55 (9238) [INFO] 
* 2025-01-12 03:10:00 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-12 03:10:00 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-12 03:10:00 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-12 03:10:00 (9238) [INFO] 
* 2025-01-12 03:10:00 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 03:10:00 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-12 03:10:01 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-12 03:10:01 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-12 03:10:01 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-12 03:10:02 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 03:10:02 (9251) [INFO] Trying other mirror.
* 2025-01-12 03:10:02 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-12 03:10:02 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 03:10:02 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 03:10:02 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-12 03:10:02 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-12 03:10:02 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-12 03:10:02 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 03:10:02 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-12 03:10:02 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-12 03:10:02 (9251) [INFO]         or
* 2025-01-12 03:10:02 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 03:10:02 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 03:10:02 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 03:10:02 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 03:10:02 (9251) [INFO]         compromise:
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-12 03:10:02 (9251) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-12 03:10:02 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 03:10:02 (9268) [INFO] 
* 2025-01-12 03:10:02 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 03:10:02 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-12 03:10:02 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-12 03:10:02 (9238) [INFO] 
* 2025-01-12 03:10:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 03:10:02 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-12 03:10:02 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-12 03:10:02 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-12 03:10:02 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-12 03:10:02 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-12 03:10:02 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-12 03:10:02 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-12 03:10:02 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-12 03:10:02 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-12 03:10:02 (9268) [INFO] 
* 2025-01-12 03:10:02 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-12 03:10:02 (9238) [INFO] 
* 2025-01-12 03:10:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-12 03:10:03 (9251) [INFO] Determining fastest mirrors
* 2025-01-12 03:10:04 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-12 03:10:04 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-12 03:10:04 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-12 03:10:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 03:10:04 (9251) [INFO] Trying other mirror.
* 2025-01-12 03:10:04 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-12 03:10:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-12 03:10:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-12 03:10:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-12 03:10:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-12 03:10:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-12 03:10:04 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-12 03:10:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-12 03:10:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-12 03:10:04 (9251) [INFO]         or
* 2025-01-12 03:10:04 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-12 03:10:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-12 03:10:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-12 03:10:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-12 03:10:04 (9251) [INFO]         compromise:
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-12 03:10:04 (9251) [INFO] 
* 2025-01-12 03:10:04 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-12 03:10:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 03:10:04 (9268) [INFO] 
* 2025-01-12 03:10:04 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-12 03:10:04 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-12 03:10:05 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-12 03:10:06 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xam07ZDq7G/ea_profile.json
* 2025-01-12 03:10:08 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/xam07ZDq7G/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-12 03:10:08 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-13 03:08:51 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-13 03:08:51 (10313) [INFO] Script is up to date.
* 2025-01-13 03:08:52 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-13 03:08:52 (9238) [INFO] 
* 2025-01-13 03:08:56 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-13 03:08:56 (9238) [INFO] 
* 2025-01-13 03:09:03 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-13 03:09:03 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-13 03:09:03 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-13 03:09:03 (9238) [INFO] 
* 2025-01-13 03:09:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 03:09:03 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-13 03:09:03 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-13 03:09:03 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-13 03:09:03 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-13 03:09:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 03:09:04 (9251) [INFO] Trying other mirror.
* 2025-01-13 03:09:04 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-13 03:09:04 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 03:09:04 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 03:09:04 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-13 03:09:04 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-13 03:09:04 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-13 03:09:04 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 03:09:04 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-13 03:09:04 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-13 03:09:04 (9251) [INFO]         or
* 2025-01-13 03:09:04 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 03:09:04 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 03:09:04 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 03:09:04 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 03:09:04 (9251) [INFO]         compromise:
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-13 03:09:04 (9251) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-13 03:09:04 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 03:09:04 (9268) [INFO] 
* 2025-01-13 03:09:04 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 03:09:04 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-13 03:09:04 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-13 03:09:04 (9238) [INFO] 
* 2025-01-13 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 03:09:04 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-13 03:09:04 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-13 03:09:04 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-13 03:09:04 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-13 03:09:04 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-13 03:09:04 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-13 03:09:04 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-13 03:09:04 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-13 03:09:04 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-13 03:09:04 (9268) [INFO] 
* 2025-01-13 03:09:04 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-13 03:09:04 (9238) [INFO] 
* 2025-01-13 03:09:05 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-13 03:09:05 (9251) [INFO] Determining fastest mirrors
* 2025-01-13 03:09:06 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-13 03:09:06 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-13 03:09:06 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-13 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 03:09:06 (9251) [INFO] Trying other mirror.
* 2025-01-13 03:09:06 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-13 03:09:06 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-13 03:09:06 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-13 03:09:06 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-13 03:09:06 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-13 03:09:06 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-13 03:09:06 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-13 03:09:06 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-13 03:09:06 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-13 03:09:06 (9251) [INFO]         or
* 2025-01-13 03:09:06 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-13 03:09:06 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-13 03:09:06 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-13 03:09:06 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-13 03:09:06 (9251) [INFO]         compromise:
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-13 03:09:06 (9251) [INFO] 
* 2025-01-13 03:09:06 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-13 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 03:09:06 (9268) [INFO] 
* 2025-01-13 03:09:06 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-13 03:09:06 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-13 03:09:07 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-13 03:09:08 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qd2JqcqVRZ/ea_profile.json
* 2025-01-13 03:09:09 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/Qd2JqcqVRZ/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-13 03:09:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-14 03:08:51 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-14 03:08:51 (10313) [INFO] Script is up to date.
* 2025-01-14 03:08:52 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-14 03:08:52 (9238) [INFO] 
* 2025-01-14 03:08:57 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-14 03:08:57 (9238) [INFO] 
* 2025-01-14 03:09:02 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-14 03:09:02 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-14 03:09:02 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-14 03:09:02 (9238) [INFO] 
* 2025-01-14 03:09:02 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 03:09:02 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-14 03:09:03 (9251) [INFO]  * EA4: 185.157.208.252
* 2025-01-14 03:09:03 (9251) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-01-14 03:09:03 (9251) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-01-14 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 03:09:03 (9251) [INFO] Trying other mirror.
* 2025-01-14 03:09:03 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-14 03:09:03 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 03:09:03 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 03:09:03 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-14 03:09:03 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-14 03:09:03 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-14 03:09:03 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 03:09:03 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-14 03:09:03 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-14 03:09:03 (9251) [INFO]         or
* 2025-01-14 03:09:03 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 03:09:03 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 03:09:03 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 03:09:03 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 03:09:03 (9251) [INFO]         compromise:
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-14 03:09:03 (9251) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-14 03:09:03 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 03:09:03 (9268) [INFO] 
* 2025-01-14 03:09:03 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 03:09:03 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-14 03:09:03 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-14 03:09:03 (9238) [INFO] 
* 2025-01-14 03:09:03 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 03:09:04 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-14 03:09:04 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-14 03:09:04 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-14 03:09:04 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-14 03:09:04 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-14 03:09:04 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-14 03:09:04 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-14 03:09:04 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-14 03:09:04 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-14 03:09:04 (9268) [INFO] 
* 2025-01-14 03:09:04 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-14 03:09:04 (9238) [INFO] 
* 2025-01-14 03:09:04 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-14 03:09:04 (9251) [INFO] Determining fastest mirrors
* 2025-01-14 03:09:05 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-14 03:09:05 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-14 03:09:05 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-14 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 03:09:06 (9251) [INFO] Trying other mirror.
* 2025-01-14 03:09:06 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-14 03:09:06 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-14 03:09:06 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-14 03:09:06 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-14 03:09:06 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-14 03:09:06 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-14 03:09:06 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-14 03:09:06 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-14 03:09:06 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-14 03:09:06 (9251) [INFO]         or
* 2025-01-14 03:09:06 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-14 03:09:06 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-14 03:09:06 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-14 03:09:06 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-14 03:09:06 (9251) [INFO]         compromise:
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-14 03:09:06 (9251) [INFO] 
* 2025-01-14 03:09:06 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-14 03:09:06 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 03:09:06 (9268) [INFO] 
* 2025-01-14 03:09:06 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-14 03:09:06 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-14 03:09:06 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-14 03:09:07 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SriqGmnrtb/ea_profile.json
* 2025-01-14 03:09:09 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/SriqGmnrtb/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-14 03:09:09 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-01-15 03:09:10 (10291) [INFO] Self-update of script version 59 requested.
* 2025-01-15 03:09:11 (10313) [INFO] Script is up to date.
* 2025-01-15 03:09:13 (9237) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-01-15 03:09:13 (9238) [INFO] 
* 2025-01-15 03:09:18 (9237) [INFO] Running: /usr/bin/yum list extras
* 2025-01-15 03:09:18 (9238) [INFO] 
* 2025-01-15 03:09:24 (5910) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-01-15 03:09:24 (252) [WARN] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-01-15 03:09:24 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-15 03:09:24 (9238) [INFO] 
* 2025-01-15 03:09:25 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 03:09:25 (9251) [INFO] Loading mirror speeds from cached hostfile
* 2025-01-15 03:09:25 (9251) [INFO]  * EA4: 185.15.22.168
* 2025-01-15 03:09:25 (9251) [INFO]  * cpanel-addons-production-feed: 185.15.22.168
* 2025-01-15 03:09:25 (9251) [INFO]  * cpanel-plugins: 185.15.22.168
* 2025-01-15 03:09:26 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 03:09:26 (9251) [INFO] Trying other mirror.
* 2025-01-15 03:09:26 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-15 03:09:26 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 03:09:26 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 03:09:26 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-15 03:09:26 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-15 03:09:26 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-15 03:09:26 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 03:09:26 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-15 03:09:26 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-15 03:09:26 (9251) [INFO]         or
* 2025-01-15 03:09:26 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 03:09:26 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 03:09:26 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 03:09:26 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 03:09:26 (9251) [INFO]         compromise:
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-15 03:09:26 (9251) [INFO] 
* 2025-01-15 03:09:26 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-15 03:09:26 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 03:09:26 (9268) [INFO] 
* 2025-01-15 03:09:26 (5793) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 03:09:26 (5794) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-01-15 03:09:26 (9237) [INFO] Running: /usr/bin/yum clean all
* 2025-01-15 03:09:26 (9238) [INFO] 
* 2025-01-15 03:09:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 03:09:27 (9251) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-01-15 03:09:27 (9251) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-01-15 03:09:27 (9251) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-01-15 03:09:27 (9251) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-01-15 03:09:27 (9251) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-01-15 03:09:27 (9251) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-01-15 03:09:27 (9251) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-01-15 03:09:27 (9251) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-01-15 03:09:27 (9251) [INFO] Cleaning up list of fastest mirrors
* 2025-01-15 03:09:27 (9268) [INFO] 
* 2025-01-15 03:09:27 (9237) [INFO] Running: /usr/bin/yum makecache
* 2025-01-15 03:09:27 (9238) [INFO] 
* 2025-01-15 03:09:27 (9251) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-01-15 03:09:28 (9251) [INFO] Determining fastest mirrors
* 2025-01-15 03:09:28 (9251) [INFO]  * EA4: 31.22.112.31
* 2025-01-15 03:09:28 (9251) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-01-15 03:09:28 (9251) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-01-15 03:09:29 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 03:09:29 (9251) [INFO] Trying other mirror.
* 2025-01-15 03:09:29 (9251) [INFO] To address this issue please refer to the below wiki article 
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO] https://wiki.centos.org/yum-errors
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-01-15 03:09:29 (9251) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-01-15 03:09:29 (9251) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-01-15 03:09:29 (9251) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-01-15 03:09:29 (9251) [INFO]         distribution release than is supported by the repository (and the
* 2025-01-15 03:09:29 (9251) [INFO]         packages for the previous distribution release still work).
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-01-15 03:09:29 (9251) [INFO]             yum --disablerepo=base ...
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-01-15 03:09:29 (9251) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-01-15 03:09:29 (9251) [INFO]         again or use --enablerepo for temporary usage:
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]             yum-config-manager --disable base
* 2025-01-15 03:09:29 (9251) [INFO]         or
* 2025-01-15 03:09:29 (9251) [INFO]             subscription-manager repos --disable=base
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-01-15 03:09:29 (9251) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-01-15 03:09:29 (9251) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-01-15 03:09:29 (9251) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-01-15 03:09:29 (9251) [INFO]         compromise:
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-01-15 03:09:29 (9251) [INFO] 
* 2025-01-15 03:09:29 (9251) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-01-15 03:09:29 (9251) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 03:09:29 (9268) [INFO] 
* 2025-01-15 03:09:29 (5803) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-01-15 03:09:29 (5804) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-01-15 03:09:29 (1992) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-01-15 03:09:31 (8362) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kByhDI3oZR/ea_profile.json
* 2025-01-15 03:09:32 (484) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/kByhDI3oZR/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 8364.
* 2025-01-15 03:09:32 (448) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-12 03:08:31 (10291) [INFO] Self-update of script version 59 requested.
* 2025-06-12 03:08:31 (10296) [INFO] Newer version of script found. Downloading.
* 2025-06-12 03:08:31 (10305) [INFO] Script update to version 66 successful.
* 2025-06-12 03:08:32 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2025-06-12 03:08:32 (10169) [INFO] 
* 2025-06-12 03:09:05 (10199) [INFO] 
* 2025-06-12 03:09:05 (259) [ERROR] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.50) does not appear to be up to date.
Additionally, we were unable to determine the expected version for this build.

* 2025-06-12 03:09:05 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-06-12 03:09:05 (10169) [INFO] 
* 2025-06-12 03:09:07 (10168) [INFO] Running: /usr/bin/yum list extras
* 2025-06-12 03:09:07 (10169) [INFO] 
* 2025-06-12 03:09:10 (6504) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-06-12 03:09:10 (259) [ERROR] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

updates
base

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-06-12 03:09:10 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-12 03:09:10 (10169) [INFO] 
* 2025-06-12 03:09:11 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-12 03:09:11 (10182) [INFO] Loading mirror speeds from cached hostfile
* 2025-06-12 03:09:11 (10182) [INFO]  * EA4: 31.22.112.31
* 2025-06-12 03:09:11 (10182) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-06-12 03:09:11 (10182) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-06-12 03:09:12 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 03:09:12 (10182) [INFO] Trying other mirror.
* 2025-06-12 03:09:12 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-06-12 03:09:12 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-12 03:09:12 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-12 03:09:12 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-12 03:09:12 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-12 03:09:12 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-12 03:09:12 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-12 03:09:12 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-12 03:09:12 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-12 03:09:12 (10182) [INFO]         or
* 2025-06-12 03:09:12 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-12 03:09:12 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-12 03:09:12 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-12 03:09:12 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-12 03:09:12 (10182) [INFO]         compromise:
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-12 03:09:12 (10182) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-12 03:09:12 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 03:09:12 (10199) [INFO] 
* 2025-06-12 03:09:12 (6386) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 03:09:12 (6387) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-06-12 03:09:12 (10168) [INFO] Running: /usr/bin/yum clean all
* 2025-06-12 03:09:12 (10169) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-12 03:09:12 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-06-12 03:09:12 (10182) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-06-12 03:09:12 (10182) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-06-12 03:09:12 (10182) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-06-12 03:09:12 (10182) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-06-12 03:09:12 (10182) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-06-12 03:09:12 (10182) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-06-12 03:09:12 (10182) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-06-12 03:09:12 (10182) [INFO] Cleaning up list of fastest mirrors
* 2025-06-12 03:09:12 (10199) [INFO] 
* 2025-06-12 03:09:12 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-12 03:09:12 (10169) [INFO] 
* 2025-06-12 03:09:12 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-12 03:09:12 (10182) [INFO] Determining fastest mirrors
* 2025-06-12 03:09:15 (10182) [INFO]  * EA4: 31.22.112.31
* 2025-06-12 03:09:15 (10182) [INFO]  * cpanel-addons-production-feed: 31.22.112.31
* 2025-06-12 03:09:15 (10182) [INFO]  * cpanel-plugins: 31.22.112.31
* 2025-06-12 03:09:15 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 03:09:15 (10182) [INFO] Trying other mirror.
* 2025-06-12 03:09:15 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-12 03:09:15 (10182) [INFO] 
* 2025-06-12 03:09:15 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-12 03:09:15 (10182) [INFO] 
* 2025-06-12 03:09:15 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-12 03:09:15 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-06-12 03:09:16 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-12 03:09:16 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-12 03:09:16 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-12 03:09:16 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-12 03:09:16 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-12 03:09:16 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-12 03:09:16 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-12 03:09:16 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-12 03:09:16 (10182) [INFO]         or
* 2025-06-12 03:09:16 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-12 03:09:16 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-12 03:09:16 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-12 03:09:16 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-12 03:09:16 (10182) [INFO]         compromise:
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-12 03:09:16 (10182) [INFO] 
* 2025-06-12 03:09:16 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-12 03:09:16 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 03:09:16 (10199) [INFO] 
* 2025-06-12 03:09:16 (6396) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-06-12 03:09:16 (6397) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-12 03:09:16 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-06-12 03:09:17 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9xbND3MOg7/ea_profile.json
* 2025-06-12 03:09:18 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/9xbND3MOg7/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290.
* 2025-06-12 03:09:18 (476) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/
* 2025-06-13 03:08:43 (11230) [INFO] Self-update of script version 66 requested.
* 2025-06-13 03:08:43 (11252) [INFO] Script is up to date.
* 2025-06-13 03:08:44 (10168) [INFO] Running: /usr/local/cpanel/scripts/check_cpanel_pkgs --list-only
* 2025-06-13 03:08:44 (10169) [INFO] 
* 2025-06-13 03:09:20 (10199) [INFO] 
* 2025-06-13 03:09:20 (259) [ERROR] *** Elevation Blocker detected: ***
This installation of cPanel (11.110.0.50) does not appear to be up to date.
Please upgrade cPanel to 11.110.0.68.

* 2025-06-13 03:09:20 (10168) [INFO] Running: /usr/bin/imunify360-agent version --json
* 2025-06-13 03:09:20 (10169) [INFO] 
* 2025-06-13 03:09:22 (10168) [INFO] Running: /usr/bin/yum list extras
* 2025-06-13 03:09:22 (10169) [INFO] 
* 2025-06-13 03:09:26 (6504) [ERROR] 6 package(s) installed from unsupported YUM repo 'docker-ce-stable' from /etc/yum.repos.d/docker-ce.repo
* 2025-06-13 03:09:26 (259) [ERROR] *** Elevation Blocker detected: ***
One or more enable YUM repo have repositories defined multiple times:

base
updates

A possible resolution for this issue is to either remove the duplicate
repository definitions or change the repoids of the conflicting
repositories on the system to prevent the conflict.

* 2025-06-13 03:09:26 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-13 03:09:26 (10169) [INFO] 
* 2025-06-13 03:09:26 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-13 03:09:26 (10182) [INFO] Loading mirror speeds from cached hostfile
* 2025-06-13 03:09:27 (10182) [INFO]  * EA4: 185.157.208.252
* 2025-06-13 03:09:27 (10182) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-06-13 03:09:27 (10182) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-06-13 03:09:28 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 03:09:28 (10182) [INFO] Trying other mirror.
* 2025-06-13 03:09:28 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-06-13 03:09:28 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-13 03:09:28 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-13 03:09:28 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-13 03:09:28 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-13 03:09:28 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-13 03:09:28 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-13 03:09:28 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-13 03:09:28 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-13 03:09:28 (10182) [INFO]         or
* 2025-06-13 03:09:28 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-13 03:09:28 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-13 03:09:28 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-13 03:09:28 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-13 03:09:28 (10182) [INFO]         compromise:
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-13 03:09:28 (10182) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-13 03:09:28 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 03:09:28 (10199) [INFO] 
* 2025-06-13 03:09:28 (6386) [WARN] Initial run of "yum makecache" failed: http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 03:09:28 (6387) [WARN] Running "yum clean all" in an attempt to fix yum
* 2025-06-13 03:09:28 (10168) [INFO] Running: /usr/bin/yum clean all
* 2025-06-13 03:09:28 (10169) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-13 03:09:28 (10182) [INFO] Cleaning repos: EA4 cpanel-addons-production-feed cpanel-plugins MariaDB106 base
* 2025-06-13 03:09:28 (10182) [INFO]               : centos7-els centos7els-rollout-1 centos7els-rollout-2
* 2025-06-13 03:09:28 (10182) [INFO]               : centos7els-rollout-3 centos7els-rollout-4 centos7els-rollout-5
* 2025-06-13 03:09:28 (10182) [INFO]               : centos7els-rollout-6 docker-ce-stable extras imunify360
* 2025-06-13 03:09:28 (10182) [INFO]               : imunify360-rollout-1 imunify360-rollout-2 imunify360-rollout-3
* 2025-06-13 03:09:28 (10182) [INFO]               : imunify360-rollout-4 imunify360-rollout-5 imunify360-rollout-6
* 2025-06-13 03:09:28 (10182) [INFO]               : imunify360-rollout-7 imunify360-rollout-8 updates
* 2025-06-13 03:09:28 (10182) [INFO]               : wp-toolkit-cpanel wp-toolkit-thirdparties
* 2025-06-13 03:09:28 (10182) [INFO] Cleaning up list of fastest mirrors
* 2025-06-13 03:09:28 (10199) [INFO] 
* 2025-06-13 03:09:28 (10168) [INFO] Running: /usr/bin/yum makecache
* 2025-06-13 03:09:28 (10169) [INFO] 
* 2025-06-13 03:09:28 (10182) [INFO] Loaded plugins: fastestmirror, universal-hooks
* 2025-06-13 03:09:28 (10182) [INFO] Determining fastest mirrors
* 2025-06-13 03:09:31 (10182) [INFO]  * EA4: 185.157.208.252
* 2025-06-13 03:09:31 (10182) [INFO]  * cpanel-addons-production-feed: 185.157.208.252
* 2025-06-13 03:09:31 (10182) [INFO]  * cpanel-plugins: 185.157.208.252
* 2025-06-13 03:09:32 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 03:09:32 (10182) [INFO] Trying other mirror.
* 2025-06-13 03:09:32 (10182) [INFO] To address this issue please refer to the below wiki article 
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO] https://wiki.centos.org/yum-errors
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO] If above article doesn't help to resolve this issue please use https://bugs.centos.org/.
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]  One of the configured repositories failed (CentOS-7-Base),
* 2025-06-13 03:09:32 (10182) [INFO]  and yum doesn't have enough cached data to continue. At this point the only
* 2025-06-13 03:09:32 (10182) [INFO]  safe thing yum can do is fail. There are a few ways to work "fix" this:
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]      1. Contact the upstream for the repository and get them to fix the problem.
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]      2. Reconfigure the baseurl/etc. for the repository, to point to a working
* 2025-06-13 03:09:32 (10182) [INFO]         upstream. This is most often useful if you are using a newer
* 2025-06-13 03:09:32 (10182) [INFO]         distribution release than is supported by the repository (and the
* 2025-06-13 03:09:32 (10182) [INFO]         packages for the previous distribution release still work).
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]      3. Run the command with the repository temporarily disabled
* 2025-06-13 03:09:32 (10182) [INFO]             yum --disablerepo=base ...
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]      4. Disable the repository permanently, so yum won't use it by default. Yum
* 2025-06-13 03:09:32 (10182) [INFO]         will then just ignore the repository until you permanently enable it
* 2025-06-13 03:09:32 (10182) [INFO]         again or use --enablerepo for temporary usage:
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]             yum-config-manager --disable base
* 2025-06-13 03:09:32 (10182) [INFO]         or
* 2025-06-13 03:09:32 (10182) [INFO]             subscription-manager repos --disable=base
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]      5. Configure the failing repository to be skipped, if it is unavailable.
* 2025-06-13 03:09:32 (10182) [INFO]         Note that yum will try to contact the repo. when it runs most commands,
* 2025-06-13 03:09:32 (10182) [INFO]         so will have to try and fail each time (and thus. yum will be be much
* 2025-06-13 03:09:32 (10182) [INFO]         slower). If it is a very temporary problem though, this is often a nice
* 2025-06-13 03:09:32 (10182) [INFO]         compromise:
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO]             yum-config-manager --save --setopt=base.skip_if_unavailable=true
* 2025-06-13 03:09:32 (10182) [INFO] 
* 2025-06-13 03:09:32 (10182) [INFO] failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
* 2025-06-13 03:09:32 (10182) [INFO] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 03:09:32 (10199) [INFO] 
* 2025-06-13 03:09:32 (6396) [ERROR] '/usr/bin/yum makecache' failed to return cleanly. This could be due to a temporary mirror problem, or it could indicate a larger issue, such as a broken repository. Since this script relies heavily on yum, you will need to address this issue before upgrading.

If you need assistance, open a ticket with cPanel Support, as outlined here:

https://docs.cpanel.net/knowledge-base/technical-support-services/how-to-open-a-technical-support-ticket/
* 2025-06-13 03:09:32 (6397) [ERROR] http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article 

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



 One of the configured repositories failed (CentOS-7-Base),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Run the command with the repository temporarily disabled
            yum --disablerepo=base ...

     4. Disable the repository permanently, so yum won't use it by default. Yum
        will then just ignore the repository until you permanently enable it
        again or use --enablerepo for temporary usage:

            yum-config-manager --disable base
        or
            subscription-manager repos --disable=base

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://asi-fs-d.contabo.net/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
* 2025-06-13 03:09:32 (2295) [INFO] Checking EasyApache profile compatibility with AlmaLinux 8.
* 2025-06-13 03:09:33 (9288) [INFO] Running: /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jHVTRRiC1f/ea_profile.json
* 2025-06-13 03:09:34 (535) [WARN] Unknown error while checking blockers: Unable to backup EA4 profile. Failure from /usr/local/bin/ea_current_to_profile --target-os=CentOS_8 --output=/tmp/jHVTRRiC1f/ea_profile.json at /usr/local/cpanel/scripts/elevate-cpanel line 9290.
* 2025-06-13 03:09:34 (476) [WARN] Please fix the detected issues before performing the elevation process.
Read More: https://cpanel.github.io/elevate/blockers/