getting error while running system update
System update process has started.
"/usr/bin/dnf" reported error code "1" when it ended: w/ /usr/bin/dnf upgrade -y --exclude=kernel-*
Last metadata expiration check: 2:01:30 ago on Fri Apr 29 11:54:49 2022.
Error:
Problem 1: package kernel-4.18.0-348.23.1.el8_5.x86_64 requires kernel-modules-uname-r = 4.18.0-348.23.1.el8_5.x86_64, but none of the providers can be installed
- cannot install the best update candidate for package kernel-4.18.0-348.20.1.el8_5.x86_64
- package kernel-modules-4.18.0-348.23.1.el8_5.x86_64 is filtered out by exclude filtering
Problem 2: package kernel-4.18.0-348.23.1.el8_5.x86_64 requires kernel-modules-uname-r = 4.18.0-348.23.1.el8_5.x86_64, but none of the providers can be installed
- cannot install the best update candidate for package kernel-4.18.0-348.el8.x86_64
- package kernel-modules-4.18.0-348.23.1.el8_5.x86_64 is filtered out by exclude filtering
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Often errors like this can be resolved by running `dnf makecache`
System update process has finished.
I ran dnf makecache in terminal and tried to run the update again and i got same error using 102.0.13 cPanel 8.5 AlmaLinux
-
PS I have KernelCare purchase from cPanel on this server. just fyi so when I try to update I do not leave the check mark enabled, Cause KernelCare takes care of that. 0 -
Hey hey! I reached out to the CloudLinux team about this and they let me know this looks like a bad repository related to KernelCare. If you're seeing this frequently and it's not just a one-off issue, could you submit a ticket so we can do some more testing? 0 -
If you're seeing this frequently and it's not just a one-off issue, could you submit a ticket so we can do some more testing?
ever time I click update without the checkmark I get that error. will submit a ticket and post it here thanks0 -
Hey hey! I reached out to the CloudLinux team about this and they let me know this looks like a bad repository related to KernelCare. If you're seeing this frequently and it's not just a one-off issue, could you submit a ticket so we can do some more testing?
#94441775 just added. since i am low priority ;) i added per cPRex hopefully that rings a bell to get my ticket looked at lol0 -
Oh man, that might make it take *longer* actually!!! 0 -
Hey there guys I have a similar error - but different error message... I don't think related, so not sure if I need a new thread (please move if necessary) - but since we are here.... see next post ! can't edit code here.... 0 -
For some reason I am unable to enter / edit the code (clicking on the code icon took me to a "Forum List " list of posts....) I am using the quote feature instead. Here is the error message I am seeing... [QUOTE] 0 -
For some reason I am unable to enter / edit the code (clicking on the code icon took me to a "Forum List " list of posts....) I am using the quote feature instead. Here is the error message I am seeing...
Can you try to force toe update /scripts/upcp "force0 -
@WorkinOnIt also what version of cPanel are you on plus you have centos 7 correct or cloudlinux version ? 0 -
Hey hey! I reached out to the CloudLinux team about this and they let me know this looks like a bad repository related to KernelCare. If you're seeing this frequently and it's not just a one-off issue, could you submit a ticket so we can do some more testing?
from support: We've seen this issue before, your dnf is trying to download an outdated version of a dependency rather than the newer one already installed then it gets stuck. It's a common issue where the workaround is simply changing "best=True" to "best=False" in the dnf configuration file. I went ahead and edited this file for you:[18:50:47 server1 root@94441775 ~]cPs# diff -u /root/cptechs/94441775/dnf.conf /etc/dnf/dnf.conf --- /root/cptechs/94441775/dnf.conf 2022-04-30 18:49:57.507000000 -0500 +++ /etc/dnf/dnf.conf 2022-04-30 18:50:17.451000000 -0500 @@ -6,5 +6,5 @@ gpgcheck=1 installonly_limit=3 clean_requirements_on_remove=True -best=True +best=False skip_if_unavailable=False
I then confirmed dnf update was working properly:[18:50:17 server1 root@94441775 ~]cPs# dnf update Last metadata expiration check: 3:21:47 ago on Sat 30 Apr 2022 03:28:43 PM CDT. Dependencies resolved. ============================================================================================================================================================================================================ Package Architecture Version Repository Size ============================================================================================================================================================================================================ Installing: kernel x86_64 4.18.0-348.23.1.el8_5 baseos 7.0 M Installing dependencies: kernel-core x86_64 4.18.0-348.23.1.el8_5 baseos 38 M kernel-modules x86_64 4.18.0-348.23.1.el8_5 baseos 30 M Transaction Summary ============================================================================================================================================================================================================ Install 3 Packages Total download size: 74 M Installed size: 90 M Is this ok [y/N]: n
this corrected the issue.0 -
I'm glad you got that resolved, @Spirogg !!! 0 -
@Spirogg yes, I think it was the timing out at their end..... 0
Please sign in to leave a comment.
Comments
13 comments