Bug 89981
| Summary: | db4 lockers table (known bug upstream) | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Phil Mayers <p.mayers> |
| Component: | db4 | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | barryn, taj |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| URL: | http://www.openldap.org/lists/openldap-bugs/200208/msg00130.html | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-11-14 04:22:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Phil Mayers
2003-04-30 19:03:23 UTC
The first linked patch does *not* fix the problem - I'm about to re-build the RPM and try the 2nd patch. FWIW, recent versions of RPM (4.0.5, 4.1.x and 4.2 for sure) do not use the systemwide Berkeley DB any longer -- they use their own private copies instead. (In the case of 4.0.5/4.1.x/4.2, it's a patched db 4.1.24, I think. Check the RPM changelogs/documentation for more information.) Hmm. The 2nd patch didn't seem to fix it either. It's good to know that RPM doesn't use the system libdb - I'll probably upgrade to the 4.1 track from source in that case and see if it goes away - although I've rolled the machine back to 7.3 now! Phil says: [I am also a bit worried that RPM will eventually fall foul of this - that would be disastrous!] Nothing like seeing that as the first hit in google. After performing yum install db4-devel (unrelated?) in fedora rawhide, ... ------------------------------------------------------------- rpm -qa rpmdb: Lock table is out of available locker entries error: db4 error(22) from db->close: Invalid argument error: cannot open Packages index using db3 - Cannot allocate memory (12) error: cannot open Packages database in /var/lib/rpm no packages ------------------------------------------------------------- Phil also says "A db_recover seems to cure this." would there be more to the command line than 'db_recover?' I assume this should be opened as a seperate bug? I've had no problems with rpm until I did the install of db4-devel and then this. In fact it got a little further. All of the following worked 1044 yum install db4-devel 1045 yum install gcc-g77 1048 yum install evolution-devel gmp-devel gd-devel 1050 yum install slang-devel gpm-devel then bad news as seen above with 1056 yum install libjpeg-devel libungif-devel libtiff-devel zlib-devel gettext rpm-(-devel)4.3.2-8.x86_64.rpm db4(-devel)4.2.52-6.x86_64.rpm Filed comment 4 as a new bug. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134427 From my (recent) exeperience with a db lockers table full problem in rpm, the issue was not closing cursors and databases, causing table overflow eventually. The defaults should be sufficient for general purpose use, that's certainly the case within my rpm experience. If OpenLDAP is an exception that truly needs a larger table, then pleas reopne this bug and get confirmation that, indeed, OpenLDAP needs more table entries. |