Shadowstrider

Q: Yosemite random Crash - discoveryd_helper[147]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Hi Everyone,

 

i have a crash every now and then. Looks like it has something to do with Networking or Bonjour.

 

Nov 10 23:55:34.018358 Chriss-iMac.local discoveryd_helper[147]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Nov 10 23:55:34.018593 Chriss-iMac.local discoveryd_helper[147]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7ff9d0600210: start (pid=50, <unknown> not root)

Nov 10 23:55:34.018358 Chriss-iMac.local discoveryd_helper[147]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Nov 10 23:55:34.018593 Chriss-iMac.local discoveryd_helper[147]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7ff9d0600210: start (pid=50, <unknown> not root)

 

anyone got any idea what it could be ? I learned that

 

there is no more com.apple.mDNSResponder.plist in OS X 10.10. The service that controls mDNSResponder is now discoverd. The plist file you are looking for is actually:

/System/Library/LaunchDaemons/com.apple.discoveryd.plist 

You want to add --no-multicast to the ProgramArguments in that file.

  <key>ProgramArguments</key> <array> <string>/usr/libexec/discoveryd</string> <string>--udsocket</string> <string>standard</string> <string>--loglevel</string> <string>Basic</string> <string>--logclass</string> <string>Everything</string> <string>--logto</string> <string>asl</string> </array> 

Becomes

  <key>ProgramArguments</key> <array> <string>/usr/libexec/discoveryd</string> <string>--udsocket</string> <string>standard</string> <string>--loglevel</string> <string>Basic</string> <string>--logclass</string> <string>Everything</string> <string>--logto</string> <string>asl</string> <string>--no-multicast</string> </array>

 

but doing this (adding --no-multicast) disables finding and communicating with printers in my network and my timemachine backup drive can't be found.

 

..... any clues ? this is driving me mad.

Posted on Nov 11, 2014 10:48 AM

Close

Q: Yosemite random Crash - discoveryd_helper[147]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

  • All replies
  • Helpful answers

first Previous Page 9 of 11 last Next
  • by Pascal88,

    Pascal88 Pascal88 May 30, 2015 7:20 AM in response to Erlich Bachmann
    Level 1 (10 points)
    Mac OS X
    May 30, 2015 7:20 AM in response to Erlich Bachmann

    Don't bother again with the Genius bar. They are not geniuses!  Reinstalling the OS is a typical Windows ME & Vista response which is what led me to buy a Mac in the first place. Apple seriously needs to address this issue and stop pumping out defective OS's every year!

  • by NiqueXyZ,

    NiqueXyZ NiqueXyZ May 30, 2015 9:03 AM in response to rwhitley45
    Level 1 (8 points)
    Mac OS X
    May 30, 2015 9:03 AM in response to rwhitley45

    The thing about the logs though is that we now know they are nonsense, so I'm not sure what Apple is going to be able to do with them -- they're all the exact same thing -- It's a cascading failure, the only reason discoveryd fails and puts that in the logs is because something else kicks it off -- what that something else is does *not* get logged, as far as I can see. 

    I used to be halfway decent at supporting macs, is there any way to get more advanced logging from the kernel?  I can't remember..

  • by tatvamasi,

    tatvamasi tatvamasi May 30, 2015 9:55 PM in response to NiqueXyZ
    Level 1 (0 points)
    May 30, 2015 9:55 PM in response to NiqueXyZ

    Did SMC/PRAM reset followed by erasing disk and reinstalling OS (as suggested by apple support), no change ! In my case crash is much frequent, avg crash time is 30 min.

  • by rwhitley45,

    rwhitley45 rwhitley45 May 31, 2015 5:01 AM in response to NiqueXyZ
    Level 1 (0 points)
    May 31, 2015 5:01 AM in response to NiqueXyZ

    Well, they're two types of logs that are important here:

     

    The logs from the crash reporter which indicate what caused the crash

    The system logs which indicate what led up to the crash

     

    Both logs are time stamped so engineering can check what was going on in the system before the crash occurred. That way, it easier to pinpoint the line of code that causes the crash.

  • by rwhitley45,

    rwhitley45 rwhitley45 May 31, 2015 5:07 AM in response to tatvamasi
    Level 1 (0 points)
    May 31, 2015 5:07 AM in response to tatvamasi

    Yes, they're going to give you a lot of advice that just doesn't work.  If I were you, I would just tell them that you already tried to reinstall the OS and it didn't work. Also, go ahead and try running in safe mode and see if a crash occurs (it shouldn't).  Then tell them you also tried abother user and the crash occurred for that user too (it should).

     

    They should be stumped at that point and connect you to a senior advisor.

  • by GKrajnc,

    GKrajnc GKrajnc Jun 4, 2015 1:07 AM in response to Shadowstrider
    Level 1 (0 points)
    Jun 4, 2015 1:07 AM in response to Shadowstrider

    Hi,

     

    MacMini 2012

    Yosemite 10.10.3

    2x4GB orig RAM

     

     

    my problem started 3 days ago with same crashlog which is weird because my macmini didn't crash completly, just network.

     

    DHCP connection via ethernet drops the connection and ethernet goes from green to yellow with Self-assigned IP.

    Tried to release/renew, disable/enable ethernet and put all other connections (BT, wi-fi, TB) on inactive mode and stil no connection.

    I switched on to manual IP and got my connection back. After reboot DHCP was working again till the next day when the same crash happend almost at the same time (1 hour late as seen by the log)

     

    Jun  1 14:02:01.092033 My-Mac-mini.local discoveryd_helper[283]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

    Jun  1 14:02:01.092464 My-Mac-mini.local discoveryd_helper[283]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fa613d01e80: start (pid=74, <unknown> not root)

    Jun  2 15:07:55.123063 My-Mac-mini.local discoveryd_helper[300]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

    Jun  2 15:07:55.123641 My-Mac-mini.local discoveryd_helper[300]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7f9fcb100000: start (pid=75, <unknown> not root)

     

     

    On the 3rd day it gets even weirder:

     

    03/06/15 15:08:33,806 discoveryd[75]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.1 Port 53 errno 49, fd 56, ErrLogCount 4 ResolverIntf:0

    03/06/15 15:08:33,808 networkd[295]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache

    03/06/15 15:08:33,809 configd[51]: network changed: v4(en0-:192.168.1.70) DNS- Proxy-

    03/06/15 15:08:33,810 discoveryd[75]: Basic WABServer NetResolverEvent no resolvers, resetting domains

    03/06/15 15:08:33,810 discoveryd[75]: Basic Warn DD_Warn: Corrupt NSEC RDATA size

    03/06/15 15:08:33,812 configd[51]: setting hostname to "My-Mac-mini.local"

    03/06/15 15:08:38,815 netbiosd[340]: network_reachability_changed : network is not reachable, netbiosd is shutting down

    03/06/15 15:08:43,821 com.apple.geod[554]: 2015-06-03 15:08:43.820, 554, f2765b00, [CountryConfiguration]: Could not determine current country code: Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo=0x7fdcf242a160 {NSUnderlyingError=0x7fdcf273f590 "The Internet connection appears to be offline.", NSErrorFailingURLStringKey=http://gsp1.apple.com/pep/gcc, NSErrorFailingURLKey=http://gsp1.apple.com/pep/gcc, _kCFStreamErrorDomainKey=12, _kCFStreamErrorCodeKey=8, NSLocalizedDescription=The Internet connection appears to be offline.}

    03/06/15 15:08:53,546 com.apple.preference.network.remoteservice[3788]: Failed to connect (o_advancedMenu) outlet from (ANPNetworkController) to (NSMenu): missing setter or instance variable

    03/06/15 15:08:53,625 com.apple.preference.network.remoteservice[3788]: Failed to connect (o_serviceImageView) outlet from (ANPAdvancedTabController) to (NSImageView): missing setter or instance variable

    03/06/15 15:08:53,625 com.apple.preference.network.remoteservice[3788]: Failed to connect (o_serviceNameField) outlet from (ANPAdvancedTabController) to (NSTextField): missing setter or instance variable

    03/06/15 15:08:53,625 com.apple.preference.network.remoteservice[3788]: Failed to connect (o_tabViewWindow) outlet from (ANPAdvancedTabController) to (NSPanel): missing setter or instance variable

    03/06/15 15:08:54,040 com.apple.preference.network.remoteservice[3788]: Could not find image named 'InvalidDataIcon'.

     

     

    In log on DHCP server I only get "Unsuccessful offer lease"

  • by Shadowstrider,

    Shadowstrider Shadowstrider Jun 4, 2015 1:52 AM in response to GKrajnc
    Level 1 (0 points)
    Jun 4, 2015 1:52 AM in response to GKrajnc

    Hi Everyone,

     

    ok so some update from my side. I have installed 10.10.4 Public beta on 27.4.2015. on my Imac 5k. No crash since then. This seems to have fixed the issue for me.

     

    I can back theory: "It looks like Apple has finally come to their senses and has dropped the closed source discoveryd from the latest Yosemite and replaced it with the open source mDNSResponder we all know and love."

     

    My recomendation is try the Public beta. https://appleseed.apple.com/sp/betaprogram/ 

     

    good luck.

  • by tatvamasi,

    tatvamasi tatvamasi Jun 8, 2015 6:59 PM in response to Shadowstrider
    Level 1 (0 points)
    Jun 8, 2015 6:59 PM in response to Shadowstrider

    No luck with 10.10.4 beta for me.

  • by Foxy754,

    Foxy754 Foxy754 Jun 12, 2015 6:10 PM in response to tatvamasi
    Level 1 (4 points)
    Jun 12, 2015 6:10 PM in response to tatvamasi

    Hello, I am having this same issue. I'm not going to bother copying and pasting the code. From what I have read going and getting a new hard drive wont fix this as well as different ram. The computer acted like I opened the bottom while it was still on. If I were to go buy anther Macbook Pro from a reseller and put my hard drive in it would the issue persist? I would be upgrading from a mid 2010 to a mid 2012 so its not like that much of a difference but  if that will help thats what I will do.

     

    Thanks!

  • by rwhitley45,

    rwhitley45 rwhitley45 Jun 12, 2015 6:35 PM in response to Foxy754
    Level 1 (0 points)
    Jun 12, 2015 6:35 PM in response to Foxy754

    It's not the machine that's the problem; it's the OS (Yoesmite).  Getting a new machine might help, but you always run the risk of having this issue if you have Yoesmite installed.

  • by Foxy754,

    Foxy754 Foxy754 Jun 12, 2015 7:19 PM in response to rwhitley45
    Level 1 (4 points)
    Jun 12, 2015 7:19 PM in response to rwhitley45

    Is there any way to avoid this while on Yosemite? I really don't want to go back. I will be upgrading to the Beta in July, but I don't want to live wit hit that long. Has anyone tried the fresh install and then restored from a backup?

  • by NiqueXyZ,

    NiqueXyZ NiqueXyZ Jun 12, 2015 7:50 PM in response to Foxy754
    Level 1 (8 points)
    Mac OS X
    Jun 12, 2015 7:50 PM in response to Foxy754

    Yes, reinstalled and had no 3rd party apps running, did not restore from any backup -- crashed within 2 hours just browsing with Safari.

  • by rwhitley45,

    rwhitley45 rwhitley45 Jun 12, 2015 7:54 PM in response to Foxy754
    Level 1 (0 points)
    Jun 12, 2015 7:54 PM in response to Foxy754

    If you're lucky, 10.10.4 will fix it for you.  But that's only if you're lucky.  I and others have not been so lucky.  And so far we've had no fix.

  • by Shadowstrider,

    Shadowstrider Shadowstrider Jun 13, 2015 2:55 AM in response to rwhitley45
    Level 1 (0 points)
    Jun 13, 2015 2:55 AM in response to rwhitley45

    Update on my side again.

     

    10.10.4 beta did not fix the Problem. It reduced the frequency of the crashes though.

  • by Foxy754,

    Foxy754 Foxy754 Jun 13, 2015 11:41 AM in response to Shadowstrider
    Level 1 (4 points)
    Jun 13, 2015 11:41 AM in response to Shadowstrider

    I'm looking into taking my disc drive out and then putting in a hard drive. I just need a clamp to do so. With that I will try to go back to mavericks and then keep my system on Yosemite and then when El Capitan launches next month I will update to that after restoring my computer to Yosemite. Anyone tried this?

first Previous Page 9 of 11 last Next