10.9.5 update causing high CPU load when connected to Active Directory

[Mr Rabbit]

Already have confirmation from Apple that this is a known issue and a fix is in the works, until that fix rolls out though I'm wondering if anyone in the community has found any workarounds.

Our office environment consists of roughly 200 Macs connecting to Active Directory & Open Directory (Golden Triangle). Several have now updated to 10.9.5 following the release last week. Those that have updated are seeing the opendirectoryd process continually consume more than 300% of CPU power, which leads to incredibly long logins (5~ minutes to login if it doesn't time out), authentication issues when trying to access network services, fans running at high constantly and overall slow performance.

So far the only workarounds we've found are to either unbind from Active Directory and/or disconnect the network cable.

Anyone else run into this and find a better workaround yet?

 

[Mr Rabbit]

Found a workaround today.

Noticed that the issue only seem to be affecting Macs that had been migrated up from 10.7 or earlier. Newer Macs that shipped with 10.8 or 10.9 seemed to be unaffected.

The only difference I could find was that their search policies had one variance in the available directory domain options. Removing "/Active Directory/domain-name", which isn't even an option in 10.8 and above, then disconnecting and reconnecting from the network seems to fix it.

Hoping to see a supplemental update from Apple to address this soon. Most of our 200 Macs likely have these settings. Anyone know of a way to script a fix so I don't have to manually update/fix each one?

Screen shots attached showing the differences.

 

[TsunamiTheClown]

Well its more than 2 months later and I can vouch that 10.9.5 is still causing opendirectoryd to regularly consume more than half of the available CPU each day when I log in. The only way I have found to stop that process is with a sigkill.

I have taken a look at the Search Policy in Directory Utility and have tried your fix Mr. Rabbit. I'll update you if it is a long term solution. Up till today I have just been killing the offending process each day. I would really love for Apple to fix this issue, but they are working on Virtual Reality i suppose. :T

I have also noticed that some network mounts are also causing the activedirectoryd process to go haywire, so for now I have had to stop auto mounting network resources.