Incomplete or inconsistent data may be written to the rpmdb when a crash event occurs for an RPM or YUM transaction that was updating the RPM database, causing RPM database corruption. The reason for the crash could be a variety of reasons such as killing the process prematurely or resource or disk issues.
A corrupt RPM database can cause a myriad of issues related to package-management. Software such as EasyApache4 and YUM will also not work until the RPM database is in a functional state. Due to this, one of cPanel & WHM's tasks during update sessions includes performing a check of the database and attempting a repair if needed. However, sometimes you may need to run this process manually.
This check may be performed from WHM or the command-line.
- Navigate to "Home » Software » Rebuild RPM Database"
- Click the "Proceed >>" button.
- Log in as root.
- Run the find_and_fix_rpm_issues script.
If script times out or does not respond, please review the following article.