I had this same problem, turned out that one of our analysts had a bad piece of code that was constantly querying the directory server for a username and password... Aaron -----Original Message----- From: fedora-directory-users-bounces(a)redhat.com [mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Renato Ribeiro da Silva Sent: Friday, January 26, 2007 7:18 AM To: fedora-directory-users Subject: [Fedora-directory-users] CPU utilization I'm having questions about CPU utilization of Directory Server. The process ns-slapd take 99.9% of CPU almost all the time. Is there any way to know why this is happening? Any performance counter ( DS Console ) can show me the answer ? Is is possible to know the apps that are using the Directory in this moment ? Best Regards, Renato -- Fedora-directory-users mailing list Fedora-directory-users(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users Confidentiality Notice: The information contained in this electronic message is intended for the exclusive use of the individual or entity named above and may contain privileged or confidential information. If the reader of this message is not the intended recipient or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that dissemination, distribution or copying of this information is prohibited. If you have received this communication in error, please notify the sender immediately by telephone and destroy the copies you received.

The best way to handle performance issues is look in the acccess log for notes=U. These are unindexed searches. Its amazing to add the index and then watch the processor move from 99% to 0% thats what happened with one of our applications. It is definately a good idea to make different usernames for you different applications. If you give each application a different login it later allows you to go back and write individual ACI's. If all your applications share the same login you will eventually have to move all applications to a different user. Here is a question for all. Does anyone know of a log tool specifically for LDAP logs? I think there are big possibilites for something like this. Edward On 1/26/07, David Boreham <david_list(a)boreham.org&gt; wrote:

Eddie C wrote: bin/slapd/admin/bin/logconv.pl can help diagnose some problems like this.