error: db3 error(-) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery

error: db3 error(-) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery can occur if there is corruption in your rpm database.

Situations also include :

rpmdb: Thread/process /failed: Thread died in Berkeley DB library

error: db3 error(-) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery

error: cannot open Packages index using db3 - (-)

error: cannot open Packages database in /var/lib/rpm

An error has occurred:

<class '_rpm.error'>

# db3 error(-xxxx) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery

For such cases performing the following in should correct the issue:

rpm -qa 
rm -f /var/lib/rpm/__*
rpm --rebuilddb




  • 53 Users Found This Useful

Was this answer helpful?

Related Articles

central_filter defer (-17): error in filter file: unknown filtering command r_subject: near line 22 of filter file

The error "central_filter defer (-17): error in filter file: unknown filtering command r_subject:...

Account's error_log produces flood of missing modules

 Account's error_log produces flood of missing modules. Ex:   From error_log:     [23-Apr-2018...

ModSecurity: collection_store: Failed to access DBM file /var/cpanel/secdatadir/ip: Permission denied

The error Failed to access DBM file /var/cpanel/secdatadir/ip: Permission denied can occur on...

Failed to start tailwatchd - Unit tailwatchd service entered failed state

Failed to start tailwatchd. Unit tailwatchd.service entered failed state.  tailwatchd.service...

FSCK Options and Maintenance

Provided below are some useful commands pertaining to FSCK. Update commands to your environment /...