Skip to main content

The system cannot check the kernel status: “/usr/bin/yum” reported error code “1”

Comments

8 comments

  • cPRex Jurassic Moderator

    Hey hey!  I'm really confused with this post, so I want to clarify a few things.

    When you receive the "The system cannot check the kernel status" error, is that from a upcp nightly notification?

    As far as the code snippet from the dnf log, I'm not entirely sure how that's related, honestly.

    The other thread linked is talking about Security Advisor, which is a separate process from the nightly update, so I'm also not sure how that would be related.

    Did CloudLinux provide some context on how these things would all be related?  Or is the original kernel error coming from Security Advisor?

    0
  • JIKOmetrix

    Sorry to be confusing. Here is a run down of events. 

    1. When cpanel runs its update on one of my servers via automated cron, I get an email from cpanel with an error, "The system cannot check the kernel status: “/usr/bin/yum” reported error code “1” when it ended: Error: Cannot open file "/var/cache/dnf/cloudlinux-x86_64-server-8-da32511927ff2ed7/repodata/6fcacc38beb0dc5182965e6f97be2968a23db94ab29325d07ab7d8ad9301f93a-modules.yaml.gz": No such file or directory. 
    2. I opened a ticket with Cloudlinux since the above DNF starts with /var/cache/dnf/cloudlinux-x86_64- ....
    3. Cloud linux support say just run yum clean all, yum makecahce, yum update
    4. Yes, that does update the server without error, but I should not have to manually update my server. It should update itself. 
    5. Then they escalate the ticket
    6. Escalated support says, this is a know issue with cpanel. open a ticket with them. 
    7. Above is the last part of my ticket that support seemed to say it is a known cpanel issue. 

    Does this help or make it less clear?

    0
  • cPRex Jurassic Moderator

    Perfect - thanks so much.

    I'm not aware of any specific cPanel issues at this time that would cause this.  Would you happen to have your CloudLinux ticket number so I can reach out to their team?

    0
  • JIKOmetrix

    It is 252439 ticket. 

    0
  • cPRex Jurassic Moderator

    Thanks for that - I've reached out to them for some context and I'll let you know once I hear back!

    0
  • JIKOmetrix

    Thank you

    0
  • cPRex Jurassic Moderator

    Alright - it seems that case CPANEL-42350 is the one that would address these issues, but it hasn't seen any action yet.  I've given it some priority so the developers can look at it during their next meeting.

    I'm not sure exactly when this will be resolved though, so I can't provide an ETA at this point.

    0
  • JIKOmetrix

    Ah ha! :-)

    Yeah it's been this for a while on just the one server. My other servers do not do this. 

    1

Please sign in to leave a comment.