Hi,

We are using the following:
Red Hat 2.4.9-e.24smp
OpenLDAP 2.1.29
Berkeley DB 4.1.24

Now and then openLDAP seems to hang while using 100% of CPU-time.

We can't find the needle.

output of db_stat:


250 Last allocated locker ID.
2147M Current maximum unused locker ID.
9 Number of lock modes.
1000 Maximum number of locks possible.
1000 Maximum number of lockers possible.
1000 Maximum number of lock objects possible.
48 Number of current locks.
114 Maximum number of locks at any one time.
140 Number of current lockers.
140 Maximum number of lockers at any one time.
21 Number of current lock objects.
95 Maximum number of lock objects at any one time.
421M Total number of locks requested.
1399337 Total number of locks released.
420M Total number of lock requests failing because DB_LOCK_NOWAIT
was set.
5 Total number of locks not immediately available due to
conflicts.
0 Number of deadlocks.
0 Lock timeout value.
0 Number of locks that have timed out.
0 Transaction timeout value.
0 Number of transactions that have timed out.
360KB The size of the lock region..
56352 The number of region locks granted after waiting.
422M The number of region locks granted without waiting.

The only other not common messages in openldap.log during the "hanging"
are "deferring operation".


Someone a suggestion what to do?


Best Regards,

Koert Gielen

koert gielen@bt com <koert.gielen (AT) bt (DOT) com> writes:

OpenLDAP 2.1 is historic. OpenLDAP 2.2 will soon be historic as well.

I advise upgrading to the latest stable release (OpenLDAP 2.3) and using
BDB 4.2.52 + patches.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

O.K.

Seems logical to me but I am also curious about the cause of the
problem.

Everything went well during a couple of years and now we suddenly have
this problem.

Also, nothing has been changed in the environment (no new hardware, no
OS-changes).

Koert.