Bug 454857 - db-4 in openldap needs new patches
db-4 in openldap needs new patches
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: openldap (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Jan Safranek
Depends On:
  Show dependency treegraph
Reported: 2008-07-10 04:55 EDT by Jan Safranek
Modified: 2009-01-20 15:53 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 15:53:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0090 normal SHIPPED_LIVE openldap bug fix and enhancement update 2009-01-20 11:04:26 EST

  None (edit)
Description Jan Safranek 2008-07-10 04:55:06 EDT
Description of problem:
We shop openldap-servers with it's own version of Berkeley DB. Currently we ship
ver. db-4.4.20, with two official patches. Upstream released additional two
patches, improving the stability of the database.

We should apply these patches to prevent database corruption. See
for description - we ship the first two, I'd like to add the later ones.

There is no reproducer. The database gets corrupted in very specific conditions
only - see the patch description.
Comment 1 RHEL Product and Program Management 2008-07-10 05:00:27 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 6 errata-xmlrpc 2009-01-20 15:53:45 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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