Plesk fails to update or install packages: RPM database errors

Symptoms

• Unable to update Plesk or install a component, errors being:
  

  CONFIG_TEXT: error: rpmdb: BDB0113 Thread/process 2849489/139868914726976 failed: BDB1507 Thread died in Berkeley DB library
  error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
  error: cannot open Packages index using db5 - (-30973)
  error: cannot open Packages database in /var/lib/rpm
  error: rpmdb: BDB0113 Thread/process 2849489/139868914726976 failed: BDB1507 Thread died in Berkeley DB library
  error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
  error: cannot open Packages database in /var/lib/rpm
  Error: Unable to retrieve the information about the packages installed in the system:
  Failed to read output from the rpm utility.
  Error 1 in execution of rpm

• And attempting to enable SSH access using the Support SSH Access extension :
  

  CONFIG_TEXT: Failed to provide access: Cache update failed: Binary sa-package_yum.sh execution failed with error code 1; stdout [] stderr [error: rpmdb: BDB0113 Thread/process 2849489/139868914726976 failed: BDB1507 Thread died in Berkeley DB library error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main: Error: rpmdb open failed ]

Cause

The package manager database is corrupted.

Resolution

1. Check for lock files in the RPM database directory:
   

   # mv /var/lib/rpm/__db* /tmp/

2. If any lock files are found (e.g., `__db.001`, `__db.002`), remove them:
   

   # rpm --rebuilddb

3. Rebuild the RPM database:
   

   # yum clean all

4. Proceed with the update of Plesk, component installation or SSH access enablement.