I'm running OpenLDAP 2.2.6 on SuSE 9.1 on a dual-Xeon Intel server. It
is set up to provide user, group, netgroup, and automount data. I do a
fair amount of writing on occasion when I repopulate some of these OUs
using migration scripts to pull in updated data from a production NIS
server. None of the OUs have more than about 1,000 entries. I've been
running it about a month and twice I've had BDB corruption in which the
server stopped responding or could only serve up a portion of its
entries without hanging. Restarting the server had no beneficial
effect. The first time, I just shut down, wiped the LDAP database
directory, restarted, and slapadd'ed in a back-up LDIF. Now that it's
happened the second time, I've performed the following to try to get to
the bottom of it:

# cd /var/lib/ldap; db_recover
(This appeared to resolve the problem, though I still plan to wipe it
out and restore from a back-up LDIF)

------------------------------
------------------------------

Has anyone come across a situation like this before and/or have any tips
on how I might permanently avoid the condition in the future? On less
well-used software I'd expect a possible reentrancy issue, but think
that's unlikely to be the case here. If it's a known issue with there
is a patch, I'd be happy to test it.