[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: OpenLDAP 2.2 crashes with BDB but not LDBM
Quanah Gibson-Mount wrote:
--On Friday, June 25, 2004 4:30 PM -0500 Jason Joines
<joines@bus.okstate.edu> wrote:
We're preparing to upgrade a bunch of servers with
OpenLDAP 2.0 on SuSE 8.0 and 8.1 to OpenLDAP 2.2 on SuSE 9.1. I finally
got all my LDIFs exported from the 2.0 directory via slapcat
straightened out to comply with the stricter schema checking of 2.2, new
Samba 3 schema, etc, and got it into the 2.2 directory on a test server
via slapadd. Linux authentication works fine. However, if I'm using BDB
as the database, any add, delete, or modify operation crashes OpenLDAP.
I can't use ldapadd to add a user, ldappasswd to change a password, or
ldapdelete to delete a user without it crashing. If I change the backend
to LDBM, everything works fine.
What version of BDB are you using? Does it have the applicable patches?
What does your DB_CONFIG file have in it?
What is the database definition of your BDB section say?
What does gdb say?
What does debug -1 output show for slapd?
--Quanah
--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
It's what came with SuSE Linux 9.1, looks like:
Berkeley DB 4.2.52
I'm not sure about patches except that the entire system has all the
patches related to installed software that SuSE has supplied.
DB_CONFIG has:
set_cachesize 0 15000000 1
set_lg_bsize 2097152
OpenLDAP 2.2.6
#####################################################
# bdb database definitions
#####################################################
database bdb
checkpoint 1024 5
cachesize 10000
database ldbm
suffix "dc=my,dc=domain,dc=org"
rootdn "cn=Manager,dc=my,dc=domain,dc=org"
rootpw {MD5}yCLBtjhT7Sc7iWh6xQX5+g==
directory /var/lib/ldap
# Indices to maintain
index objectClass,userPassword eq
index cn,sn,mail,uid pres,eq,approx,sub
There was nothing in the log.
I just changed everything back to bdb, ran slapd in debug 1 and tried
again. I could not reproduce the problem running in debug mode. I
restarted in daemon mode and still can't reproduce the problem. It
happened over and over Thursday and Friday. My only guess at this point
is that I may have copied the DB_CONFIG file to the wrong location at
some point when I was emptying and rebuilding the directory to get my
ldif's straightened out.
Jason Joines
=================================