High CPU slapd process and Open Directory Certificate

I'm noticing the exact same issue here. The server running the OD master suffers from extreme lagging due to "slapd" higging the CPU.

We've got a Comodo Certificate but Open Directory Service will not accept it. So I made a self signed certificate and Open Directory accepted that. After some time CPU load starts to build up but as soon as I select "None" certificate for Open Directory Service the CPU load drops instantly.

It might well be that the "slapd" process is just being restarted upon certificate change and that the process suffers from a bug or memory leak wich is totally unrelated to certificates.

I don't feel like restarting "slapd" on an hourly basis. Where would I start asking Apples assistance for an issue like this?

Bump, same issue here. I've tried all of the easy and extreme stuff, including a complete rebuild of the master and replica. I've even fiddled around with automatic restarts of the dirserv through cron, which seem to correct the CPU usage ~50% of the time.

My company recently moved to a pair of OS X server machines at our colo facility and I'm pretty shocked at how poorly supported and QA'ed this product really is. Microsoft, Novell, etc. would never stand for this.

Mac Mini Server with Mavericks 10.9.2 and Server 3.0.3

I also saw this today on a Replica OD. Had high CPU caused by slapd process.

Changed the Certificate to none and the slapd process falls to zero then I re-enabled the certificate.

Seems to be running without an issue for now. Will report if it comes back.

I found a bug that might be related. After trying to change a users password through terminal, the slapd process went sky high. To try this out for yourself enter the following command in terminal:

passwd

Then type the users old password followed by the new password twice. When hitting enter after the second password an error occurs in terminal. The slapd process starts going hayward (98% - 150%) right after that.

Attached a screenshot from right after this moment.

! Please note that in my case this user could not log into ssh or any other service anymore. Probably because the password save went wrong in combination with OD. To fix things, first quit the slapd process then go into Server App and change the user password by right-clicking on the user and select "Reset Password" from the contextual menu. Access to services was restored right away and slapd process load remained normal (<1%).

Can anyone confirm this?

Follow-on to the previous mail.

By the next day, slapd was taking all of the available cycles.

There is a bug in slapd that Apple needs to fix!

This bug has been going on for years now... BTW, Just keep an eye on your certificate's expiration date. Once it is valid for less than 30 days slapd is going nuts. I have renewed mine, and this thing went silent right away.