Bug 1033013 - frequently facing the rpmdb error.
Summary: frequently facing the rpmdb error.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rpmdb-redhat
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Daniel Mach
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-21 12:22 UTC by Gopikannan Ellappan
Modified: 2016-06-21 12:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-21 12:58:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Gopikannan Ellappan 2013-11-21 12:22:34 UTC
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:

Comment 1 Gopikannan Ellappan 2013-11-22 10:30:10 UTC
Hi Daniel,

Could you please check and update me? Its blocking me here..!

Comment 2 Daniel Mach 2016-06-21 12:58:54 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.