Symptoms
You receive a security advisor notification with some or all of the following messages:
The system cannot check the kernel status: “/usr/bin/yum” reported error code “1”
when it ended
[Errno 14] HTTP Error 404 - Not Found Trying other mirror. It looks like you
encountered an issue when performing the operation. Please check if the issue
related to CloudLinux repositories. Usually our repositories contain "cloudlinux"
word in their name. If it does, check our knowledgebase for a possible solution or
contact support: https://www.cloudlinux.com/support-portal/ In other cases,
please contact your system administrator to fix the issue.
[Errno 14] HTTPS Error 403 - Forbidden Trying other mirror. It looks like you
encountered an issue when performing the operation. Please check if the issue
related to CloudLinux repositories. Usually our repositories contain "cloudlinux"
word in their name. If it does, check our knowledgebase for a possible solution or
contact support: https://www.cloudlinux.com/support-portal/ In other cases,
please contact your system administrator to fix the issue.
[Errno -1] Metadata file does not match checksum Trying other mirror.
[Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Trying other mirror.
Description
The package manager is attempting to reach out and get information about updates but is receiving errors from the package mirror servers. This can be due to local issues with the package manager or upstream issues with the mirror servers. You can check any published issues on CloudLinux here:
Workaround
You can verify that your package manager is using the most up-to-date information from the mirrors by clearing and updating the cache. Once those are done you can see if a check-update completes successfully:
CL 7 systems:
yum clean all
yum makecache
yum check-update
CL 8 systems:
dnf clean all
dnf makecache
dnf check-update
If this is an upstream issue on the mirror servers, the issue will clear itself up after some time. If the check-update continues to fail, please contact your System Administrator or open a support ticket for a second look.
Comments
0 comments
Article is closed for comments.