• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

mchk error

D

dourtyb

Guest
I am running RHEL 3.0, Plesk 7.5.2, and get the following error when I try to run mchk.

./mchk -v
rpmdb: fatal region error detected; run recovery
error: db4 error(-30982) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30982)
mchk: Unable to open rpm db: cannot open Packages index using db3 - (-30982)


System error 2: No such file or directory
mchk: Unable to open rpm db: cannot open Packages index using db3 - (-30982)


System error 2: No such file or directory
 
We have seen this problem also. I will update this when we have identified a resolution to the problem.

- Chris
 
I found the solution. It is to remove the __db.00x files in /var/lib/rpm and then run rpm --rebuilddb. mchk -v will then run. I've had to rebuild the RPM database a couple of times since I installed 7.5.2. I'm not sure what keeps corrupting the RPM database. It isn't right.

Does anyone know what mchk -v actually does?

Brian Dourty
 
Back
Top