Your message dated Fri, 18 Aug 2006 13:36:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [Pkg-openldap-devel] Bug#383676: slapd 2.3.25-1 fails to
start, undefined symbol: ldap_pvt_sasl_mutex_new
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: slapd
Version 2.3.25-1
slapd fails to start:
ldap2:~# /etc/init.d/slapd start
Starting OpenLDAP: slapd - failed:
/usr/sbin/slapd: symbol lookup error: /usr/sbin/slapd: undefined symbol:
ldap_pvt_sasl_mutex_new
ldap2:~# slapd -V
@(#) $OpenLDAP: slapd 2.3.25 (Aug 3 2006 23:09:08) $
@pulsar:/home/torsten/packages/openldap2.3-2.3.25/debian/build/servers/slapd
slapd: symbol lookup error: slapd: undefined symbol: ldap_pvt_sasl_mutex_new
Doesn't really matter if I have a valid slapd.conf or not.
ldap2:~# ldd `which slapd`
linux-gate.so.1 => (0xffffe000)
libldap_r-2.3.so.0 => /usr/local/lib/libldap_r-2.3.so.0 (0xb7f81000)
liblber-2.3.so.0 => /usr/local/lib/liblber-2.3.so.0 (0xb7f75000)
libiodbc.so.2 => /usr/lib/libiodbc.so.2 (0xb7f2b000)
libslp.so.1 => /usr/lib/libslp.so.1 (0xb7f1c000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xb7f07000)
libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0xb7ec8000)
libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb7d8e000)
libcrypt.so.1 => /lib/tls/libcrypt.so.1 (0xb7d60000)
libresolv.so.2 => /lib/tls/libresolv.so.2 (0xb7d4c000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7d3a000)
libltdl.so.3 => /usr/local/lib/libltdl.so.3 (0xb7d34000)
libwrap.so.0 => /lib/libwrap.so.0 (0xb7d2c000)
libc.so.6 => /lib/tls/libc.so.6 (0xb7bf4000)
libdl.so.2 => /lib/tls/libdl.so.2 (0xb7bf0000)
libnsl.so.1 => /lib/tls/libnsl.so.1 (0xb7bd9000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7bc5000)
/lib/ld-linux.so.2 (0xb7fbf000)
ldap2:~# dpkg -l libc6 libdb4.2 libiodbc2 libldap-2.3-0 libltdl3 libperl5.8 \
libsasl2 libslp1 libssl0.9.8 libwrap0 coreutils psmisc perl \
libmime-base64-perl | grep -e '^ii' | awk '{print $2 " = " $3}'
coreutils = 5.96-5 libc6 = 2.3.6-15 libdb4.2 = 4.2.52-23.1
libiodbc2 = 3.52.4-3
libldap-2.3-0 = 2.3.25-1
libltdl3 = 1.5.22-4
libperl5.8 = 5.8.8-6.1
libsasl2 = 2.1.19.dfsg1-0.2
libslp1 = 1.2.1-5
libssl0.9.8 = 0.9.8b-2
libwrap0 = 7.6.dbs-9
perl = 5.8.8-6.1
psmisc = 22.2-1
--
Michael Stella
CHARLEX d e s i g n + b u i l d
T 212.845.5849
--- End Message ---
--- Begin Message ---
On Fri, Aug 18, 2006 at 01:00:01PM -0400, Michael Stella wrote:
> libldap_r-2.3.so.0 => /usr/local/lib/libldap_r-2.3.so.0 (0xb7f81000)
Well, it's been established that this isn't a bug in the package, it's
caused by local libraries, so -- closing.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
