Viewing Historical/5019
Full headers

Major security issue: yes  no

Notes:
back-ldbm is deprecated, won't fix
Notification:

Date: Thu, 14 Jun 2007 20:59:41 GMT
From: asedlack@mailfoundry.com
To: openldap-its@OpenLDAP.org
Subject: slapd: ldbm/gdbm, cache.c core dump

Full_Name: Aron Sedlack
Version: 2.3.35
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (66.18.18.14)


Platform: Linux, OpenLDAP-2.3.35
Compiled with: ./configure --enable-dynamic --enable-wrappers --enable-bdb=no
--enable-hdb=no --enable-ldbm --enable-ldbm-api=gdbm --with-threads --with-tls
--with-threads=no
gcc version 3.3.4, gdbm 1.8.3, OpenSSL 0.9.8e

slapd core dumps with a corrupted stack, SIGABRT.
slapd: cache.c:111: cache_return_entry_rw: Assertion `e->e_private != (( void
*)0)' failed..

Happens every time ldif is loaded...
$ ldapmodify -a -f ./mf.ldif -D "cn=Root,dc=mf" -w secret
adding new entry "dc=mf"

adding new entry "dc=iana,dc=mf"
ldap_result: Can't contact LDAP server (-1)

Reply 1

From: Pierangelo Masarati <openldap-its@OpenLDAP.org>
To: asedlack@mailfoundry.com
Subject: Re: slapd: ldbm/gdbm, cache.c core dump (ITS#5019)
Date: Thu Jun 14 21:12:42 2007

back-ldbm is deprecated and will be abandoned since OpenLDAP 2.4.  It is a very
bad idea to use it with OpenLDAP 2.3 (and with OpenLDAP 2.2, and 2.1, ...).  It
is very unlikely that anyone spends time in fixing dead code.  Use back-bdb or
back-hdb instead for better performances and incredibly higher reliability.

p.

Followup 1

Date: Thu, 14 Jun 2007 15:15:10 -0700
From: Howard Chu <hyc@symas.com>
To: asedlack@mailfoundry.com
CC: openldap-its@openldap.org
Subject: Re: (ITS#5019) slapd: ldbm/gdbm, cache.c core dump

asedlack@mailfoundry.com wrote:
> Full_Name: Aron Sedlack
> Version: 2.3.35
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (66.18.18.14)
> 
> 
> Platform: Linux, OpenLDAP-2.3.35
> Compiled with: ./configure --enable-dynamic --enable-wrappers
--enable-bdb=no
> --enable-hdb=no --enable-ldbm --enable-ldbm-api=gdbm --with-threads
--with-tls
> --with-threads=no
> gcc version 3.3.4, gdbm 1.8.3, OpenSSL 0.9.8e
> 
> slapd core dumps with a corrupted stack, SIGABRT.
> slapd: cache.c:111: cache_return_entry_rw: Assertion `e->e_private != ((
void
> *)0)' failed..
> 
> Happens every time ldif is loaded...
> $ ldapmodify -a -f ./mf.ldif -D "cn=Root,dc=mf" -w secret
> adding new entry "dc=mf"
> 
> adding new entry "dc=iana,dc=mf"
> ldap_result: Can't contact LDAP server (-1)

1) ldbm is deprecated, don't use it.

2) if you insist on using it, get a debug stack trace for the abort

3) note that ldbm is still tested regularly in the 2.3 builds, and no one else 
has reported this occurrence, so there's probably something odd in your 
configuration. Providing your slapd.conf might help.

But the ldbm code has been removed for 2.4; support for it is disappearing fast.

-- 
   -- Howard Chu
   Chief Architect, Symas Corp.  http://www.symas.com
   Director, Highland Sun        http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP     http://www.openldap.org/project/

Followup 2

Date: Thu, 14 Jun 2007 15:16:30 -0700
From: Quanah Gibson-Mount <quanah@zimbra.com>
To: asedlack@mailfoundry.com, openldap-its@openldap.org
Subject: Re: (ITS#5019) slapd: ldbm/gdbm, cache.c core dump

--On Thursday, June 14, 2007 8:59 PM +0000 asedlack@mailfoundry.com wrote:

> Full_Name: Aron Sedlack
> Version: 2.3.35
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (66.18.18.14)
>

LDBM is deprecated, and has been removed from the source tree.  Bugs 
against LDBM will not be fixed, because of its inherent flaws.  Upgrade 
your configuration to use one of the supported database mechanisms, 
back-bdb or back-hdb. :)

--Quanah


--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration