yum update stuck with conflicting requests due to kmod-lve ?

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • oceanwave
    Member
    Forum ExplorerTechnical Associate
    • Dec 2024
    • 56

    #1

    yum update stuck with conflicting requests due to kmod-lve ?

    On CL 9.8, I notice the following today; second server I checked has same issue today.

    Do I need to manually fix this on each server?

    I believe by default it keeps the latest 3 kernels and latest 3 kmod-lve versions.

    Code:
    yum update
    Last metadata expiration check: 0:07:10 ago on Mon 06 Jul 2026 03:03:30
    AM EDT.
    Error:
    Problem 1: package kmod-lve-2.1-59.el9.x86_64 from system requires
    kernel(__put_cred) = 0x1ea3167a, but none of the providers can be installed
    - package kmod-lve-2.1-59.el9.x86_64 from system requires
    kernel(__put_task_struct) = 0x25bbcf08, but none of the providers can be
    installed
    - package kmod-lve-2.1-59.el9.x86_64 from system requires
    kernel(__tracepoint_sched_set_state_tp) = 0x2dc2a350, but none of the
    providers can be installed
    - package kmod-lve-2.1-59.el9.x86_64 from system requires
    kernel(bpf_trace_run12) = 0x99a4ecec, but none of the providers can be
    installed
    .....
    - conflicting requests
    Problem 2: package kmod-lve-2.1-56.el9.x86_64 from system requires
    kernel(__put_cred) = 0x1ea3167a, but none of the providers can be installed
    - package kmod-lve-2.1-56.el9.x86_64 from system requires
    kernel(__put_task_struct) = 0x25bbcf08, but none of the providers can be
    installed
    - package kmod-lve-2.1-56.el9.x86_64 from system requires
    kernel(__tracepoint_sched_set_state_tp) = 0x2dc2a350, but none of the
    providers can be installed
    - package kmod-lve-2.1-56.el9.x86_64 from system requires
    kernel(bpf_trace_run12) = 0x99a4ecec, but none of the providers can be
    installed
    - package kmod-lve-2.1-56.el9.x86_64 from system requires
    ....
    - package kmod-lve-2.1-56.el9.x86_64 from system requires
    kernel(wake_up_process) = 0xf607df2f, 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)
  • Answer selected by oceanwave at 07-08-2026, 09:51 AM.
    bogdan.sh
    Administrator
    • Nov 2016
    • 1315

    Thanks for the output. Good news: the mirror side is fine now, makecache pulled everything cleanly. The problem now is local. You have three kmod-lve versions installed, and the two older ones (2.1-59 and 2.1-61.1) were built for kernels you no longer have. Each kmod-lve is tied to a specific kernel, so those two can't be satisfied, and dnf won't run any update until they're gone. Version 2.1-66 matches your current kernel, so keep that one.

    Check what's installed and which is loaded:
    Code:
    rpm -qa 'kmod-lve*' | sort -V
    cat /sys/module/kmodlve/version

    Then remove the two old ones and update:
    Code:
    yum remove kmod-lve-2.1-59.el9 kmod-lve-2.1-61.1.el9
    yum update
    If yum remove complains about dependencies, drop them from the rpm database only (this won't touch the loaded module) and retry:
    Code:
    rpm -e --nodeps --justdb kmod-lve-2.1-59.el9.x86_64 kmod-lve-2.1-61.1.el9.x86_64
    yum update

    Reboot onto the latest kernel afterwards. Same three commands work across your other servers.

    Comment

    • bogdan.sh
      Administrator
      • Nov 2016
      • 1315

      #2
      This wasn't anything wrong on your servers - one of our mirrors had fallen behind and was serving stale metadata, so kmod-lve was being offered without the matching kernel symbols. We've already pulled that mirror out of rotation, so new updates will come from a healthy one.

      You shouldn't need to touch each server by hand. Just clear the cached metadata and re-run the update:
      Code:
      yum clean all
      yum makecache
      yum update

      If a box still complains after that, run rpm -qa 'kmod-lve*' | sort -V and uname -r and paste the output here - but in most cases the cache refresh is all it takes.

      Cheers

      Comment

      • oceanwave
        Member
        Forum ExplorerTechnical Associate
        • Dec 2024
        • 56

        #3
        Thanks very much, but that did not solve it.

        Code:
        # rpm -qa 'kmod-lve*' | sort -V
        kmod-lve-2.1-59.el9.x86_64
        kmod-lve-2.1-61.1.el9.x86_64
        kmod-lve-2.1-66.el9.x86_64
        
        # uname -r
        5.14.0-687.17.1.el9_8.x86_64
        Code:
        # yum clean all
        355 files removed
        
        # yum makecache
        EA4 ( EasyApache 4 - c9 )                                 1.3 MB/s | 1.5
        MB     00:01
        cPanel Plugins project                                  194 kB/s | 148
        kB     00:00
        MariaDB105                                  390 kB/s | 608 kB     00:01
        AlmaLinux 9.8 - AppStream                                  59 MB/s |  15
        MB     00:00
        AlmaLinux 9.8 - BaseOS                                   53 MB/s |  14
        MB     00:00
        AlmaLinux 9.8 - CRB                                  27 MB/s | 4.0 MB  
          00:00
        alt common Extended Lifecycle Support by TuxCare                        
                  1.6 MB/s | 1.0 MB     00:00
        CloudLinux 9 - Updates                                   26 MB/s |  37
        MB     00:01
        CloudLinux 9 EasyApache4                                  3.0 MB/s | 1.4
        MB     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 1                              
           708  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 2                              
           765  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 3                              
           732  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 4                              
           737  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 5                              
           770  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 6                              
           1.0 kB/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 7                              
           990  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 8                              
           763  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 9                              
           739  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 10                              
            762  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 11                              
            743  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 12                              
            767  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 13                              
            818  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 14                              
            800  B/s | 257  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 17                              
            766  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 18                              
            793  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 19                              
            751  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 20                              
            796  B/s | 258  B     00:00
        CloudLinux-EA4-9 - Gradual Rollout Slot 21                              
            763  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 1                                
        762  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 2                                
        788  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 3                                
        773  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 4                                
        754  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 5                                
        781  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 6                                
        954  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 7                                
          74 kB/s |  22 kB     00:00
        CloudLinux-9 - Gradual Rollout Slot 8                                
        773  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 9                                
        764  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 10                                
          767  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 11                                
          786  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 12                                
          784  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 13                                
          786  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 14                                
          778  B/s | 257  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 15                                
          772  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 16                                
          782  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 17                                
          738  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 18                                
          757  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 19                                
          752  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 20                                
          747  B/s | 258  B     00:00
        CloudLinux-9 - Gradual Rollout Slot 21                                
          739  B/s | 258  B     00:00
        Extra Packages for Enterprise Linux 9 - x86_64                          
                 19 MB/s |  21 MB     00:01
        Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64  
                                      3.8 kB/s | 2.5 kB     00:00
        Imunify360 - Gradual Rollout Slot 1                                 805
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 2                                  42
        kB/s |  12 kB     00:00
        Imunify360 - Gradual Rollout Slot 3                                 739
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 4                                 784
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 5                                 1.0
        kB/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 6                                 814
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 7                                 745
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 8                                 750
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 9                                 776
        B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 10                                
          775  B/s | 258  B     00:00
        Imunify360 - Gradual Rollout Slot 11                                
          674  B/s | 241  B     00:00
        Imunify360 - Gradual Rollout Slot 12                                
          669  B/s | 241  B     00:00
        EL-9 - Imunify360                                 5.4 MB/s | 3.2 MB  
          00:00
        WP Toolkit for cPanel                                 528 kB/s | 117 kB
            00:00
        WP Toolkit third parties                                   48 kB/s | 8.5
        kB     00:00
        Metadata cache created.
        
        # yum update
        Error:
          Problem 1: package kmod-lve-2.1-61.1.el9.x86_64 from @System requires
        kernel(__put_cred) = 0x1ea3167a, but none of the providers can be installed
        ...
          - package kmod-lve-2.1-61.1.el9.x86_64 from @System requires
        kernel(wake_up_process) = 0xf607df2f, but none of the providers can be
        installed
           - conflicting requests
          Problem 2: package kmod-lve-2.1-59.el9.x86_64 from @System requires
        kernel(__put_cred) = 0x1ea3167a, 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)​

        Comment

        • bogdan.sh
          Administrator
          • Nov 2016
          • 1315

          #4
          Thanks for the output. Good news: the mirror side is fine now, makecache pulled everything cleanly. The problem now is local. You have three kmod-lve versions installed, and the two older ones (2.1-59 and 2.1-61.1) were built for kernels you no longer have. Each kmod-lve is tied to a specific kernel, so those two can't be satisfied, and dnf won't run any update until they're gone. Version 2.1-66 matches your current kernel, so keep that one.

          Check what's installed and which is loaded:
          Code:
          rpm -qa 'kmod-lve*' | sort -V
          cat /sys/module/kmodlve/version

          Then remove the two old ones and update:
          Code:
          yum remove kmod-lve-2.1-59.el9 kmod-lve-2.1-61.1.el9
          yum update
          If yum remove complains about dependencies, drop them from the rpm database only (this won't touch the loaded module) and retry:
          Code:
          rpm -e --nodeps --justdb kmod-lve-2.1-59.el9.x86_64 kmod-lve-2.1-61.1.el9.x86_64
          yum update

          Reboot onto the latest kernel afterwards. Same three commands work across your other servers.

          Comment

          • oceanwave
            Member
            Forum ExplorerTechnical Associate
            • Dec 2024
            • 56

            #5
            That worked. Thank you.

            I guess the only drawback is that if you did need to reboot into a very old kernel, lve limits wouldn't load, but that would not be a major problem. And since there is a new kernel, I still have the one older kernel with its one older lve version in case for any reason I needed to boot into an older kernel, so no worry at all removing the old kmod-lve versions.

            Thanks again.

            Comment

            Working...