cPanel & WHM update failure in upcp script
I've been coping with the following messages (sent via an e-mail with subject "cPanel & WHM update failure in upcp script") for a year and wondered if there is a better solution than running yum update manually and restarting the server.
Here's the error message detail:
2025-07-03 01:34:18 -0400] [/usr/local/cpanel/scripts/update-packages] Error:
[2025-07-03 01:34:18 -0400] [/usr/local/cpanel/scripts/update-packages] Problem: package kernel-devel-matched-5.14.0-570.24.1.el9_6.x86_64 from appstream requires kernel-core = 5.14.0-570.24.1.el9_6, but none of the providers can be installed
[2025-07-03 01:34:18 -0400] [/usr/local/cpanel/scripts/update-packages] - cannot install the best update candidate for package kernel-devel-matched-5.14.0-570.23.1.el9_6.x86_64
[2025-07-03 01:34:18 -0400] [/usr/local/cpanel/scripts/update-packages] - package kernel-core-5.14.0-570.24.1.el9_6.x86_64 from baseos is filtered out by exclude filtering
[2025-07-03 01:34:18 -0400] [/usr/local/cpanel/scripts/update-packages] (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[2025-07-03 01:34:18 -0400] [/usr/local/cpanel/scripts/update-packages] (XID 6vdvzx) “/usr/bin/yum” reported error code “1” when it ended:
[2025-07-03 01:34:18 -0400] E [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages” command (process 822159) reported error number 1 when it ended.
I root into the server the following morning and run yum update. It either works just fine after that - no more errors - or requires a restart. Is /usr/local/cpanel/scripts/upcp unable to run a regular yum update due to some sort of exclusion?
[root@core ~]# pico /etc/yum.conf
[main]
exclude=bind-chroot dovecot* exim* filesystem p0f php* proftpd* pure-ftpd*
tolerant=1
plugins=1
gpgcheck=1
installonly_limit=3
clean_requirements_on_remove=True
best=True
skip_if_unavailable=False
minrate=50k
Running yum update manually sometimes produces this e-mail message "New Security Advisor notifications with High importance":
The system kernel is at version “5.14.0-570.22.1.el9_6.x86_64”, but the system is configured to boot version “5.14.0-570.24.1.el9_6.x86_64”. Reboot the system. If the problem persists, check the GRUB boot configuration.
Checking that:
[root@core ~]# /usr/bin/kcarectl --info
kpatch-state: patch is applied
kpatch-for: Linux version 5.14.0-570.22.1.el9_6.x86_64 (mockbuild@x64-builder02.almalinux.org) (gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-5), GNU ld version 2.35.2-63.el9) #1 SMP PREEMPT_DYNAMIC Thu Jun 19 08:10:32 EDT 2025
kpatch-build-time: Fri Jun 20 13:53:40 2025
kpatch-description: 1-free:1751028356;5.14.0-570.23.1.el9_6
And verifying:
[root@core ~]# /usr/bin/kcarectl --update
Updates already downloaded
No updates are needed for this kernel
Kernel is safe
So I get frustrated and reboot the server late at night, which solves everything until the next update rolls around.
Any insights? Thank you.
-
Hey there! That output all looks normal to me, except the temporary failure from Yum. If "yum update" works normally the next day, it was likely just a failed update that resolved itself.
As far as the Kcare issue, if the kernel was just recently released it was likely not in the Kcare system just yet, so it didn't detect any udpates. It does take a few days, or sometimes longer, for Kcare to process the most recent udpates.
0 -
cPRex I'll try not running yum update or /usr/local/cpanel/scripts/upcp from the command line after I see an error as a test, but previously manually running either of these commands and doing a full graceful restart of the server was the only resolution.
0 -
cPRex Not taking action when the error pops up does not resolve. Running upcp manually produces:
[2025-07-15 13:28:16 -0400] [/usr/local/cpanel/scripts/update-packages] Error:
[2025-07-15 13:28:16 -0400] [/usr/local/cpanel/scripts/update-packages] Problem: package kernel-devel-matched-5.14.0-570.25.1.el9_6.x86_64 from appstream requires kernel-core = 5.14.0-570.25.1.el9_6, but none of the providers can be installed
[2025-07-15 13:28:16 -0400] [/usr/local/cpanel/scripts/update-packages] - cannot install the best update candidate for package kernel-devel-matched-5.14.0-570.24.1.el9_6.x86_64
[2025-07-15 13:28:16 -0400] [/usr/local/cpanel/scripts/update-packages] - package kernel-core-5.14.0-570.25.1.el9_6.x86_64 from baseos is filtered out by exclude filtering
[2025-07-15 13:28:16 -0400] [/usr/local/cpanel/scripts/update-packages] (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[2025-07-15 13:28:16 -0400] [/usr/local/cpanel/scripts/update-packages] (XID z3xxya) “/usr/bin/yum” reported error code “1” when it ended:
[2025-07-15 13:28:16 -0400] E [/usr/local/cpanel/scripts/update-packages] The “/usr/local/cpanel/scripts/update-packages” command (process 2715294) reported error number 1 when it ended.[2025-07-15 13:28:59 -0400] E Pre Maintenance ended, however it did not exit cleanly (256). The following events were logged: "scripts/update-packages". Please check the logs for an indication of what happened
Then I run yum update, which asks if ok to do the following in this case:
==================================================================================================================================================================
Package Architecture Version Repository Size
==================================================================================================================================================================
Installing:
kernel x86_64 5.14.0-570.25.1.el9_6 baseos 1.8 M
kernel-core x86_64 5.14.0-570.25.1.el9_6 baseos 18 M
kernel-devel x86_64 5.14.0-570.25.1.el9_6 appstream 18 M
kernel-modules x86_64 5.14.0-570.25.1.el9_6 baseos 39 M
kernel-modules-core x86_64 5.14.0-570.25.1.el9_6 baseos 31 M
Upgrading:
dkms noarch 3.2.1-1.el9 epel 87 k
dpkg x86_64 1.22.20-1.el9 epel 1.5 M
jq x86_64 1.6-17.el9_6.2 baseos 186 k
kernel-devel-matched x86_64 5.14.0-570.25.1.el9_6 appstream 1.8 M
kernel-headers x86_64 5.14.0-570.25.1.el9_6 appstream 3.3 M
kernel-tools x86_64 5.14.0-570.25.1.el9_6 baseos 2.0 M
kernel-tools-libs x86_64 5.14.0-570.25.1.el9_6 baseos 1.8 M
libldb x86_64 4.21.3-7.el9_6 baseos 176 k
libsmbclient x86_64 4.21.3-7.el9_6 baseos 73 k
libwbclient x86_64 4.21.3-7.el9_6 baseos 42 k
libxml2 x86_64 2.9.13-10.el9_6 baseos 746 k
libxml2-devel x86_64 2.9.13-10.el9_6 appstream 827 k
python3-perf x86_64 5.14.0-570.25.1.el9_6 appstream 3.2 M
samba-client-libs x86_64 4.21.3-7.el9_6 baseos 5.2 M
samba-common noarch 4.21.3-7.el9_6 baseos 173 k
samba-common-libs x86_64 4.21.3-7.el9_6 baseos 100 k
Removing:
kernel x86_64 5.14.0-570.23.1.el9_6 @baseos 0
kernel-core x86_64 5.14.0-570.23.1.el9_6 @baseos 68 M
kernel-devel x86_64 5.14.0-570.23.1.el9_6 @appstream 70 M
kernel-modules x86_64 5.14.0-570.23.1.el9_6 @baseos 36 M
kernel-modules-core x86_64 5.14.0-570.23.1.el9_6 @baseos 28 M
Transaction SummaryThis basically runs cleanly. Running upcp again produces no errors.
0 -
Thanks for the additional details - what happens if you run this command on the machine:
uname -r
That should print the kernel version and let you know what the loaded kernel is on the machine.
0 -
Hi cPRex, here's the output:
[root@core ~]# uname -r
5.14.0-570.22.1.el9_6.x86_64Additionally received the message last night, which often comes with this whole process and 100% necessitates a reboot in order to clear (noting again that kernelcare is active on this server and my understanding was that these reboots should not be necessary):
The system kernel is at version “5.14.0-570.22.1.el9_6.x86_64”, but the system is configured to boot version “5.14.0-570.25.1.el9_6.x86_64”. Reboot the system. If the problem persists, check the GRUB boot configuration.
I also know to check the following, which insists that a reboot is necessary:
[root@core ~]# /usr/bin/needs-restarting --reboothint
Core libraries or services have been updated since boot-up:
* glibc
* kernel
* linux-firmware
* microcode_ctl
* systemd
Reboot is required to fully utilize these updates.
More information: https://access.redhat.com/solutions/279430 -
Thanks for that - there does seem to be confusion with KernelCare and at this point I'd recommend creating a ticket so that can be investigated directly on the machine.
1 -
cPRex I apparently cannot create a support ticket as, like most people, cPanel is resold to me through one of your partners. They will not provide any support or ability to create a ticket. Is there another way to create a ticket?
0 -
Your provider should be the one providing support the product, and then they would escalate the ticket to the appropriate party (us or KernelCare) if they can't resolve it.
0 -
For other people looking at this, support advised the following:
https://support.cpanel.net/hc/en-us/articles/27234232488855-RPM-update-failure-kernel-devel-matched-requires-kernel-core0
Please sign in to leave a comment.
Comments
9 comments