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

Re: OpenLDAP 2.1.12 problems with back-bdb ; slapd does not start

I also build my own packages from redhat <nalin@redhat.com> 2.1.3-4 srpm (didn't find any more uptodate packages officially from redhat !).
From what, which version (from scratch ?) did you create yours ?

For me it runs with no problem.

If you want you can get it from:
where there is openldap-2.1.11-1.src.rpm which include DB 4.1.25.NC and lots of openldap backends. there are also the binarie versions for redhat 8.0 at the same place .

Here's what my ldap directory contains:
[root@corbeau /var/lib/ldap/int]
#set the logfile size to 100MB.
#set_lg_max 104857600
#set the in-memory log buffer size
set_lg_bsize 204800
#temporary while we're slapadding the database
set_flags DB_TXN_NOSYNC
#set the (per db?) cachesize to 0GB + X bytes, split into N pieces of memory
set_cachesize 0 5120000 2
[root@corbeau /var/lib/ldap/int]
$ ls
cn.bdb __db.004 dn2id.bdb IntEPersInetServ.bdb log.0000000004 log.0000000008 sn.bdb
__db.001 __db.005 gidNumber.bdb log.0000000001 log.0000000005 log.0000000009 uid.bdb
__db.002 __db.006 givenName.bdb log.0000000002 log.0000000006 mail.bdb uidNumber.bdb
__db.003 DB_CONFIG id2entry.bdb log.0000000003 log.0000000007 objectClass.bdb

Hope it helps !

Markus Benning wrote:
I build my own RPMs and in my tests i used root to
start slapd.
Later it will run under the ldap account and group, but
for now i'm just testing arround with 2.1.

He creates only one file in the directory:
-rw-------    1 root     root        0 Jan 17 16:12 __db.001

zero bytes :-/

On Fri, Jan 17, 2003 at 04:54:18PM +0100, Jehan PROCACCIA wrote:

I had this kind of error message once ... it was only because my .ddb files (an directory /var/lib/ldap ) were'nt owned by the ldap account (slapd runs with the ldap username in redhat !)

But maybe your problem comes from something else ? just check that first !.

Markus Benning wrote:


i'm currently planing to update my LDAP Server from
version 2.0 to 2.1.
I build rpms for db-4.1.25 and openldap-2.1.12.
Distribution is Redhat 7.2.

The RPMs are compiled with the following options
on a Redhat 7.2 build system with installed development

../dist/configure \
      --prefix=/usr \
      --enable-shared --enable-static --enable-rpc \
      --enable-tcl --with-tcl=%{_libdir} \
      --enable-cxx --enable-test \

and OpenLDAP with following options:
./configure \
      --prefix=/usr \
      --libexecdir=/usr/sbin \
      --sysconfdir=/etc \
      --localstatedir=/var/opt \
      --enable-syslog \
      --enable-proctitle \
      --enable-local \
      --with-cyrus-sasl \
      --with-threads \
      --with-tls \
      --enable-slapd \
      --enable-aci \
      --enable-cleartext \
      --enable-crypt \
      --enable-dynamic \
      --enable-lmpasswd \
      --enable-spasswd \
      --enable-modules \
      --enable-bdb \
      --with-bdb-module=static \
      --enable-ldbm \
      --with-ldbm-api=berkeley \
      --enable-monitor \
      --with-monitor-module=dynamic \
      --enable-perl \
      --with-perl-module=dynamic \
      --enable-slurpd \
      --enable-shared=yes \
      --disable-sql \

On the build Host slapd runs.

But on the Target Systems it can't create the bdb database.
Here's the output of "slapd -d 256":

# slapd -d 256
bdb_initialize: Sleepycat Software: Berkeley DB 4.1.25: (December 19,
bdb_db_init: Initializing BDB database
bdb(dc=my-domain,dc=com): write: 0xbfffd830, 8192: Invalid argument
bdb_db_open: dbenv_open failed: Invalid argument (22)
backend_startup: bi_db_open(0) failed! (22)
bdb(dc=my-domain,dc=com): txn_checkpoint interface requires an
environment configured for the transaction subsystem
bdb_db_destroy: txn_checkpoint failed: Invalid argument (22)
slapd stopped.
connections_destroy: nothing to destroy.

What is an "environment configured for the transaction subsystem" ?

Ideas ?

Markus Benning