Can't update system packages

[InTheWoods]

"There are 191 updatable packages on the system."

Click on, "Update all packages" and get met with, "Internal Error"

SSH into the box, run, "yum update" and am met with this:

yum update
This system is receiving updates from CloudLinux Network server.
Last metadata expiration check: 1:11:11 ago on Tue 10 Jun 2025 01:08:34 PM EDT.
Error:
 Problem: package kmod-lve-1:2.0-35.el8.x86_64 from @System requires kernel(bpf_trace_run12) = 0xa1d22df3, but none of the providers can be installed
  - package kmod-lve-1:2.0-35.el8.x86_64 from @System requires kernel(bpf_trace_run2) = 0x7b67d1d5, but none of the providers can be installed
  - package kmod-lve-1:2.0-35.el8.x86_64 from @System requires kernel(bpf_trace_run3) = 0xbe20211d, but none of the providers can be installed
  - package kmod-lve-1:2.0-35.el8.x86_64 from @System requires kernel(bpf_trace_run6) = 0xa952e67e, but none of the providers can be installed
  - package kmod-lve-1:2.0-35.el8.x86_64 from @System requires kernel(kmalloc_caches) = 0x8200293d, but none of the providers can be installed
  - conflicting requests
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Don't want to use --skip-broken flag in case it results in a discrepancy that causes a conflict with other packages. Any advice on how best to proceed? Not much time to fuss with this at the moment so will check back when I have more time.

 

[Richard G]

SSH into the box, run, "yum update" and am met with this:

Yum update is the OS, not Directadmin.
I think you might better post this issue at Cloudlinux support as they also provide the yum packages for Cloudlinux.

 

[zEitEr]

Hello,

Are you sure the kernel from CloudLinux repository is installed? Are you still with an active subscription from CloudLinux?

What will you see if you run:

yum list installed | grep ^kernel -i | sort

?

Every command yum update will require a confirmation if you did not specified -y flag. Thus if you run:

yum update --skip-broken

it should stop waiting for a confirmation from you, if everything is ready for an update. If an error is reported it does not break anything too.

And you might try and clean cache as well:

yum clean all
rm -rf /var/cache/yum
yum makecache
yum update

and see whether the error occurs again.

Don't want to use --skip-broken flag in case it results in a discrepancy that causes a conflict with other packages. Any advice on how best to proceed? Not much time to fuss with this at the moment so will check back when I have more time.