yum update failed rpmdb open failed

TL;DR

rpmdb open failed means rpm cannot open its own database, usually stale lock files and mmap cache left by a killed process, or genuine index damage. Remove the stale __db files in the rpm database folder, rebuild the indexes with rpm --rebuilddb, and verify with rpm -qa. Take a backup copy of the database folder first; on RHEL 8 and later the database is sqlite and the recovery differs slightly.

yum update failed rpmdb open failed

Use this when

• yum and rpm commands all fail with rpmdb open failed or error: cannot open Packages index.
• The host crashed or a yum process was killed with kill -9.
• rpm -qa returns nothing or errors partway through.

Not for this skill when

• Only yum fails while rpm -qa works. That points at yum config or plugins, not the database.
• The database opens but a transaction fails. Work the transaction error instead.

Steps

1. Check for any running yum, dnf, or rpm process and let it finish or stop it cleanly. Verify: no process holds the database
2. Copy the entire rpm database folder (under var lib rpm) to a backup location. Verify: the backup copy exists and matches in size
3. Delete the stale __db.00* lock files in the database folder. Verify: only the database files themselves remain
4. Run rpm --rebuilddb and wait for it to finish without interruption. Verify: the command exits cleanly
5. Test with rpm -qa and a yum check. Verify: the package list returns and yum opens normally

Variant phrasings

error rpmdb open failed rebuilddb fix

The standard phrasing.

rpm database corrupt cannot open packages index

The older rpm error phrasing.

yum killed rpmdb stale lock __db

The cause phrasing after a forced kill.

Compatibility: Compatibility: rpm 4.x on RHEL-family systems; RHEL 8 and later use a sqlite rpmdb, earlier releases use Berkeley DB.

Why it happens

The rpm database is opened by every package operation, and its lock and cache files assume orderly shutdowns. A SIGKILL or power loss leaves those files describing a state that no longer exists, so the next open fails before yum even reads a repository. Rebuilding regenerates the indexes from the package headers, which is why the backup matters if the headers themselves are damaged.

Edge cases / pitfalls

• If rebuilddb produces an empty database, the Packages file itself is damaged; restore from backup or from the daily rpmdb copy some distros keep.
• Repeated corruption on the same host is a disk or filesystem symptom; check dmesg and SMART data instead of rebuilding weekly.
• On sqlite backends, deleting the __db files does not apply; use rpm --rebuilddb directly and check the sqlite file integrity if it fails.

Provenance

Resolved from the public thread: https://vectle.com/posts/psty8Jqhxz6dfFR-jcng8hag

Resolved from the public thread: https://vectle.com/posts/psty8Jqhxz6dfFR-jcng8hag

Thread query: yum update failed rpmdb open failed

TL;DR: rpmdb open failed means rpm cannot open its own database, usually stale lock files and mmap cache left by a killed process, or genuine index damage. Remove the stale __db files in the rpm database folder, rebuild the indexes with rpm --rebuilddb, and verify with rpm -qa. Take a backup copy of the database folder first; on RHEL 8 and later the database is sqlite and the recovery differs slightly.