Bug 743824 - openldap does not work after libdb rebase
Summary: openldap does not work after libdb rebase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openldap
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Vcelak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 08:18 UTC by Jan Vcelak
Modified: 2013-10-16 07:23 UTC (History)
4 users (show)

Fixed In Version: openldap-2.4.26-5.fc16
Clone Of:
Environment:
Last Closed: 2012-01-25 09:55:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1019613 0 unspecified CLOSED openldap does not work after libdb rebase 2021-02-22 00:41:40 UTC

Internal Links: 1019613

Description Jan Vcelak 2011-10-06 08:18:35 UTC
Description of problem:

libdb in F16 was rebased and therefore OpenLDAP has to be rebuild

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

openldap-2.4.26-4.fc16
libdb-5.2.36-1.fc16

How reproducible:


Steps to Reproduce:
1. # slapd -u ldap -g ldap -d1
2.
3.
  
Actual results:

...
slapd init: initiated server.
slap_sasl_init: initialized!
bdb_back_initialize: initialize BDB backend
bdb_back_initialize: BDB library version mismatch: expected Berkeley DB 5.2.28: (June 10, 2011), got Berkeley DB 5.2.36: (September 14, 2011)
backend_init: initialized for type "bdb"
slapd destroy: freeing system resources.
slapd stopped.
connections_destroy: nothing to destroy.

Expected results:

slapd will start

Additional info:

Comment 1 Fedora Update System 2011-10-06 08:44:35 UTC
openldap-2.4.26-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/FEDORA-2011-12550

Comment 2 Fedora Update System 2011-11-05 01:25:36 UTC
openldap-2.4.26-5.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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