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

On my system at least, I don't think that is the case. I have not been using any external devices for any of my crashes. And my crashes just started this week, a while after I installed 10.10.2 (14C109).

I was just noticing issues with google chrome, but I've stopped using chrome for the time being. Oddly, when I started up after one of the crashes Chrome opened up even though it wasn't (or should not have been) running before the crash.

Additional programs used at time of crash: iTunes, Excel and Word 2011, chrome (or) safari.

oh thank goodness I found this thread. Had multiple calls to AppleCare who have neither solved the problem nor have any clue on how to read the log files. I am having kernel panics at least 1x/day with seemingly complete randomness. Same logs as reported above:

Feb 15 06:03:20.790184 Scotts-Mac-Pro.local discoveryd_helper[177]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 15 06:03:20.790614 Scotts-Mac-Pro.local discoveryd_helper[177]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7f9a31e022c0: start (pid=51, <unknown> not root)

Feb 15 21:40:10.739244 Scotts-Mac-Pro.local discoveryd_helper[177]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 15 21:40:10.739666 Scotts-Mac-Pro.local discoveryd_helper[177]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fbf73b003b0: start (pid=50, <unknown> not root)

As you can see, two just today. No real sense of what causes it. Sometimes it is right after re-boot; this evening it was after 12+ hours of working like normal. TOTALLY random. Arrrrgggghhhhh. I have a brand-spanking-new Mac Pro late 2013 running 10.10.2 with 3.5GHz 6-Core Intel and 16GB RAM and AMD FirePro D300 graphics card. Lots of USB3 drives attached, dual monitors, etc..

Been an Apple user for 20 years and have had every possible model. NEVER had this happen in 20 years.

Aaarrrrrgggghhhhh.

Reset the discoverd daemon using/Applications/Utilities/Activity Viewer.app. See if that helps.

I found the following article interesting: http://cyberparse.co.uk/2015/01/12/why-dns-in-os-x-10-10-is-broken-and-what-you- can-do-to-fix-it/

For the first time, I now (sort of) understand what "discoveryd" is. I haven't tried the "solution" proposed in this article, because my own problems have magically gone away in the past few weeks, but I'll try this if they resurface. Essentially, what it proposes is replacing "discoveryd" with the "mDNSResponder" process which was used versions of OS X prior to Yosemite (when it was replaced by discoveryd).

I remember that earlier, someone proposed the theory that this was related to Bonjour networking. I also remember that I had to reset my home network a few weeks ago, due to some kind of DNS duplication (can't remember exactly, but I had error messages in my Airport Utility app). This roughly coincided with the time when my Mac stopped crashing. That could be a complete coincidence, but I'm offering this up as a theory - i.e. that this is caused by some kind of networking issue related to the new discoveryd process in Yosemite. This would explain why the bug is affecting people with every kind of Mac (not specific to any hardware configuration, e.g. discrete graphics cards) running Yosemite, and why downgrading to earlier versions of OS X seems to fix the problem.

thank you @satcomer and @srminton. That is very useful indeed. What a mess this is. I am not courageous enough to replace discoveryd with mDNSResponder but at least I know that all the crap that AppleCare has been telling me over the past few weeks is not true (i.e. it's my 3rd party software fault, it's my 3rd party hard drives' fault, it's my 3rd party monitors' fault, it's my 3rd party anti-virus software fault, it's my 3rd party router's fault, etc... - basically it's not their fault because I have the gall to use non-Apple software and hardware on my mac) and in fact it's an OS X 10.10 core issue. Hopefully someone from Apple is working on this???

Thanks again. Much appreciated.

I think the discoveryd article is a red herring. The article does not describe the kind of issues we're seeing.

Just stabbing in the dark a little here: Who seeing this issue have some sort of audio software from Rogue Amoeba (HiJack, AirFoil, etc)? Especially if it has not been updated since before Yosemite came out. If you don't have one of their programs, do you have something else installed that uses AirPlay in some way (other than what Apple has implemented)?

Also, who started seeing this issue after restoring from TimeMachine or migrating from another computer?

You're right that the article doesn't describe the issues we're seeing. It may be a red herring. The main reason I posted it was that it explains what the 'discoveryd' process is, as this process is referred to within the error message. The other reason was that it may link to a theory, posted earlier in this thread, that this crash has something to do with networking (perhaps Bonjour). I'm shooting in the dark, too, really....

I don't have any audio software installed, or anything that uses AirPlay (except iTunes), and I don't use Time Machine. My MacBook has a clean, fresh install of Yosemite, and wasn't migrated from another computer. I don't have any USB drives or peripherals connected, but I do use it with an external monitor (Thunderbolt Display) and Bluetooth keyboard / mouse / trackpad.

I haven't had a crash in around a month now. I've gradually reinstalled all of the apps I had disabled or removed, re-enabled Bluetooth and Continuity, re-connected to the monitor, and so far the problem (which was often happening multiple times a day) hasn't returned. I realise that I'm jinxing myself, but there must be a logical explanation.

Quick info add. I'm a tech with a school district. My machine crashed last night with a spinning wheel. Restarted and clicked on my user account icon. Spinning beach ball. My account is an active directory account. So after the second time of it doing it, I tried another local admin account. Same thing happened. Restarted and tried the guest account, same thing. Tried again this morning at home, same thing. Brought it into school and was able to finally login to the local admin account. Did a repair permission and the usual stuff. Logged out and was able to login with my ad account.

At this time, we started to get reports from teachers that they had a crash and now overtime they clicked their icon on the login screen, it would have a spinning beach ball with no resolution. Started having them come in and startup their machines. Wait about 5 minutes or so on the login screen and poof, they could login.

This all happened starting 2/19 at about 22:00. All of the machines coming in have the following crash report at the times when they clicked their account icon:

discoveryd_helper[238]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

discoveryd_helper[238]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fbfe98003a0: start (pid=53, <unknown> not root)

All of them are bound to the same AD server. The only new thing is that we have 10.8.5 clients reporting the same issue but they do not have this crash reporter log. So far 20 machines are all affected at the same time and I am going to assume that we will have more reports as the day goes on.

Have contacted helpdesk with this issue.

Thanks for sharing, Jason. Is there anything else special about these machines besides the fact that they're bound to an AD domain? There's wouldn't be discoveryd messages in 10.8 as the OS still used mDNS responder, but I'm very interested to hear that you're seeing similar symptoms with that OS. It's also really interesting that other machines on your net seemed to start having this issue all at once.

Of course it could be that whatever is causing the system to crash is causing discoveryd to crash before the rest of the system goes. Several times when this has happened to me, there's been a sort of cascading effect where I'll only see the beachball in a couple applications and first and then the rest will become unresponsive - though sometimes it seems like everything goes at once.

Has anyone else found a way to reliably reproduce the problem? I've seen issues recently while Evernote was re-indexing after an update, when I was trying to rebuild my mailbox index in Mail.app, and while using a windows VM in VMWare Fusion, but I haven't gotten to the point where I can reliably cause a crash.

Same issue here. Daily crashes. Last messages before crash:

Feb 26 12:52:57.246279 localhost discoveryd_helper[158]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 26 12:52:57.246589 localhost discoveryd_helper[158]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7ffc62c03910: start (pid=50, <unknown> not root)

I have been struggling with a Mac Mini at my wife's day spa that started spontaneously rebooting occasionally after upgrading to Yosemite. After looking at this thread and a few others. I believe that the cause is Bonjour or at least involved Bonjour and I am posting here because have the XPC RemoteControl messages in the CrashReporter log file.

I am using Bonjour to serve two printers on the Mac to a PC running Windows 7. This all worked fine with Mavericks. After upgrading to Yosemite printing from the PC generally worked but since the most recent Yosemite update (10.10.2), printing from the PC fails after a few print jobs or a short time (I can't tell which) and the only way I have found to restore printing is to reboot the Mac Mini (I guess if I restarted the right service I would not need the reboot). Nothing needs to happen on the PC side. The last random reboot happened this afternoon when there was a queue of customers waiting to checkout. In the CrashReporter file com.apple.networking.discoveryd.log I find:

Mar 1 15:40:14.886910 localhost discoveryd_helper[152]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Mar 1 15:40:14.887318 localhost discoveryd_helper[152]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fe329600260: start (pid=53, <unknown> not root)

and in the file com.apple.networking.discoveryd.log.<datetimestamp> from last night when I was printing some W-2s from QuickBooks on the PC, I find:

Feb 28 21:53:29.726454 localhost discoveryd_helper[153]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 28 21:53:29.727363 localhost discoveryd_helper[153]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fea32701dc0: start (pid=53, <unknown> not root)

Feb 28 22:13:06.813731 localhost discoveryd_helper[156]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Feb 28 22:13:06.814720 localhost discoveryd_helper[156]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fadf3c009a0: start (pid=53, <unknown> not root)

Same error BUT the Mac Mini did NOT spontaneously reboot, I manually forced the reboot. In the CUPS log, I find tons of errors from last night like:

E [28/Feb/2015:22:13:18 -0500] Missing value on line 687.

E [28/Feb/2015:22:13:18 -0500] Missing value on line 699.

E [28/Feb/2015:22:13:18 -0500] Missing value on line 711.

The printer I was printing to is an older HP Multifunction laser printer model 3015 which has served me well for many years and under Mavericks the Gutenprint driver worked apparently flawlessly. I don't think it matters but the other printer is a fairly recent Epson WP-4020 which is also served by Bonjour to the PC, also fails after printing for a short time and also worked fine under Mavericks. The Epson is using the current Epson propriety driver. Under Yosemite the Gutenprint driver for the HP seems to work fine when printing from the Mac but apparently no longer plays well with Bonjour. The Epson driver also works fine when printing from the Mac. In between the bootlog: BOOT_TIME line and XPC messages I see this:

3/1/15 3:39:59.000 PM kernel[0]: Previous shutdown cause: -62

and whole stack of suspicious messages from the kernel /XPC/discoveryd which I put at the bottom of this post.

I am UNIX/Linux compliant as my day job involves looking for subatomic particles and I have been trying move the day spa off Windows because usually BSD/Mac OS X kernel is rock solid (and I know what to do on the command line) and Windows always seems to fail in mysterious ways but this is making me look a little idiotic. If anyone can tell me what to do, I would be most appreciative.

Thanks greatly!

Fred

Suspicious kernel/XPC/discoveryd messages:

3/1/15 3:39:40.702 PM com.apple.xpc.launchd[1]: (com.apple.alf) The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

3/1/15 3:39:40.703 PM com.apple.xpc.launchd[1]: (com.apple.audio.coreaudiod) Unknown key for array: seatbelt-profiles

3/1/15 3:39:40.703 PM com.apple.xpc.launchd[1]: (com.apple.backupd-helper.status) The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

3/1/15 3:39:40.703 PM com.apple.xpc.launchd[1]: (com.apple.backupd-auto) This service is defined to be constantly running and is inherently inefficient.

3/1/15 3:39:40.703 PM com.apple.xpc.launchd[1]: (com.apple.backupd-status) The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

3/1/15 3:39:44.961 PM iconservicesagent[39]: iconservicesagent launched.

3/1/15 3:39:40.703 PM com.apple.xpc.launchd[1]: (com.apple.backupd.status.xpc) The HideUntilCheckIn property is an architectural performance issue. Please transition away from it.

3/1/15 3:39:40.703 PM com.apple.xpc.launchd[1]: (com.apple.bsd.dirhelper) The TimeOut key is no longer respected. It never did anything anyway.

3/1/15 3:39:40.776 PM com.apple.xpc.launchd[1]: (com.apple.cmio.AVCAssistant) ThrottleInterval set to zero. You're not that important. Ignoring.

3/1/15 3:39:40.776 PM com.apple.xpc.launchd[1]: (com.apple.cmio.IIDCVideoAssistant) ThrottleInterval set to zero. You're not that important. Ignoring.

3/1/15 3:39:40.776 PM com.apple.xpc.launchd[1]: (com.apple.cmio.VDCAssistant) ThrottleInterval set to zero. You're not that important. Ignoring.

3/1/15 3:39:40.806 PM com.apple.xpc.launchd[1]: (com.apple.auditd) The TimeOut key is no longer respected. It never did anything anyway.

3/1/15 3:39:40.904 PM com.apple.xpc.launchd[1]: (com.apple.coreduetd) This service is defined to be constantly running and is inherently inefficient.

3/1/15 3:39:40.904 PM com.apple.xpc.launchd[1]: (com.apple.coreservicesd) The HopefullyExitsLast key is no longer respected. Please remove it.

3/1/15 3:39:40.905 PM com.apple.xpc.launchd[1]: (com.apple.configd) This service is defined to be constantly running and is inherently inefficient.

3/1/15 3:39:53.993 PM com.apple.xpc.launchd[1]: (com.apple.watchdogd) Service only ran for 0 seconds. Pushing respawn out by 10 seconds.

3/1/15 3:39:56.341 PM com.apple.xpc.launchd[1]: (com.apple.secd) This key does not do anything: OnDemand

3/1/15 3:39:56.341 PM com.apple.xpc.launchd[1]: (com.apple.secd) The ServiceIPC key is no longer respected. Please remove it.

3/1/15 3:39:56.807 PM com.apple.xpc.launchd[1]: (com.apple.speech.speechsynthesisd) This key does not do anything: OnDemand

3/1/15 3:39:56.918 PM com.apple.xpc.launchd[1]: (com.apple.TrustEvaluationAgent) This key does not do anything: OnDemand

3/1/15 3:39:57.000 PM kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification

3/1/15 3:39:57.000 PM kernel[0]: IO80211Interface::efiNVRAMPublished():

3/1/15 3:39:57.000 PM kernel[0]: bpfAttach len 64 dlt 12

3/1/15 3:39:58.798 PM fseventsd[21]: log dir: /.fseventsd getting new uuid: 790D394C-BAB7-4F3D-B87B-FC62A2574A42

3/1/15 3:39:58.849 PM kdc[66]: krb5_kdc_set_dbinfo: failed to create root node: /Local/Default

3/1/15 3:39:59.000 PM kernel[0]: IOGraphics flags 0x43

3/1/15 3:39:59.000 PM kernel[0]: [IOBluetoothHCIController][start] -- completed

3/1/15 3:39:59.000 PM kernel[0]: IOBluetoothUSBDFU::probe

3/1/15 3:39:59.000 PM kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x828A FirmwareVersion - 0x0099

3/1/15 3:39:59.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x1800 ****

3/1/15 3:39:59.000 PM kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0x1800 ****

3/1/15 3:39:59.000 PM kernel[0]: [IOBluetoothHCIController][staticBluetoothTransportShowsUp] -- Received Bluetooth Controller register service notification -- 0x1800

3/1/15 3:39:59.126 PM com.apple.xpc.launchd[1]: (com.apple.Kerberos.kdc[66]) Service exited with abnormal code: 1

3/1/15 3:39:59.000 PM kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService

3/1/15 3:39:59.000 PM kernel[0]: **** [IOBluetoothHCIController][ProcessBluetoothTransportShowsUpActionWL] -- Connected to the transport successfully -- 0x2780 -- 0xe000 -- 0x1800 ****

3/1/15 3:39:59.000 PM kernel[0]: PPGTT is enabled

3/1/15 3:39:59.000 PM kernel[0]: Previous shutdown cause: -62

3/1/15 3:39:59.000 PM kernel[0]: DSMOS has arrived

3/1/15 3:40:00.224 PM iconservicesagent[39]: Starting service with cache path: /var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/C/com.apple.iconservices

3/1/15 3:40:00.000 PM kernel[0]: pci pause: SDXC

3/1/15 3:40:02.291 PM com.apple.SecurityServer[58]: Entering service

3/1/15 3:40:02.510 PM kdc[97]: label: default

3/1/15 3:40:02.511 PM kdc[97]: dbname: od:/Local/Default

3/1/15 3:40:02.511 PM kdc[97]: mkey_file: /var/db/krb5kdc/m-key

3/1/15 3:40:02.511 PM kdc[97]: acl_file: /var/db/krb5kdc/kadmind.acl

3/1/15 3:40:02.955 PM opendirectoryd[48]: BUG in libdispatch: 14C109 - 2004 - 0x5

3/1/15 3:40:03.435 PM com.apple.usbmuxd[57]: usbmuxd-344.5 on Dec 5 2014 at 17:02:22, running 64 bit

3/1/15 3:40:03.476 PM iconservicesd[38]: iconservicesd launched.

3/1/15 3:40:03.476 PM iconservicesd[38]: Cache path: /Library/Caches/com.apple.iconservices.store

3/1/15 3:40:06.971 PM thermald[23]: Waiting for OSTT support notification

3/1/15 3:40:07.605 PM loginwindow[71]: Login Window Application Started

3/1/15 3:40:07.645 PM stackshot[70]: Timed out waiting for IOKit to finish matching.

3/1/15 3:40:08.402 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.domain.system) Service "com.apple.ManagedClient.startup" tried to hijack endpoint "com.apple.ManagedClient.agent" from owner: com.apple.ManagedClient

3/1/15 3:40:09.394 PM systemkeychain[132]: done file: /var/run/systemkeychaincheck.done

3/1/15 3:40:09.739 PM kdc[97]: WARNING Found KDC certificate (O=System Identity,CN=com.apple.kerberos.kdc)is missing the PK-INIT KDC EKU, this is bad for interoperability.

3/1/15 3:40:10.122 PM apsd[54]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)

3/1/15 3:40:12.249 PM discoveryd[53]: Basic Sockets GetProcessNameFromSocket() failed errno[57] err[-1]

3/1/15 3:40:12.249 PM discoveryd[53]: Basic Sockets Unknown(-1), errno 0 UDS FD=3

3/1/15 3:40:12.249 PM discoveryd[53]: Basic Sockets UDS FD=3 ERROR: failed to get effective user ID, errno 0

3/1/15 3:40:12.293 PM discoveryd[53]: Basic SleepProxy BSP Server Disabled. Metric = 3373

3/1/15 3:40:12.487 PM com.apple.xpc.launchd[1]: (com.apple.appkit.xpc.sandboxedServiceRunner) The JoinExistingSession key is only available to Application services.

3/1/15 3:40:12.793 PM secinitd[143]: UID[0]: cache loaded: /System/Library/Caches/com.apple.app-sandbox-cache.plist

3/1/15 3:40:12.794 PM secinitd[143]: ctkd[136]: unable to get root path for bundle of main executable: /System/Library/Frameworks/CryptoTokenKit.framework/ctkd

3/1/15 3:40:13.193 PM smb-sync-preferences[75]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.smbd

3/1/15 3:40:13.220 PM apsd[54]: Unable to bootstrap_look_up connection port 'com.apple.askpermission.aps' for user 0: Unknown service name

3/1/15 3:40:13.221 PM apsd[54]: Attempt to set push wake topics without dark wake enabled: ()

3/1/15 3:40:13.222 PM apsd[54]: Unable to bootstrap_look_up connection port 'com.apple.askpermission.aps' for user 0: Unknown service name

3/1/15 3:40:13.222 PM apsd[54]: <APSConnectionServer: 0x7fd5f9d37910> Invalid mach port - Cleaning up this named port's topics. com.apple.askpermission.aps

3/1/15 3:40:13.929 PM discoveryd[53]: AwdlD2d AwdlD2dInitialize: Initialized

3/1/15 3:40:14.133 PM digest-service[151]: label: default

3/1/15 3:40:14.133 PM digest-service[151]: dbname: od:/Local/Default

3/1/15 3:40:14.133 PM digest-service[151]: mkey_file: /var/db/krb5kdc/m-key

3/1/15 3:40:14.133 PM digest-service[151]: acl_file: /var/db/krb5kdc/kadmind.acl

3/1/15 3:40:14.234 PM digest-service[151]: digest-request: uid=0

3/1/15 3:40:14.403 PM discoveryd[53]: D2D_IPC: Loaded

3/1/15 3:40:14.414 PM discoveryd[53]: Basic WABServer NetResolverEvent no resolvers, resetting domains

3/1/15 3:40:14.414 PM discoveryd[53]: Basic RemoteControl com.apple.discoveryd Starting XPC Server

3/1/15 3:40:14.415 PM discoveryd[53]: Basic SleepProxy Could not get the primary interface

3/1/15 3:40:14.415 PM discoveryd[53]: Basic RemoteControl com.apple.discoveryd.dnsproxy Starting XPC Server

3/1/15 3:40:14.415 PM discoveryd[53]: Basic DNSResolver etc/hosts file changed: Event 0x7fc273e01f20 Flushed /etc/hosts cache

3/1/15 3:40:14.417 PM discoveryd[53]: Basic SleepProxy Sleep Proxy Server is not enabled

3/1/15 3:40:14.485 PM kdc[97]: KDC started

3/1/15 3:40:14.654 PM Symantec Error Reporting[50]: Symantec Error Reporting Daemon: Could not reach the error reporting servers.

3/1/15 3:40:14.887 PM discoveryd_helper[152]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

3/1/15 3:40:14.887 PM discoveryd_helper[152]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fe329600260: start (pid=53, <unknown> not root)

3/1/15 3:40:15.571 PM configd[26]: preference: no sharing preferences

Hi all!

Imac 24" (2008) running Yosemite 10.10.2 upgraded from Snow Leopard 10.6.8

SnowLeopard was absolutely stable for years (despite de fact that there is an issue with graphic card, but this is another story...).

Update, and crashes began: sometimes, the same awful striped screen -the mentioned graphic failure that i originally solved downgrading kext...- and some other times, with the so mentioned here problem:

Mar 9 10:19:00.998066 localhost discoveryd_helper[140]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Mar 9 10:19:00.998932 localhost discoveryd_helper[140]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7ff400401ad0: start (pid=51, <unknown> not root)

I have no idea 😟

Same here. Identical. A crash at 3:07pm. Another at 7:52pm. See below.

Shadowstrider's original post on this was on 11th November 2014. It's now 11th March 2015. That's FOUR months. It's mind boggling that Apple haven't addressed it.

Mar 10 15:07:15.396900 Nots-MacBook-Pro.local discoveryd_helper[149]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Mar 10 15:07:15.397643 Nots-MacBook-Pro.local discoveryd_helper[149]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fb999c034b0: start (pid=48, <unknown> not root)

Mar 10 19:52:38.824661 Nots-MacBook-Pro.local discoveryd_helper[138]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

Mar 10 19:52:38.825181 Nots-MacBook-Pro.local discoveryd_helper[138]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7f7fd9700770: start (pid=48, <unknown> not root)

.

Yesterday i asked an apple technician here in Oviedo, Spain, about this issue..... He has no idea.... I'll send an email to somebody else in Apple.

I can't believe there is no solution about this strange issue. :/

i have just phoned to applecare: 'this is a very local trouble; you must reinstall OS.....', 'All i know is in internet', 'your iMac is a Vintage machine' (iMac24" 2008), 'restore your previous SO with time machine'.....

apple is nice but hollow.