Skip to main content

The YUM cache is incomplete. The system is updating the cache to repair the issue. This operation can take a few minutes to complete (it is very network and disk i/o intensive). EasyApache 4

Webmasterserviceshawaii

Aloha its super strange that I have two servers on Atlantic.net with the same exact error messages when trying to access apache 4 to make some minor changes. Below is my server info and then below that is what my server team said is the issue.

OS
CentOS v7.9.2009 STANDARD kvm
cPanel Version
110.0.24
 
I have a server support staff that seemed to be pretty good however they recomended that I reach out directly to Cpanel for some assitance with this. In the past I could create a support ticket via WHM however its telling me that its not an option.
 
Any help with be greatly appreciated. 
 

Hello Gary,

We wanted to provide you with an update regarding the YUM error you reported encountering on both servers. After a thorough investigation, we have identified the root cause and attempted to resolve the issue, but unfortunately, we have encountered some challenges.

The error message you received:

"YUM encountered errors outside of EasyApache 4. Log into the system via SSH to resolve them, or you can click the 'Refresh' button to rebuild the system's cache,"

This typically indicates that the package manager on the server is unable to build its local cache successfully. Despite our efforts to address this by cleaning the package manager cache and running the yum update command, we were unable to resolve the issue.

Furthermore, during the yum update command, we encountered another error related to one of the configured repositories failing (Let's Encrypt for cPanel), which resulted in yum not having enough cached data to continue.

One of the configured repositories failed (Let's Encrypt for cPanel), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail

This indicates a potential RPM database corruption issue, which we repaired the same but the error still showing.

Given the complexity of the issue and the persistence of the error even after we attempt to troubleshoot and resolve it, we recommend reaching out to cPanel support for further assistance. They have the expertise and tools necessary to address such system-level issues, especially those arising after system updates.

We understand the urgency of resolving this matter and we suggest contacting cPanel support to resolve this error at the earliest.

Please feel free to reach out if you have any questions or if there's anything else we can assist you with.

Comments

5 comments

Date Votes

Please sign in to leave a comment.

Didn't find what you were looking for?

New post