Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 103379 - rpm hangs upon using
rpm hangs upon using
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
i686 Linux
high Severity high
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-08-29 11:09 EDT by Jack Malmostoso
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-09-01 12:37:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jack Malmostoso 2003-08-29 11:09:38 EDT
Description of problem:
When using ANY operation involving the rpm command (rpm, or apt-get), rpm hangs 
giving this output:

rpmdb:unable to join environment
error:db4 error(11) from dbenv->open:resource temporarily unavailable (11)
error:cannot open Packages database in /var/lib/rpm

This happens when 4/5 rpm commands are issued.
Upon reboot rpm works, but breaks after a few usages: I tried to download all of 
the 4.2-1 packages at rpm.org and I could install them after rebooting. Then I 
tried rpm -qa to see if anything changed, but it hanged.
I rebooted another time and it worked for three rpm -qa | grep <name>, then 

Version-Release number of selected component (if applicable):
rpm 4.2-1

How reproducible:

Steps to Reproduce:
1.use the rpm command a few times (few lower than 10)
2.rpm hangs
Actual results:

Expected results:

Additional info:
Comment 1 Jeff Johnson 2003-09-01 10:48:13 EDT
    rm -f /var/lib/rpm/__db*
Does that fix?
Comment 2 Jack Malmostoso 2003-09-01 11:40:47 EDT
I have tried it (i read the page on rpm.org) and this far everything looks good, 
but I must say I didn't make an intensive use of RPM.
But I'm optimistic :-)
Thank you for now!

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