Q: discoveryd process uses 100% CPU - Safari Can't find the server
-
Dec 2, 2014 2:51 PMby rwross1776,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 PMby thepianoman2,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 AMby Mike from Berko,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 PMby 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, then uncheck '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 PMby Carl Jonard,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.
-
Dec 31, 2014 12:45 AMby mbuser,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...
