michael(a)stroeder.com wrote:
This is a cryptographically signed message in MIME format.
--------------ms080100030105010600070605
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
A couple of days ago I had a hang with OpenLDAP 2.4.32 / back-hdb running=
on
Debian Squeeze, self-compiled against BDB 4.8.30. It seemed Database was
locked as restarting slapd of even rebooting OS did not help. Unfortunate=
ly I
had to bring up the system as fast as possible and could not examine the =
problem.
db_recover will always return the DB to a usable state and reset any DB locks.
(It completely deletes the lock region, so there cannot be any stale locks
after it runs.)
The system has only 200 entries and not much load yet. I had renamed
entr=
ies
with web2ldap when all 4 masters (4-way MMR) locked up one after the othe=
r.
So there seem to be lockup problems in 2.4.32.
The only way to know if you're seeing the same problem as the original poster
is if you provide db_stat -CA and gdb trace output, like the original poster did.
--
-- Howard Chu
CTO, Symas Corp.
http://www.symas.com
Director, Highland Sun
http://highlandsun.com/hyc/
Chief Architect, OpenLDAP
http://www.openldap.org/project/