[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: slapd high CPU usage



Angie Cao skrev, on 17-10-2007 00:58:

I am using default openldap-server-2.3.27-5 coming with red hat 5 and
I am using syncrep method to replicate with master ldap server. The
replication itself worked well, was able to replicate a large
database. but I have a severe problem that slapd process spikes high
CPU every few seconds. User time is about 85%. The whole server gets
very very slow.

Experience (years of) plus own testing with RHEL5 says: Do Not Use Red Hat's OpenLDAP, use Buchan Milnes'. My site's totally dependent on OpenLDAP on multiple servers, has no problems. Red Hat's OL is (presumably) patched to use the native BDB 4.3.29, whereas Buchan's has its own discrete patched 4.2.52. At least one developer on this list has written that the OL 2.3 source was deliberately written not to work with BDB 43, go figure.


http://staff.telkomsa.net/packages/

--Tonni

--


I turned slapd to debug level -1 and grep for error. The only error i got was:
-----------
-Oct 16 17:32:59 ldapserver slapd[3127]: => access_allowed: backend
default search access granted to "(anonymous)"
Oct 16 17:32:59 ldapserver slapd[3127]: <= test_filter 5
Oct 16 17:32:59 ldapserver slapd[3127]: <= test_filter_and 5
Oct 16 17:32:59 ldapserver slapd[3127]: <= test_filter 5
Oct 16 17:32:59 ldapserver slapd[3127]: bdb_search: 10555 does not match filter
Oct 16 17:32:56 ldapserver slapd[3127]: ber_get_next on fd 24 failed
errno=0 (Success)
Oct 16 17:32:59 ldapserver slapd[3127]: connection_read(24): input
error=-2 id=14, closing.

Oct 16 17:35:24 ldapserver slapd[3127]: connection_read(17): input
error=-2 id=32, closing.
Oct 16 17:35:29 ldapserver slapd[3127]: connection_read(18): input
error=-2 id=36, closing.
Oct 16 17:35:32 ldapserver slapd[3127]: connection_read(18): input
error=-2 id=37, closing.
----------
(I do not know if this is related with high CPU), there was no
particular messages in /var/log/message. I have 3.2GHz CPU and 2G
memory on this server.

Has anybody had the similar problem before? Can anyone advice what can
be done in order to troubleshoot further?

Thanks.

Angie



--
Tony Earnshaw
Email: tonni at hetnet dot nl