Bug 1033013
| Summary: | frequently facing the rpmdb error. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Gopikannan Ellappan <gopikannan.ellappan> |
| Component: | rpmdb-redhat | Assignee: | Daniel Mach <dmach> |
| Status: | CLOSED WONTFIX | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.9 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-21 12:58:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Hi Daniel, Could you please check and update me? Its blocking me here..! It was most likely this problem, rebuilding rpm db would fix it: https://access.redhat.com/solutions/6903 RHEL 4 is EOL already, closing the bug. |
Description of problem: Now we are frequently facing the rpmdb error, while executing the rpm query commands. Even we tried to re-build the db - but after sometime it exists. Especially during the yum-update. it works after clearing the db files and re-building the db. But my question here, is the db is getting corrupted or something else ?? Version-Release number of selected component (if applicable): Rhel 4 Actual results: Failed fetching cluster dependency rpmdb: Thread/process 25356/140122735929248 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm Expected results: Shouldnt get this error without any WA. I want a fix it shouldnt appear again. Additional info: