[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#6012) segmentation fault triggered with slapcat

martin.konold@erfrakon.de wrote:
> Full_Name: Martin Konold
> Version: 2.4.15
> OS: Linux
> URL: http://www.erfrakon.de/konold/openldap-2.4.15.empty-db-segfault.patch
> Submission from: (NULL) (
> Previous versions of OpenLDAP could show a sig11 when doing slapcat (using bdb
> backend).
> The version 2.4.15 improved in this respect already though doing a slapcat with
> an emtpy db still results in a segmentation fault.
> The following small patch by andreas.mack at erfrakon.de resolves this issue
>     http://www.erfrakon.de/konold/openldap-2.4.15.empty-db-segfault.patch
> The patch is used by the Kolab Project in productive installations

What exactly do you mean by an empty db? I see:
ada:~/OD/o24/tests> rm testrun/db.1.a/*
ada:~/OD/o24/tests> ../servers/slapd/slapd -Tc -f testrun/slapd.1.conf
bdb_db_open: warning - no DB_CONFIG file found in directory 
/home/hyc/OD/o24/tests/testrun/db.1.a: (2).
Expect poor performance for suffix "dc=example,dc=com".
bdb_db_open: database "dc=example,dc=com": 
db_open(/home/hyc/OD/o24/tests/testrun/db.1.a/id2entry.bdb) failed: No such 
file or directory (2).
backend_startup_one: bi_db_open failed! (2)
slap_startup failed

Please provide steps to reproduce the segfault, thanks.
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/