Your message dated Wed, 22 Feb 2006 22:40:35 +0100
with message-id <[EMAIL PROTECTED]>
and subject line slapd: ocasional 100% cpu usage on startup of slapd
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: slapd
Version: 2.1.17-1
Hi,
What I was afraid for and mentioned already in
http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg00179.html
appears to be a problem not only for SuSE, but for us as well.
My workstation/experimentation machine is running on ext3, and uses
nss-ldap for it's user management. It's a slave from our master directory.
I just upgraded it to slapd 2.1.17-1 and for testing purposes converted
the present directory to bdb (using slapadd from the backup ldif), and
when I updated an entry in the master directory, my slave one hung.
I noticed that only a few minutes later when I did a slapcat locally to
check the changed entry. Checking with top showed high memory usage by the
slapd processes as in the SuSE knowledge base article, etc, all similar
symptoms as I ran into before on a SuSE system.
Login or anything else which needs ldap lookups hang forever as well.
A ps output:
[EMAIL PROTECTED]:~$ ps aux | grep slap
root 16437 0.0 1.5 49636 3852 ? S 14:00 0:00 /usr/sbin/slapd
root 16438 0.0 1.5 49636 3852 ? S 14:00 0:00 /usr/sbin/slapd
root 16439 0.0 1.5 49636 3852 ? S 14:00 0:00 /usr/sbin/slapd
root 16441 25.2 1.5 49636 3852 ? R 14:00 2:14 /usr/sbin/slapd
root 16461 33.0 0.9 5932 2336 tty5 R 14:03 2:00 slapcat
root 16463 2.9 1.5 49636 3852 ? R 14:03 0:10 /usr/sbin/slapd
root 16464 23.8 1.5 49636 3852 ? R 14:03 1:24 /usr/sbin/slapd
I suspect the 4th slapd in that list is the one dealing with the replication
connection, and the first one which actually hangs. The 5th should be the
one from the slapcat, and the 6th from a login attempt.
I'll leave it to you to decide how to handle this in packages; whether to
make ldbm the default again or to add a question (probably a better
solution) with a warning or something else.
I will revert to ldbm myself now, but I suspect it'll be easily
reproducible when I go back to bdb so feel free to ask if you want me to
try something.
Regards,
Filip
--
"Sorry... my mind has a few bad sectors."
-- Ari Pollak
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Fixed upstream, and Sarge is released with 2.2.23 so I think this bug
can be closed.
Regards,
Matthijs Mohlmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD/NpT2n1ROIkXqbARAlnLAJ9q1quLuhCygAZCNSLWwUsrFmBFsACdHYw5
t/ilginiAgxxIbwfTjMrL54=
=8+YY
-----END PGP SIGNATURE-----
--- End Message ---
