Macbook Pro got slow after upgrade to 10.9.5 (Mavericks)

Same issue here. I've now upgraded four AD-bound Macs from 10.9.4 to 10.9.5, and all but one is now stable. That's the good news.

The bad news is that the only way I've succeeded in upgrading without issues is by unbinding the Mac from Active Directory *BEFORE* running the Combo Updater. I can then re-bind the machine after the upgrade has completed (and after a reboot, of course). It doesn't seem to matter how I unbind and re-bind (using dsconfigad with dscl in a a script or interactively) or how I apply the update (opening the package or running "sudo installer" from the command line). The results have been the same; if I don't unbind first, then opendirectoryd gobbles up all the CPU cycles, and my next login attempt times out.

Same here on a MacBookPro8,1 in an Active Directory Domain provided by Windows Server 2008 R2. Unbinding from the domain or removing network connection solves it temporary but after binding again the high CPU usage by opendirectoryd appears again.

Did you try the suggestion of bmiller-tam?

To further complicate matters, I restored back to 10.9.4, and now I can't bind to AD either (I get "Authentication server could not be contacted. (5200)" error). Truly frustrating.

unbind from domain, re-install 10.9.5 and bind after

That's what I'm suggesting. I have no idea whether it will work, but you shouldn't be any worse off than you are now, as long as you back up.

Linc Davis wrote:

unbind from domain, re-install 10.9.5 and bind after

That's what I'm suggesting. I have no idea whether it will work, but you shouldn't be any worse off than you are now, as long as you back up.

Unfortunatly that does NOT work. SO I guess I have to either do a clean install or wait for a fix from Apple?

I ended up filing a bug report with apple on 10.9.5 I've submitted my sysdiagnose file (cmd+ctrl+opt+shift + period) to provide feedback on the run away process. I've since restored 10.9.4 from time machine. filing a bug report and capturing the sysdiagnose file and submitting it to apple maybe helpful.

See this discussion for a possible fix, which has apparently worked for some.

Found a solution, at least for my system! Apparently, wrong disk permissions were causing problems on my system. I write "apparently" as I did some other tests in between which might have caused changes. But the following solution should be given a try:

1. If the system is already too slow to logon, remove the network cable or switch off wireless.
2. Unbind from the Active Directory Domain: Mac OS X 10.6 Server Admin: Unbinding from the Active Directory Server
3. Use Disk Utility to repair file permissions on the system disk. http://www.cnet.com/how-to/repair-disk-permissions-to-speed-up-your-mac/
4. Bind again to the Active Director Domain.

If that did not helped. Active logging for opendirectoryd as described in http://training.apple.com/pdf/wp_integrating_active_directory_mav.pdf with the following command in Terminal.app:

odutil set log debug

Then take a look what is happening:

tail -f /var/log/opendirectoryd.log

Afterwards, switch logging back to normal mode:

odutil set log default

Same issue here. Details just in case it helps someone:

iMac 12,2

Bound to Active Directory only

Update from 10.9.4 to 10.9.5 and opendirectoryd process goes 300+% on CPU after update restart once network login is "live" (i.e. "Other" user login Icon appears on login screen)

Steps taken

• Unplug network cable (WiFi already Off) and CPU immediately drops to normal
• Unbind from Active Directory via GUI as per Linc Davis
• Plug network cable back in and all works Ok (even logging in and out as a network user with local profile as customer has mobile profiles enabled)
• Attempted to find .plist files as per GregD7 but had issues with permissions and limited time so did not pursue any further as I had a temporary work around (unbinding from AD)
• Repaired disk permissions as per isenberg but this did not work for me (see next step)
• Bind to AD again and CPU immediately goes 300+% for opendirectoryd
• Unbind and it drops to normal again immediately

I have left the machine unbound from AD and will not update other machines to 10.9.5 until I can test and confirm work around on customer's system. At least I can reproduce the issue......😐

Darren, is your opendirectoryd.log showing some errors? How to activate the log is shown in my previous message.

In my case, repairing permissions doesn’t bring any positive results.

Hi everybody,

I had the exact same problem on my mid-2011 MacBook Air, right after 10.9.5 update.

But my company's SysAdmin found a solution! I'm not tech-savvy enough to explain what he did in details but I hope my experience might help.

What he did:

• Go to Users & Groups / Login Options
• Network Account Server => Edit
• Select account and open Directory Utility
• From Directory Utility, go to the Search Policy tab and remove any Directoy Domain you don't need.

From what I understood, there was a kind of loop in there creating endless requests, leading to high CPU usage (up to 330%) and network overload.

Hope it helped a little