Hi Martin, On Sun, Jun 05, 2005 at 10:54:24PM +0200, Martin Bammer wrote: > syslog: > Jun 5 22:22:40 bender slapd[4964]: slapd init: initiated server. > Jun 5 22:22:40 bender slapd[4964]: slap_sasl_init: initialized! > Jun 5 22:22:40 bender slapd[4964]: >>> dnNormalize: <cn=Subschema> > Jun 5 22:22:40 bender slapd[4964]: <<< dnNormalize: <cn=subschema> > > gdb-output: > [EMAIL PROTECTED]:~# gdb slapd -d 1 -s 1
> backend_startup: starting "dc=blahblubb,dc=com" > bdb_db_open: only one
> suffix allowed
> backend_startup: bi_db_open failed! (-1)
> slapd shutdown: initiated
> ====> bdb_cache_release_all
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1212040608 (LWP 4964)]
> 0xb7ab0b8f in bdb_bt_compare () from /usr/lib/ldap/back_bdb.so
> (gdb) bt
> #0 0xb7ab0b8f in bdb_bt_compare () from /usr/lib/ldap/back_bdb.so
> #1 0x0806dae8 in backend_shutdown ()
> #2 0x08055854 in main ()
There is a point in this report - it seems like an error return is not
checked here. But the whole problem is easier to find with the
configuration files.
In this case you seem to have two suffix directives inside a database
definition which is not supported with the BDB backend and most likely a
mistake anyway. I can reproduce the problem with about the same trace
by breaking my config like that.
OTOH I don't like people who just dump a lot of less helpful debugging
output without any description at the maintainer and claim that the
package is unusable. Immediately segfaults is a bit extreme as the
default install will not segfault. It would be helpful to describe the
circumstances.
Please don't just offload your problems on the maintainer without some
hints.
Thanks
Torsten
signature.asc
Description: Digital signature
