Jerry36
Level 1 (10 points)

Q: [discoveryd problem]No internet connection after lid on/off and CPU 100% leak

Hey,

to resolve 'discoveryd' problem is only upgrade concern.

this problem come from 'wakeup to check cloud and sync' and 'system always pulling and tracking'.

finally, CPU keep 100% and power leak. ( why apple never see that !? )

 

first, to create a script for on/off discoveryd for ensure a solution for  problem come again again.

 

"sol.sh"

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

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

 

second, flower http://www.iphonehacks.com/2014/11/wi-fi-problems-mac-os-x-yosemite.html to remove network configuration.

 

goto /Library/Preferences/SystemConfiguration/

 

trash those file and reboot

  • com.apple.airport.preferences.plist
  • com.apple.network.identification.plist
  • com.apple.wifi.message-tracer.plist
  • NetworkInterfaces.plist
  • preferences.plist
  • com.apple.smb.server.plist

 

so easy!

 

Try to lid on/off few time, I never see that again.

have fun and night.

 

-Jerry

Posted on Apr 11, 2015 6:06 AM

by Jerry36,Solvedanswer
Jerry36 Jerry36
Level 1 (10 points)
A:

After remove system configuration files.

I found new issue at system can't identify DNS.

 

Please set DNS to 8.8.8.8 8.8.4.4 via terminal and reboot again.

'sudo networksetup -setdnsservers Wifi 8.8.8.8 8.8.4.4'

'sudo networksetup -setdnsservers 'Bluetooth PAN' 8.8.8.8 8.8.4.4'

... etc

Posted on Apr 11, 2015 6:56 AM

Close
Jerry36

Q: [discoveryd problem]No internet connection after lid on/off and CPU 100% leak

  • All replies
  • Helpful answers

  • by Jerry36,Solvedanswer

    Jerry36 Jerry36 Apr 11, 2015 6:56 AM in response to Jerry36
    Level 1 (10 points)
    Apr 11, 2015 6:56 AM in response to Jerry36

    After remove system configuration files.

    I found new issue at system can't identify DNS.

     

    Please set DNS to 8.8.8.8 8.8.4.4 via terminal and reboot again.

    'sudo networksetup -setdnsservers Wifi 8.8.8.8 8.8.4.4'

    'sudo networksetup -setdnsservers 'Bluetooth PAN' 8.8.8.8 8.8.4.4'

    ... etc

  • by Jerry36,

    Jerry36 Jerry36 Apr 19, 2015 6:50 AM in response to Jerry36
    Level 1 (10 points)
    Apr 19, 2015 6:50 AM in response to Jerry36

    Yesterday, Apple update new configuration for repair this issue.

    if u updated, this problem shall be closed.

     

    If u have other message for discoveryd, I suggest u check plist and daemon setting.

  • by Bernhard Meier,

    Bernhard Meier Bernhard Meier Jul 3, 2015 2:09 AM in response to Jerry36
    Level 1 (9 points)
    iCloud
    Jul 3, 2015 2:09 AM in response to Jerry36

    Although the Mac OS 10.10.4 update got rid of discoveryd, the network problems behind a proxy persist.

     

    Safari becomes unresponisve after a while (minutes not hours of use). So do other web access protocols. Strangely, Firefox still works.

     

    Only a restart of the computer gets Safari etc. connected again.

     

    Proxy settings are on automatic.

  • by Jondor,

    Jondor Jondor Jul 3, 2015 8:55 AM in response to Bernhard Meier
    Level 1 (27 points)
    Jul 3, 2015 8:55 AM in response to Bernhard Meier

    i have the same problem. even though discoveryd is replaced by the old mDNSResponder process in 10.10.4, this doesn't help to fix the problem. After wake up from sleep, the mac could not connect to the internet.

     

    I found a temporary fix:

    Hold Alt/option and click on the wifi icon on the menu bar,

    choose "disconnect from (SSID name)",

    wait a while and then reconnect to the same network.

     

    The problem appears again after sleep.

     

    so disappointed that apple could not fix this simple bug.

  • by Bernhard Meier,

    Bernhard Meier Bernhard Meier Jul 3, 2015 9:20 AM in response to Jondor
    Level 1 (9 points)
    iCloud
    Jul 3, 2015 9:20 AM in response to Jondor

    Not quite the same here, as I am on an ethernet cable LAN behind a proxy.

     

    Strangely, since I have written my comment the connection has worked steadily. Yet, I am sure that this is not the final solution and disconnection requiring  computer restart will happen again. I had tried changing the connection to WiFi and back but that had not worked. It needed a full reboot.