Tags Tags

Bug#651700: slapd: BDB library version mismatch

December 11th, 2011 - 08:30 am ET by storm66 | Report spam
Help Create a new topic
Package: slapd
Version: 2.4.25-4+b1
Severity: important

Dear Maintainer,

I think that the openldap package was not compiled with the last
version :
bdb_back_initialize: BDB library version mismatch: expected Berkeley DB 5.1.25: (January 28, 2011)
got Berkeley DB 5.1.29: (October 25, 2011).
slapd stopped.

So slapd dose not start.

Regards

JPP

Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages slapd depends on:
ii adduser 3.113
ii coreutils 8.13-3
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-21
ii libdb5.1 5.1.29-1
ii libgcrypt11 1.5.0-3
ii libgnutls26 2.12.14-4
ii libldap-2.4-2 2.4.25-4+b1
ii libltdl7 2.4.2-1
ii libodbc1 2.2.14p2-5
ii libperl5.14 5.14.2-6
ii libsasl2-2 2.1.25.dfsg1-2
ii libslp1 1.2.1-7.8
ii libwrap0 7.6.q-22
ii lsb-base 3.2-28
ii multiarch-support 2.13-21
ii perl [libmime-base64-perl] 5.14.2-6
ii psmisc 22.14-1
ii unixodbc 2.2.14p2-5

Versions of packages slapd recommends:
ii libsasl2-modules 2.1.25.dfsg1-2

Versions of packages slapd suggests:
ii ldap-utils 2.4.25-4+b1

/etc/default/slapd changed:
SLAPD_CONF="/etc/ldap/slapd.d"
SLAPD_CONF="/etc/ldap/slapd.conf"
SLAPD_USER="openldap"
SLAPD_GROUP="openldap"
SLAPD_PIDFILESLAPD_SERVICES="ldap://192.168.2.8:489 ldapi:///"
SLAPD_SENTINEL_FILE=/etc/ldap/noslapd
SLAPD_OPTIONS=" -4 "





To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 4 repliesReplies Make a reply

Similar topics

Replies

#1 Quanah Gibson-Mount
December 12th, 2011 - 04:40 pm ET | Report spam
wrote:

wrote:

Package: slapd
Version: 2.4.25-4+b1
Severity: important

Dear Maintainer,

I think that the openldap package was not compiled with the last
version :
bdb_back_initialize: BDB library version mismatch: expected Berkeley DB
5.1.25: (January 28, 2011) got Berkeley DB 5.1.29: (October 25, 2011).
slapd stopped.



Actually this indicates that OpenLDAP was recompiled with the latest BDB
version (5.1.29). It is complaining about the fact that your database
was created using the 5.1.25 version, and thus it refuses to start.



Ugh, nm, misread that.

OpenLDAP was compiled using 5.1.25, and the libs were updated to 5.1.29.
OpenLDAP *must* be recompiled against 5.1.29 as well in that case. If that
is done, then everything will move along happily.

This is by design because Oracle/Sleepycat has made API changes in patch
level releases before. back-hdb/bdb *must* be compiled against the exact
BDB library version they are linked to. In this case, the patch level does
matter.



Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Replies Reply to this message
#2 Quanah Gibson-Mount
December 12th, 2011 - 04:50 pm ET | Report spam
wrote:

Package: slapd
Version: 2.4.25-4+b1
Severity: important

Dear Maintainer,

I think that the openldap package was not compiled with the last
version :
bdb_back_initialize: BDB library version mismatch: expected Berkeley DB
5.1.25: (January 28, 2011) got Berkeley DB 5.1.29: (October 25, 2011).
slapd stopped.



Actually this indicates that OpenLDAP was recompiled with the latest BDB
version (5.1.29). It is complaining about the fact that your database was
created using the 5.1.25 version, and thus it refuses to start.

The correct behavior on Debian's part is to export the database(s) prior to
updating the BDB library via slapcat, and then reimport it via slapadd post
upgrade. OpenLDAP is working as designed.



Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Replies Reply to this message
#3 Julien Cristau
December 12th, 2011 - 05:00 pm ET | Report spam
On Mon, Dec 12, 2011 at 13:35:50 -0800, Quanah Gibson-Mount wrote:

OpenLDAP was compiled using 5.1.25, and the libs were updated to
5.1.29. OpenLDAP *must* be recompiled against 5.1.29 as well in that
case. If that is done, then everything will move along happily.

This is by design because Oracle/Sleepycat has made API changes in
patch level releases before. back-hdb/bdb *must* be compiled
against the exact BDB library version they are linked to. In this
case, the patch level does matter.



If bdb breaks ABI then it needs to bump SONAME. If it doesn't then
apps compiled against an earlier version must still work. A check for
the patchlevel version is just broken.

Cheers,
Julien



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
Replies Reply to this message
#4 Quanah Gibson-Mount
December 12th, 2011 - 05:10 pm ET | Report spam
wrote:

On Mon, Dec 12, 2011 at 13:35:50 -0800, Quanah Gibson-Mount wrote:

OpenLDAP was compiled using 5.1.25, and the libs were updated to
5.1.29. OpenLDAP *must* be recompiled against 5.1.29 as well in that
case. If that is done, then everything will move along happily.

This is by design because Oracle/Sleepycat has made API changes in
patch level releases before. back-hdb/bdb *must* be compiled
against the exact BDB library version they are linked to. In this
case, the patch level does matter.



If bdb breaks ABI then it needs to bump SONAME. If it doesn't then
apps compiled against an earlier version must still work. A check for
the patchlevel version is just broken.



Feel free to take that up with Oracle. ;) Until they fix their development
practices, the OpenLDAP behavior remains.



Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact
email Follow the discussion Replies Reply to this message
Help Create a new topicReplies Make a reply
Search Make your own search