[Pkg-openldap-devel] Bug#651333: slapd: fails to start, requires exact version of Berkeley DB
Antonio Terceiro
terceiro at debian.org
Wed Dec 7 20:39:00 UTC 2011
Package: slapd
Version: 2.4.25-4+b1
Severity: grave
Justification: renders package unusable
$ LANG=C sudo apt-get install slapd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
ruby-activeldap ruby-activerecord libldap-ruby1.8 ruby-gettext-activerecord libmozjs7d libxalan2-java-gcj
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
slapd
0 upgraded, 1 newly installed, 0 to remove and 25 not upgraded.
Need to get 0 B/1682 kB of archives.
After this operation, 3951 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package slapd.
(Reading database ... 247019 files and directories currently installed.)
Unpacking slapd (from .../slapd_2.4.25-4+b1_amd64.deb) ...
Processing triggers for man-db ...
Setting up slapd (2.4.25-4+b1) ...
Creating initial configuration... Loading the initial configuration from the ldif file () failed with
the following error while running slapadd:
hdb_back_initialize: BDB library version mismatch: expected Berkeley DB 5.1.25: (January 28, 2011), got Berkeley DB 5.1.29: (October 25, 2011)
backend_add: initialization for type "hdb" failed
olcBackend: value #0: <olcBackend> failed init (hdb)!
slapadd: could not add entry dn="olcBackend={0}hdb,cn=config" (line=1047):
dpkg: error processing slapd (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
slapd
E: Sub-process /usr/bin/dpkg returned an error code (1)
This will happen whenever a new version of Berkeley DB is uploaded. When slapd
is already installed and then libdb5.1 is upgraded, it just fails to start.
I am rebuilding from source to confirm that it "fixes" the problem, but it
would be nice if slapd didn't check for such a specific version. Testing for
the soname should be enough.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (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-21
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
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
-- debconf information:
slapd/password_mismatch:
slapd/invalid_config: true
shared/organization: nodomain
slapd/upgrade_slapcat_failure:
slapd/backend: HDB
slapd/dump_database: when needed
slapd/allow_ldap_v2: false
slapd/no_configuration: false
slapd/move_old_database: true
slapd/dump_database_destdir: /var/backups/slapd-VERSION
slapd/purge_database: false
slapd/domain: nodomain
--
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-openldap-devel/attachments/20111207/07862b18/attachment.pgp>
More information about the Pkg-openldap-devel
mailing list