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

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

Reply
74 replies

Dec 2, 2014 2:51 PM in response to Carl Jonard

Odd...everytime my CPU usage pegged that high, memory use was also high. However, the reverse is not true. Over time, memory usage grows even past 100 MB, but that doesn't always create a CPU issue. I think this latter behavior is somewhat normal for a system that's been up for 3+ days, just like Kernel task growing to 1.5 GB+


That said, here's a suggestion that you probably won't like much.


Remove all your login items or create a new user with no login items.


Reboot and then only use native Apple Apps for 24 hours and see if the issue resurfaces. I think there may be something amiss in an API that Apple may have deprecated w/o properly informing devs or has shifted calls to the old API to a new one that has issues.


In addition to native apps, you could certainly use ones that don't require network connectivity to function...the point here is to try and eliminate all/most 3rd party calls to the discoveryd process.

Dec 2, 2014 2:57 PM in response to srobert

This is a great workaround until they actually solve the problem.

Here's what I've been doing and I've had no problems since.


Open terminal.

Edit your cron by typing: "crontab -e"

type "i" to insert, then paste the following:

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

type "esc" then "wq" then enter.

Your new crontab will be saved. What this does is every minute relaunch the discoveryd process so that it has no time to grow out of control. It has no adversed impacts on connectivity as i've been connected to a corporate vpn the entire time.

Dec 4, 2014 2:20 AM in response to joedjjjjj

After weeks of running Yosemite on an iMac and MacBook Pro, without any network issues, this happened to my iMac for the first time about half an hour after I enabled screen sharing. (I wanted to try out a VNC client.) Like everyone else, several times a day discoveryd went rogue, ate up all the CPU and stopped discovering things. It didn't seem likely that screen sharing was the reason, so I spent several days messing around with network configurations, deleting plist files, and all the other things suggested in this and other similar forums. Nothing helped.


Then I decided to turn off screen sharing, and lo! the problem went away again.


I'm not saying that's going to be the cause for everyone. Network issues can be complex, and there's certainly a nasty bug in discoveryd, but it was certainly what triggered it in my case. Just thought I'd mention it in case it helps someone.

Dec 12, 2014 12:21 PM in response to srobert

I might have inadvertently fixed my issue. (Fingers crossed)


I can't confirm the issue permanently gone but so far discoveryd hasn't hung up for more than 24 hours. (The issue usually happened every 2-3 hour).


I had what I thought was an unrelated problem: The first tab of my Creative Cloud app (Home) only showed a blue spinning wheel. I found some instructions on the Adobe Community forums on how to fix such an issue.


3. Re: Creative Cloud Desktop App stuck on blue spinning wheel after update.


Michaelkaye Jul 2, 2014 6:31 AM (in response to raphaelP)




This worked for me:




Open Finder, click on Go > Go to Folder. Type in ~/library and hit enter.

Open Application Support/Adobe folder and rename OOBE folder to OOBEold.

Click on Apple icon on the top left, select System Preferences

Choose the network that is currently connected to internet that can be Ethernet or

Airport(Wireless). Click on Advanced button and click Proxies Tab.

Under 'Select a Proxy server to Configure' Uncheck all the proxy check boxes, thenuncheck 'Use Passive FTP Mode (PASV)'.


Hope this helps someone else.




This indeed fixed my creative cloud issue but it might have also fixed my discoveryd issue.


This might still be a coincidence but I thought I'd share in case somebody would like to try.


Anybody knows exactly what unchecking "Use Passive FTP Mode (PASV)" does? Could this cause some other apps to stop working or could it be a security issue?


I'll make sure to update this post if I lose my connection again.

Dec 15, 2014 1:18 PM in response to thepianoman2

thepianoman2 wrote:


Open terminal.

Edit your cron by typing: "crontab -e"

type "i" to insert, then paste the following:

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

type "esc" then "wq" then enter.


Thanks for the tip. Pressing escape and "wq" didn't work for me, but I downloaded Cronnix and added the cron job that way. I modified it to run once every hour instead of every minute. This is a workaround that shouldn't be necessary, but I expect it will work.


User uploaded file

Dec 31, 2014 12:45 AM in response to Carl Jonard

Still now real fix from Apple ? HEY HO APPLE GUYS, WAKE UP, THE NETWORK IS BROKEN IN YOUR OS !!! This is an intolerable issue.

A lot of people are wondering "is it because I run this or that software ?" but there is no specific software involved, your softwares are just trying to use the network resources from the OS and it is broken since Yosemite... 😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠😠

Jan 2, 2015 8:26 AM in response to thepianoman2

I've been having the same problem since Yosemite installed. I'm generally not using Safari, but Firefox or Chrome. I know that Chrome does have some backend processes that can run when the browser is closed, MightyText and PrinterShare are two android apps that use that mechanism, I believe. I do know that it will happen (that is the launchd CPU % will grow to 100%) over time. I had thought, before reading this thread, that some setting was off on my router, since not only is my Mac affected, but my entire network looses connection to the internet (via Comcast cable modem) when this happens. What has been odd is the lack of any error messages in the router. I run a TP-Link TL-WDR4300, but running ww-drt firmware (latest compatible). Sometimes I can reboot the router and the problem will clear, sometimes not. My usual parallel routine, but on the cable modem does not resolve my connectivity. In order of chance of success for a temporary reprieve from internet exile, these things seem to work best, in this order (relative, not absolute, and none 100% of the time):

1) Rebooting the Mac - this will reset the CPU use and the problem will resolve maybe 50% of the time.

2) Rebooting the Router - this will resolve the problem, but usually only for a short time, maybe 20% of the time

3) insuring only one network connection is enabled, using built-in "helpers" to test or configure network connections, alternately turning on all 3 direct to router connections (2 physical and 1 wifi MacPro old style) - keeps me busy but only 5% chance of resolving at best. When it's worked, my impression is that "assist me" then "assistant" in Network Preferences has at times resolved the connectivity issue, but it could be just coincidence,

4) Rebooting the Comcast Modem 0% effective, but what I had to do in the past to resolve loss of Comcast network) Also know telling issues in the event log of the modem, I just see the steps it goes through when rebooting, nothing before or after unusual.

5) Messing with the wwdrt settings (various) 0% effective


Side notes that may or may not be germain or important: Once I noticed the discoveryd process increasing use to 100%, I always have killed that first before attempting to resolve. While that alone, as far as I can tell, never resolved the connectivity issue for me . I was granted the insight to look at the Activity Monitor after experiencing the problem updating iTunes to the latest version, which would attempt with or without my prompting countless times without success. The
App Store could not make it happen and I tried everything I could think of. Another person with that problem (iTunes 12.0 to 12.0.1 update fails, but reports as successful on App Store, while remaining listed as "need to install") eventually was advised to uninstall iTunes (not the intuitive and enjoyable content, the frustratingly complex and buggy app), and I had to do so as well, resolving the issue. But when this was happening the App Store was highlighted in Red in activity monitor, presumably due to the inability to install the iTunes update. I don't know what effect this could have on calls out to DNS or other network traffic.


I had wanted to attempt a DNS flush command to see if that would help, since I remember years ago experiencing a problem that behaved like this on Windows (likely Win XP prior to SP 2), which quickly resolved when DNS flush forced by PC. But I don't recall any symptom including a process hogging CPU in conjunction, just an otherwise unfixable inability to get out of the LAN to the internet. I think, as it turns out, Windows Network Sharing was implicated and finally fixed. For what it's worth, through a very fuzzy memory lens.


Any confirmed fixes or helpful workarounds that have been tested a bit by someone smarter than me (I see thousands of candidates with their hands up!) will be happily implemented, or attempted on my machine with commitment to followup with results. BTW, srobert thank you and for your continued focus and willingness continue to beta test. How do we get him promoted to level 2, and does that help in court or when dealing with the IRS? I'm kidding, but the total of the work done by everyone contributing just to this one thread (except this post) is really encouraging and helpful and I think we can't say that to you smart persons enough. Why it's needed, well, that would require a really boring set of stories that hopefully will skip a generation and be told to your grandchildren. A lot of people think we should still be in Vietnam, that Nixon was not any worse than President fillintheblank, and that Fox News presents information not adapted to fit their ideological agenda. Of course, these aren't all the same people, but I'll leave the ven diagrams to your imagination. One more, sorry, truth roll very boring and probably sounds smug, but Reagan was (one of) our best President(s), ever. That is very likely, not very close to the truth.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.