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 4 of 4
  • by jmo81,

    jmo81 jmo81 Nov 5, 2014 3:30 PM in response to buckley100
    Level 1 (0 points)
    Nov 5, 2014 3:30 PM in response to buckley100

    I ran into a similar issue this week with regards to OS X 10.9.5 (with all updates) AND 10.10 pinwheeling on login; sometimes for as long as 20 minutes.  We have a number of Macs configured to log in with Active Directory, but the problem seemed to occur even when a local account was being accessed.  However, logging in via safe mode worked completely fine. After a few days of troubleshooting, we discovered that the LogMeIn menu bar application was freezing during the login process.  While it was unresponsive, the network connection was dropping packets and disconnected a dozen times (we monitored from the Cisco switch).  The only way we found this connection was I got lucky that I forgot to quit out of Activity Monitor when I rebooted.  Activity Monitor started up at boot just before the machine locked up.  I could see the unresponsive process as it pinwheeled, but couldn't force it closed.  I uninstalled LogMeIn from all the affected machines, and now they have all come back to life.  I'm not sure if this applies to everyone, but I thought I'd share as we were going insane trying to figure out what was going on.  Hopefully patches will come out that will fix the issue.

first Previous Page 4 of 4