The system cannot check the kernel status: “/usr/bin/yum” reported error code “1”
Hello,
I keep getting yum update error during automated updates. Manually updated yum always works fine.
The system cannot check the kernel status: “/usr/bin/yum” reported error code “1” when it ended: failed to open: /var/cache/dnf/cloudlinux-x86_64-server-8-0db977d054401728/repodata/179af3b1e3037c9c86ea52a93128f3a06aecef6cf2bb09696b8dda31f05945d7-filelists.xml.gz
I opned a ticket with CloudLinux and they pointed to cPanel has having a known issue?
Please note that dnf.log file has the following error:
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 67, in main
return _main(base, args, cli_class, option_parser_class)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 106, in _main
return cli_run(cli, base)
File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 122, in cli_run
cli.run()
File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 1055, in run
return self.command.run()
File "/usr/lib/python3.6/site-packages/dnf/cli/commands/__init__.py", line 226, in run
self.opts.packages)
File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 523, in output_packages
raise dnf.exceptions.Error(_('No matching Packages to list'))
dnf.exceptions.Error: No matching Packages to list
2025-05-20T16:24:13-0500 CRITICAL Error: No matching Packages to list
I can this issue has been reported to cPanel team here:
https://support.cpanel.net/hc/en-us/community/posts/19163545155095
Can you please create a ticket for cPanel team with the same error message and the reported error from dnf.log file?
I believe they have an open task for this issue.
Any thoughts on this?
-
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 -
Sorry to be confusing. Here is a run down of events.
- 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.
- I opened a ticket with Cloudlinux since the above DNF starts with /var/cache/dnf/cloudlinux-x86_64- ....
- Cloud linux support say just run yum clean all, yum makecahce, yum update
- Yes, that does update the server without error, but I should not have to manually update my server. It should update itself.
- Then they escalate the ticket
- Escalated support says, this is a know issue with cpanel. open a ticket with them.
- 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 -
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 -
It is 252439 ticket.
0 -
Thanks for that - I've reached out to them for some context and I'll let you know once I hear back!
0 -
Thank you
0 -
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 -
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.
Comments
8 comments