This guide explains how to rebuild the RPM database using WHM and SSH.
The RPM database can get corrupted if an RPM or YUM update is interrupted or crashes while the database is being updated, because incomplete or inconsistent data may be written to it. Disk problems, low server resources, or a process being stopped too early can cause this.
A damaged RPM database causes many problems with package management. Tools such as YUM and EasyApache 4 will not work until the database is repaired. For this reason, cPanel & WHM check the database during updates and try to fix it when needed. Sometimes, however, you may need to rebuild it manually.
A) To rebuild an RPM database using WHM, follow the steps:
- Log in to WHM.
- In the left-hand menu, go to Software and click Rebuild RPM Database.

- Click on the “Proceed” button.

- If your RPM database is corrupted, WHM will try to repair it.

- This process can take from one to thirty minutes, depending on the speed of your server.
B) To rebuild an RPM database using the command line:
- Log in to SSH as a root user.
- Run the below command:
/scripts/find_and_fix_rpm_issues
Hope you understood how to rebuild an RPM database using WHM and SSH. For any difficulty, reach out to our eukhost’s support specialists.


