You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

srobert Author

Level 1

25 points

discoveryd process uses 100% CPU - Safari Can't find the server

Hello

Since upgrading to Yosemite, I lose connection to the internet 2 or 3 times a day. (Outlook goes offline at the same time)

This is with a wired connection. (Wi-Fi is turned off)

Safari gives me the "Safari Can't Find the Server" message.

Restarting the computer solves the issue temporarily.

While I'm unable to connect to the internet, Activity Monitor shows a process named "discoveryd" that uses 100% CPU.

Force quitting this process gives me back access to the internet instantly. Unfortunately, I suffered a kernel panic (auto restart) a few minutes after force quitting discoveryd. I'm not 100% sure those 2 are related but it would be an odd coincidence as I never experienced had a single kernel on that system. Haven't tried force quitting that process since.

I'm using this iMac in a work environment. (Connected to a windows file server and exchange)

This issue has been happening 2-3 times a day since the day I upgraded to Yosemite.

Any pointers on what could fix this issue ?

Thanks

iMac, OS X Yosemite (10.10), iMac (27-inch, Mid 2010)

Posted on Nov 10, 2014 1:05 PM

74 replies

Apr 7, 2015 6:04 PM in response to DannyBoyVA

Try to redirect the incoming port 53 to your router's IP. Once I did that run this issue went away for me.

AdB1973

Level 1

13 points

Apr 22, 2015 6:59 AM in response to srobert

I'm inclined to think this is bound to the discoveryd.plist mentioned before.

Fresh installs seem to help

unloading the plist seems to help

and (don't do it) deleting the .plist helps too (but you won't have internet).

hope Apple fixes this because my MBP early 2011 consumes battery power like a monster when discoveryd is burning the CPU

stefdnk

Level 1

11 points

Apr 22, 2015 7:41 AM in response to AdB1973

Don't know if this may help others.

I disabled the remote control in the Security and Privacy.

Apr 26, 2015 7:19 AM in response to mrwahed

This so far seems to have resolved the discoveryd issue where it was showing 99% CPU usage in Activity Monitor - I also deleted out a couple of unused network services related to old mobile phones - but anyhow it all seems to be working a little bit quicker and smoother - just a RAM upgrade to do now and I hope things will be like new .......

Apr 30, 2015 2:25 AM in response to srobert

Hello guys,

i also have problems with the discoveryd -> 100% CPU usage.

But i have no problems with safari.

For me this commands in Terminal helps temporarily!

sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist

sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.discoveryd.plist

I have the problem since 10.10.3

Its very annoying!

Hope Apple will fix it immediately....

----------------------------

Macbook Pro early 2011

15" i7

cdhw

Level 4

3,588 points

Apr 30, 2015 2:51 AM in response to Blümchenpflücker

The fix that works in many (all?) cases for the 'discoveryd 100% CPU on Yosemite' issue is

Use 'Finder > Go' to go to this folder:

/Library/Preferences/SystemConfiguration/

Delete the file 'preferences.plist' and restart your Mac. Google for the above path if you want further details.

May 3, 2015 5:53 AM in response to cdhw

Thank you cdhw, deleting that file solved the problem... I've been struggling for weeks now and nothing fixed it. 😀

May 3, 2015 2:30 PM in response to cdhw

Thanks, cdhw. Your solution solved my problem as well!

ram_ger

Level 1

0 points

May 9, 2015 12:54 AM in response to cdhw

cdhw, made my day!

thx.

warpony

Level 1

0 points

May 9, 2015 8:53 PM in response to srobert

In my case the issue with discoveryd chewing up my CPU was a 'messy' hosts file. I have had some entires there from way back when I was playing around with DNS and forgot all about them. Cleaned up the extra entries and left only the default loopback entry there. Flushed my DNS, rebooted the machine and voila.

Go>Go to Folder and type /private/etc/hosts

Double-click on the hosts file and see if you have any extra entries there below the IP addresses. The default file should look like this:

# Host Database

# localhost is used to configure the loopback interface

# when the system is booting. Do not change this entry.

127.0.0.1 localhost

255.255.255.255 broadcasthost

::1 localhost