Bug 103993 - 2.6 Test Kernel kills access to RPM Database
2.6 Test Kernel kills access to RPM Database
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
9
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
http://people.redhat.com/arjanv/2.5/R...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-09-08 17:27 EDT by Omkhar Arasaratnam
Modified: 2007-04-18 12:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:41:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Omkhar Arasaratnam 2003-09-08 17:27:54 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030807

Description of problem:
The following error is observed if the latest (sept 5th) 2.6.0-0.test4.1.33
kernels are installed on RH9 with the latest errata.

[root@omkhar root]# rpm -qa
rpmdb: unable to join the environment
error: db4 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index using db3 - Resource temporarily unavailable (11)
error cannot open Packages database in /var/lib/rpm
no packages

However, this works fine under 2.4.20-20.9

Version-Release number of selected component (if applicable):
2.6.0-0.test4.1.33

How reproducible:
Always

Steps to Reproduce:
See above
    

Actual Results:  See Above

Expected Results:  See above

Additional info:
Comment 1 Omkhar Arasaratnam 2003-09-26 15:53:49 EDT
Apparently this can be resolved with the latest RPM from here :
ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.2.x

Perhaps this can be added as a dependancy?
Comment 2 Bugzilla owner 2004-09-30 11:41:31 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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