mDNSresponder Sierra

Discussion in 'macOS Sierra (10.12)' started by flexiboy1912, Jun 14, 2016.

  1. flexiboy1912 macrumors newbie

    flexiboy1912

    Joined:
    May 13, 2016
    #1
    Installed it and this process is now killing my Mac , anyone else having this problem?

    Cooking my Mac so going to roll back to El Capitan , shame
     
  2. nick19 macrumors member

    nick19

    Joined:
    Jun 4, 2014
    Location:
    London, UK
    #2
    No, mDNSresponder is just sitting there quietly on my rMBP using 0.1% CPU.
     
  3. flexiboy1912 thread starter macrumors newbie

    flexiboy1912

    Joined:
    May 13, 2016
    #3
    Lucky you mine is running about 95% and I also have logd running at 70%.

    Restoring time machine back to El Capitan.

    Perhaps it's because I am on Corp Wi-Fi but did the same on my dongle
    --- Post Merged, Jun 14, 2016 ---
    --- Post Merged, Jun 14, 2016 ---
    Back on El Capitan and CPU back to normal and no sign of either process in activity monitor

    I am on MacBook Pro (Retina, 13-inch, Early 2015)
     
  4. LuisN macrumors newbie

    Joined:
    Mar 30, 2013
    Location:
    Torres Vedras, Portugal
    #4
    --- Post Merged, Jun 17, 2016 ---
    Had same problem in MacBook Pro mid 2012. Did PRAM reset and it is running normal now!
     
  5. flexiboy1912 thread starter macrumors newbie

    flexiboy1912

    Joined:
    May 13, 2016
    #5
    I also tried a fresh install into a new partition rather then and upgrade on the same rMBP at the same network location and this time it didn't cause a problem. So I did the same on my other rMPB and also ok.

    Did you upgrade or fresh install?
     
  6. LuisN macrumors newbie

    Joined:
    Mar 30, 2013
    Location:
    Torres Vedras, Portugal
    #6
    --- Post Merged, Jun 20, 2016 ---
    Upgraded from latest El Capitan beta
     
  7. MacsRgr8 macrumors 604

    MacsRgr8

    Joined:
    Sep 8, 2002
    Location:
    The Netherlands
    #7
    Whatever happened to the effort of using discoveryd?
    They axed it with OS X 10.10.4 after introducing it with 10.10.0 but why did they start with discoverd in the first place?

    In El Cap it didn't return, but also with Sierra Apple has kept the old mDNSresponder.
     
  8. Tomkins! macrumors member

    Joined:
    Jul 17, 2012
    #8
    Discoveryd was supposed to be mDNSreponder's replacement. However, it wasn't ready for primetime yet. That's why they did away with it and restored mDNSresponder.
     
  9. MacsRgr8 macrumors 604

    MacsRgr8

    Joined:
    Sep 8, 2002
    Location:
    The Netherlands
    #9
    Was released as non-Beta in OS X 10.10.0 through 10.10.3. After many complaints it's since then gone.

    My question is: have Apple stopped trying now?
     
  10. Tomkins! macrumors member

    Joined:
    Jul 17, 2012
    #10
    They're probably working on it internally. Maybe they will reintroduce it a few years down the road.
     
  11. Milquetoast, Oct 10, 2016
    Last edited: Oct 10, 2016

    Milquetoast macrumors newbie

    Joined:
    Apr 14, 2008
    Location:
    Maryland
    #11
    I am experiencing horrendous logd output volume (and CPU) to a Time Capsule from a late 2012 mini. Since upgrading to Sierra, working in the background, logd wrote about 16GB over a 24 hour period (and constantly sucked about 70% of one of the four of my mini's I7 cores in the process of doing so, as documented by iStatMenus). Granted, this was on a newly-reconnected off-site TM backup set that was a few months out of service, so there was more churn than normal. But still, that's crazy!!!

    This log data of course later got backed up to a local Time Machine backup set, but without the voluminous logd output. (no, the local Time Machine backup does not show the same logd offense) ;-(( This looks like Nyquist-related instability - it is likely to compound and get worse; I think I will need to disconnect the Time Capsule until Apple can resolve the issue.

    Any thoughts???
     

Share This Page