[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: slapd stuck in sched_yield() call
--On Thursday, January 06, 2005 3:21 PM -0500 Misty Stanley-Jones
<misty@borkholder.com> wrote:
Hi all,
I've got an openLDAP read-only replica running on a server, and I noticed
today that it is using 90-95% of the CPU and it is looping in
sched_yield() system call (according the strace). It really should not
be doing anything as no changes are being made to the master LDAP
repository at all. Could this be a bug? I am running 2.2.6 (the latest
RPM from SUSE) on this system. As it is only a failover system I'd
rather have an easy-to-manage RPM than the latest and greatest. But
maybe this is a known bug that I am running into? It would only concern
me because it seems to be pegging the CPU.
OpenLDAP 2.2.6 was a very buggy release. The best release to run is
OpenLDAP 2.2.20, especially because of the fixes that went into 2.2.18,
2.2.19, and 2.2.20 that closed out some long standing bugs. I understand
that you may not want the latest and greatest, but you *will* experience a
number of problems with 2.2.6.
--Quanah
--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
"These censorship operations against schools and libraries are stronger
than ever in the present religio-political climate. They often focus on
fantasy and sf books, which foster that deadly enemy to bigotry and blind
faith, the imagination." -- Ursula K. Le Guin