RPM Database Lock Contention During DNF Operations

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

dnf reports another app is holding the lock and transactions fail.

Environment & Reproduction

Use ps aux | grep -E ‘dnf|rpm’ and lsof /var/lib/rpm/.rpm.lock.

Root Cause Analysis

Determine whether lock is valid active work or a stale interrupted process.

Quick Triage

Concurrent automation, hung package jobs, or abrupt shutdown left a stale state.

Step-by-Step Diagnosis

Wait for active transactions to finish or stop only truly stuck dnf/rpm jobs.

Solution – Primary Fix

Run rpm –rebuilddb, then dnf clean all and retry.

Solution – Alternative Approaches

Install a small package with dnf to verify transaction integrity.

Verification & Acceptance Criteria

No direct firewall dependency, but confirm repos are reachable before retest.

Rollback Plan

Validate labels under /var/lib/rpm if custom restore scripts were used.

Prevention & Hardening

Inspect journalctl and /var/log/dnf.log around the lock contention window.

Related Errors & Cross-Refs

Serialize package operations in CI/CD and configuration management runs.

Related tutorial: View the step-by-step tutorial for rhel-9.

View all rhel-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Restore RPM DB from backup snapshot if rebuilddb does not recover state.