Vlasak

Q: Macbook Pro got slow after upgrade to 10.9.5 (Mavericks)

Hello,

 

I have updated my Mavericks system to the latest version released recently (10.9.5) and since then my system is much slower than it used to be (with side effect that fan is still active).

 

If I take a look into Activity Monitor, I can see that the process called opendirectoryd is consuming big percentage of CPU power (around 200%).

 

Looking into the console in system.log is giving me the following failure messages which are being displayed every 10 minutes (roughly):

 

Sep 18 17:12:38 VLAPE02mac1446 com.apple.launchd[1] (com.apple.opendirectoryd[1694]): Exited with code: 70

Sep 18 17:12:38 VLAPE02mac1446 automount[1700]: od_search: query failed: The daemon encountered an error processing request.

 

Do you have any idea what could be the problem?

MacBook Pro with Retina display, OS X Mavericks (10.9.5), 2 GHz Intel Core i7

Posted on Sep 18, 2014 8:44 AM

Close

Q: Macbook Pro got slow after upgrade to 10.9.5 (Mavericks)

  • All replies
  • Helpful answers

first Previous Page 3 of 4 last Next
  • by CedX,

    CedX CedX Sep 24, 2014 3:27 AM in response to Vlasak
    Level 1 (0 points)
    iCloud
    Sep 24, 2014 3:27 AM in response to Vlasak

    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

  • by DarrenChap,

    DarrenChap DarrenChap Sep 24, 2014 4:09 PM in response to isenberg
    Level 1 (0 points)
    Sep 24, 2014 4:09 PM in response to isenberg

    Isenberg, no I haven't activated or checked the opendirectoryd log as yet.  Need to physically go the the customer location so I can disconnect the network cable when the system "locks up".  Will hopefully get a chance to do that next week, customer is isolated from the problem at the moment so all good.  Will report back if I find anything.

  • by mcglow2,

    mcglow2 mcglow2 Sep 25, 2014 11:41 AM in response to Vlasak
    Level 1 (0 points)
    Sep 25, 2014 11:41 AM in response to Vlasak

    We experience this same problem on any mac joined to our Active Directory domain that was upgraded to 10.9.5 .  We were able to track it down to millions of connections per machine being made to the domain controllers Global Catalog port 3268. 

     

    FIXED:

    We were able to fix this problem by removing the AD Domain from the Search Policy -> Contacts in the Directory Utility .  After this the extra connections stopped and users could login in using their AD credentials again,

  • by bmiller-tam,

    bmiller-tam bmiller-tam Sep 25, 2014 12:28 PM in response to mcglow2
    Level 1 (0 points)
    Sep 25, 2014 12:28 PM in response to mcglow2

    Found the same thing here. On my test machine, I noticed it caused a problem when I bound with the ALL DOMAINS switch set to 'disable.'

     

    To unbind from the command line using SSH or ARD's UNIX command, it looks like you can use this (as root or with sudo):

     

    shortDomainName="yourdomainnamegoeshere"

    rm -rfdv /Library/Preferences/DirectoryService

    rm -rfdv /Library/Preferences/OpenDirectory

    rm -rfdv /var/db/dslocal/nodes/Default/config

    dscl /Search -delete / CSPSearchPath "/Active Directory/$shortDomainName"

    dscl /Search/Contacts -delete / CSPSearchPath "/Active Directory/$shortDomainName"

    dscl /Search -delete / CSPSearchPath "/Active Directory/$shortDomainName/All Domains"

    dscl /Search/Contacts -delete / CSPSearchPath "/Active Directory/$shortDomainName/All Domains"

    killall opendirectoryd

     

    For the shortDomainName variable, enter the short form of your AD domain name. For example, if your domain name is acme.com, use ACME.

  • by keithfromvirginia beach,

    keithfromvirginia beach keithfromvirginia beach Sep 30, 2014 7:57 AM in response to Vlasak
    Level 1 (20 points)
    Mac OS X
    Sep 30, 2014 7:57 AM in response to Vlasak

    I can confirm that the Search Policy settings (Authentication in my case) under the Directory Utility was the culprit. I did the SMC, PRAM, unbind and rebind, remove from Apple MDM and nothing fixed it until I went into Search Policy (Paths) and removed everything except Active Directory/DOMAIN/All Domains. After that change the issue was resolved and the user experienced normal CPU usage again.

  • by zioskit,

    zioskit zioskit Oct 2, 2014 1:09 PM in response to GregD7
    Level 1 (0 points)
    Oct 2, 2014 1:09 PM in response to GregD7

    I saw symptoms exactly as GregD7 describes.  I also followed the same steps to disjoin, clean the .plist file, and rejoin to my AD.  Symptoms re-appeared immediately after re-join was complete.  I then also observed quite a bit of traffic from opendirectoryd & NetBIOS processes directed at one of my DC's.  Looking through all the directory settings, I found what seemed to be an extra Directory Domain entry on the Directory Utility > Search Policy > Authentication listing.  The affected machine had 3 entries:

    1. /Local/Default
    2. /Active Directory/MYDOMAIN
    3. /Active Directory/MYDOMAIN/All Domains

    No other Mac I examined had the 2nd entry present.  I removed this entry from the affected machine and rebooted.  The issue has seemingly disappeared after that point.  Hope that helps other suffering from this issue.

  • by CantSalomeDown,

    CantSalomeDown CantSalomeDown Oct 3, 2014 9:03 AM in response to Vlasak
    Level 1 (1 points)
    Oct 3, 2014 9:03 AM in response to Vlasak

    FYI all the issue appears to have been resolved by Apple, not sure if I missed a communication, or if they haven't gotten around to closing out tickets submitted to AppleCare for this.

     

    Below is how I discovered it was no longer a problem:

     

    I was testing today with ARD's ability to update software on Macs in the environment today and I sent a unix command to two machines with 10.9.4 "softwareupdate -i -a"  to install all available updates.

     

    After restarting the machines they updated to 10.9.5, and I no longer see the previous issue.  There is no erroneous search policy anymore, and the OpenDirectory tool is no longer spiking.  No need to turn off wireless or unplug the network cable to be able to login anymore to be able to delete the search policy, everything is working fine on both macs.

  • by Andy_ma,

    Andy_ma Andy_ma Oct 6, 2014 8:38 AM in response to CantSalomeDown
    Level 1 (0 points)
    Oct 6, 2014 8:38 AM in response to CantSalomeDown

    Hi all,

     

    just to confirm that i upgraded today and issue is STILL there but, fortunately, solved it deleting search policy.

     

    thanks to all of you for the tips and support!!

    andy

  • by PJSChicago,

    PJSChicago PJSChicago Oct 7, 2014 7:12 AM in response to Vlasak
    Level 1 (0 points)
    Oct 7, 2014 7:12 AM in response to Vlasak

    Hello All - We also experienced this after 2 Mac Book Pros were upgraded to 10.9.5. These machines were bound to the network in AD. One machine we reverted back to 10.9.4 by way of Time Machine. The only time opendirectoryd would go haywire was the machine being on our corporate network and having been upgraded to 10.9.5.

     

    The other was unbound from the network. Is there a ways to alert Apple to this bug?

  • by SeeCoolGuy2,

    SeeCoolGuy2 SeeCoolGuy2 Oct 7, 2014 7:41 AM in response to PJSChicago
    Level 1 (0 points)
    Oct 7, 2014 7:41 AM in response to PJSChicago

    bugreport.apple.com 

     

    I filed a bug with the symptoms I was seeing on my machine,  I have not had the time to re-upgrade to 10.9.5 on my domain mac to test if the search policy fix (removal of the extra search domain) fixes the issues with opendirectoryd.

  • by contempt,

    contempt contempt Oct 9, 2014 8:13 AM in response to keithfromvirginia beach
    Level 1 (5 points)
    Oct 9, 2014 8:13 AM in response to keithfromvirginia beach

    This solved my problem! I was having the same problem as everyone getting about 350% CPU consumption from OpenDirectoryD. Removing all EXCEPT for /Active Directory/XYZ/All Domains solved this! Now it doesn't go beyond 5% and my computer is back to full speed.

    Thanks Keith.

  • by tchmiel,

    tchmiel tchmiel Oct 16, 2014 6:51 AM in response to CantSalomeDown
    Level 1 (0 points)
    Oct 16, 2014 6:51 AM in response to CantSalomeDown

    Thanks for the resolution.  I removed the /Active Directory/MYDOMAIN entry and now my machine is usable again!

    Much appreciated.

    Tom

  • by LonniusMax,

    LonniusMax LonniusMax Oct 17, 2014 8:27 AM in response to Vlasak
    Level 1 (0 points)
    Photos for Mac
    Oct 17, 2014 8:27 AM in response to Vlasak

    This may be slightly off-topic, but I believe still relevant to the folks here: Has anyone who has had trouble with this update upgraded to Yosemite? If so, did you have issues with AD? I'm a bit leery about it after my previous experience with 10.9.5.

  • by SeeCoolGuy2,

    SeeCoolGuy2 SeeCoolGuy2 Oct 17, 2014 3:06 PM in response to LonniusMax
    Level 1 (0 points)
    Oct 17, 2014 3:06 PM in response to LonniusMax

    I am using a 2011 iMac, the plan is for me to update after 1 month in case there are other SMB / AD issues in the current .0 release of Yosemite.

     

    On my home 2013 iMac, I updated and the short few hours I worked on it, everything seemed fine, (iPhoto, iMovie... etc).

  • by buckley100,

    buckley100 buckley100 Oct 20, 2014 7:57 AM in response to keithfromvirginia beach
    Level 1 (0 points)
    Oct 20, 2014 7:57 AM in response to keithfromvirginia beach

    Keith is quite correct.

     

    See Apple KB Article: OS X: If the opendirectoryd process CPU utilization is high after updating to OS X v10.9.5

     

    Make sure you remove from Authentication and Contacts, this is vital otherwise you will still have high CPU %.

first Previous Page 3 of 4 last Next