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

problem with openldap-2.0.27 - unsupported btree version 9


we're running fedora core 3 and openldap-2.0.27 (i can't upgrade due to limitations in the design of our underlying application). we are working with an official fedora-rpm-installation. when i try to initialize the database using a ldif-file, i am running into trouble (ldbm => unsupported btree version: 9).

# this is the contents of the ldif-file (init.ldif):
# (all real values have been changed to example.com)
dn: dc=example, dc=com
objectClass: organization
o: example.com

# the command i'm trying to use:
$ ldapadd -x -D "uid=admin.example.com,ou=system, dc=example, dc=com" -W -f init.ldif

# and its result:
adding new entry "dc=example, dc=com"
ldap_add: Operations error

ldif_record() = 1

# extract from log
Feb 3 17:06:52 www slapd[9830]: ldbm: ==> dn2id.dbb: unsupported btree version: 9
Feb 3 17:06:53 www last message repeated 2 times

# perhaps the following information about the system may help you:

$ rpm -qa | grep ldap

$ rpm -qa | grep apr

$ ls -l /var/lib/ldap -rw------- 1 ldap ldap 8192 12. Jan 21:38 dn2id.dbb -rw------- 1 root root 8192 3. Feb 15:44 id2entry.dbb -rw------- 1 root root 8192 3. Feb 15:44 nextid.dbb $ db_dump dn2id.dbb VERSION=3 format=bytevalue type=btree db_pagesize=4096 HEADER=END DATA=END $ db_dump id2entry.dbb VERSION=3 format=bytevalue type=btree db_pagesize=4096 HEADER=END DATA=END $ db_dump nextid.dbb VERSION=3 format=bytevalue type=btree db_pagesize=4096 HEADER=END ffffffff 05000000 DATA=END

# the contents of slapd.conf
$ cat /etc/openldap/slapd.conf
# $OpenLDAP: pkg/ldap/servers/slapd/slapd.conf,v 2001/09/27 20:00:31 kurt Exp $
# See slapd.conf(5) for details on configuration options.
# This file should NOT be world readable.
include /etc/openldap/schema/core.schema
include /etc/openldap/schema/cosine.schema
include /etc/openldap/schema/inetorgperson.schema
include /etc/openldap/schema/nis.schema
include /etc/openldap/schema/redhat/rfc822-MailMember.schema
include /etc/openldap/schema/redhat/autofs.schema
include /etc/openldap/schema/redhat/kerberosobject.schema
include /etc/openldap/schema/krb5-kdc.schema
include /etc/openldap/schema/samba.schema
include /etc/openldap/schema/outlook.schema

schemacheck     off

# Define global ACLs to disable default read access.

# Do not enable referrals until AFTER you have a working directory
# service AND an understanding of referrals.
#referral       ldap://root.openldap.org

pidfile         /var/run/slapd.pid
argsfile        /var/run/slapd.args

# Create a replication log in /var/lib/ldap for use by slurpd.
#replogfile     /var/lib/ldap/master-slapd.replog

# Load dynamic backend modules:
# modulepath    /usr/sbin/openldap
# moduleload    back_ldap.la
# moduleload    back_ldbm.la
# moduleload    back_passwd.la
# moduleload    back_shell.la

TLSCertificateFile      /etc/openldap/server.pem
TLSCertificateKeyFile   /etc/openldap/server.pem
#TLSCACertificateFile    /etc/openldap/server.pem

sasl-realm              EXAMPLE.COM
sasl-host               kerberos.example.com

loglevel 2048 database ldbm #dbcachenowsync readonly off directory /var/lib/ldap lastmod on #include /etc/openldap/slapd.access

# performance
index                   objectClass             eq
index                   default                 pres,eq
index                   uidNumber               pres,eq
index                   uid                     pres,eq,sub
index                   cn                      pres,eq,sub
cachesize               10000
dbcachesize             1000000

suffix "dc=example, dc=com"
rootdn "uid=admin.example.com, ou=system, dc=example, dc=com"
#rootdn "cn=Manager, dc=example, dc=com"
rootpw {KERBEROS}admin.example.com@EXAMPLE.COM

i suppose that is some problem with the underlying sleepycat, isn't it? should we compile openldap by hand and/or add some libraries?
if you need more information regarding the system, please don't hestitate to ask for it. i will try to answer any serious inquiry. nor the faq-o-matic on the openldap site, nor google, nor any newsgroup or list-archive provide help for a similar error message. well, at least i haven't found something that was helpful to me. ;) perhaps someone of you guys can help us out. your support would be highly appreciated!

thanks in advance.

christian stottmeister
http://www.stottmeister.com - http://www.mainframe8.com