Apple Event: May 7th at 7 am PT
I have a MacBook Pro (15-inch, Early 2011) i7 2GHz.
After upgrading to 10.10.3 the fan comes on permanently after waking from Sleep.
The Activity: discoveryd is using 100% CPU.
Shutting down rather than Sleep seems to stop this happening, so far.
I'm guessing this will be a "wait for the next upgrade" problem.
Thanks for the help, Linc! Funny thing: yesterday I was about to run through deleting that "zz" folder cache, but before I did it I rebooted and ran Disk Utility to Verify and Repair Disk Permissions (I had forgotten to do that after the 10.10.3 update). I ran it a few times, just in case, and now I haven't had any problems again with discoverd....even though I've run through sleep/wake several times.
I'm going to keep my eye on it and reply back if it occurs again, but I thought I'd mention it in case it could help out here...hope it does!
After trying the suggestions from Linc Davis to run Disk Utility and to delete the zz folder, I still have discoveryd at 100% after waking from sleep. This on a Mac Pro (early 2009) and a MacBook Pro (retina, 13 inch, mid 2014), both on 10.10.3.
Thanks for trying that out J. I haven't done it myself... I like to know why I'm doing something. I know there are a load of dark arts that do work so it was worth a shot. There may be a development though, see my other reply.
I have been switching off for a day or so, so I hadn't checked whether it is still rampant.
But checking now and although discoveryd still runs after Sleep it seems to be using a more sensible amount of CPU.
Maybe it's one of those things that needs to do a lot of catching up after an update (like Spotlight). I do often get the fans revving up after an update but discoveryd has been much more persistent and unusual in that it was Sleep-related too.
Thanks for the heads-up. We may be back to normal!
And I have found the same thing. The problem was not immediately fixed, but now does not happen. After multiple sleep/wake cycles, discoveryd is, at the moment, at 0% CPU.
polarman3d wrote:
Yeah, I'm bummed this is happening, but hopefully they'll find a fix soon. Good for you that it's not just the old models! 🙂 I did find a temporary fix from this thread:
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist
That seems to work, but only for a bit. Sleeping/wake will probably cause the problem again...
All that does is unload & restart the service. It seems likely it will get back to consuming all the CPU since the service has not altered.
Here is another shot in the dark…
Try setting another DNS server in your network config
Google have a free DNS server at these addresses…
8.8.8.8
8.8.4.4
…or you can try any other DNS service you desire (like Open DNS etc).
Another thing to try is disabling multiple network interfaces if you have several enabled. These can be toggled in the 'gear menu' of the interface listing.
Report back with your results please. Repeat the steps that made it fail before (let it sleep etc).
To undo the DNS change delete the Google DNS server & re-enter the one that was noted earlier (if you had one set).
P.S.
@Rob Cumberland, those folders Linc Davis suggested are temporary items, they are safe to delete. Please reconsider deleting them - it may actually help if the directory has bad permissions (repair permissions doesn't fix every single folder on the OS).
The 3 of us who have this problem now report that after a few days it seems to have settled down.
In my case discoveryd still runs after Sleep (and I think when I boot up) but uses only about 30% CPU at most and is gone after a minute or so.
Previously it was hanging in there at 100% CPU indefinitely.
I think this one has gone away on its own.
I'm not sure you are the only 3 seeing this…
There may be other threads too.
I wonder if it is related to Photos app or some other new feature on 10.10.3, it's unclear if you are all uploading images to iCloud etc.
When 10.10 came out others had issues with discoveryd & some even went as far as disabling & reinstalling the version of mdnsresponder from 10.9…
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/ (don't try that)
You may all consider creating EtreCheck reports to compare installed software - it could help indicate common items between your Macs.
I found the mdnsresponder issues and some other problems via Google but nothing that matched this one.
Pierre from page 1 hasn't reported back, so he may still need help.
I've marked the useful replies here so if anyone follows us they can see what we know.
Unless it starts happening again or Pierre comes back I'm done. I don't think there's anything else we can do with this forum... it's pretty limited in terms of logging results.
(Incidentally I used to use 8.8.8.8 but I had a problem with that on the previous release I think. Getting rid of 8.8.8.8 solved that one.)
Thanks, that was solving the problem with the sleep issue
Hello,
I'd been having this issue since last weekend, when I upgraded to 10.10.3. So far I've been killing the discoveryd process, but the problem reappeared on every wakeup; the launchd thing seems to have solved it permanently.
Thanks!
Rafael
Macbook Pro Retina late-2012 13'' 8G RAM 256G SSD
I also discovered that I could halt the process (discoveryd) in Activity Monitor.
Immediately, once disoveryd is stopped, the temperature of my macbook pro plummets and the fans come down from 4k+ rpm to the normal 2K rpm.
I haven't determined what software uses discoverd but when I quit it, no currently open software seems to be affected.
It's old story for me. please follower up!!
[discoveryd problem]No internet connection after lid on/off and CPU 100% leak
goto /Library/Preferences/SystemConfiguration/
trash those file and reboot
so easy!
There was no problem with my Internet connection.
discoveryd stopped running 100% CPU after a few days, on its own.
I did find several historic discoveryd issues through Google but not this 10.10.3 version.
Spoke too soon, today the problem is back. 😟
I'll try Jerry36's solution later and let you know what happenned.
Rafael
After 10.10.3/sleep discoveryd runs 100% CPU
