One of the following errors may appear:
The following error appears when I run the Plesk autoinstaller
error: rpmdb: BDB0113 Thread/process 19176/139826746189824 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 YumBaseError: Error: rpmdb open failed
In some cases, this error is shown in the Plesk autoinstaller:
ERROR: The Yum utility failed to install the required packages. Attention! Your software might be inoperable. Please, contact product technical support. RepoError: database disk image is malformed Execute command /usr/local/psa/admin/bin/send-error-report install Error: The Yum utility failed to install the required packages.
rpmcommand may be stuck, for example:
rpm -qf /usr/local/psa/version
Rpm shows an error as below:
# rpm -qa | grep php rpmdb: unable to join the environment error: db4 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db3 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm
Plesk upgrade fails with this error:
Error while preparing to install packages: pkgKey 3976 doesn't exist in repo base. Trying again. Error while preparing to install packages: pkgKey 3976 doesn't exist in repo File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 432, in _packageByKey raise Errors.RepoError, msg RepoError: pkgKey 3976 doesn't exist in repo base Error: The Yum utility failed to install the required packages.
The "Warning: Permission denied." error is shown in Web Server Settings under Websites & Domains.
- Unable to manage Plesk services such as DNS or PHP settings. In Tools & Settings > Server Components, all components are shown as not installed.
The RPM database is corrupted.
Backup the RPM database files:
cd /var/lib/rpm/ mv __db.* ~
Remove the corrupted database files:
rm -f /var/lib/rpm/__db.*
Rebuild the RPM database: