mDNSresponder Sierra

flexiboy1912

macrumors member
Original poster
May 13, 2016
73
136
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
 

flexiboy1912

macrumors member
Original poster
May 13, 2016
73
136
No, mDNSresponder is just sitting there quietly on my rMBP using 0.1% CPU.
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
[doublepost=1465915940][/doublepost]
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
[doublepost=1465916011][/doublepost]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)
 

flexiboy1912

macrumors member
Original poster
May 13, 2016
73
136
[doublepost=1466183501][/doublepost]Had same problem in MacBook Pro mid 2012. Did PRAM reset and it is running normal now!
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?
 

LuisN

macrumors regular
Mar 30, 2013
199
184
Torres Vedras, Portugal
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?
[doublepost=1466419656][/doublepost]Upgraded from latest El Capitan beta
 

MacsRgr8

macrumors 604
Sep 8, 2002
7,830
1,120
The Netherlands
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.
 

Tomkins!

macrumors regular
Jul 17, 2012
105
17
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.
 
  • Like
Reactions: spencer1208

MacsRgr8

macrumors 604
Sep 8, 2002
7,830
1,120
The Netherlands
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.
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?
 
  • Like
Reactions: spencer1208

Tomkins!

macrumors regular
Jul 17, 2012
105
17
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?
They're probably working on it internally. Maybe they will reintroduce it a few years down the road.
 

Milquetoast

macrumors newbie
Apr 14, 2008
27
7
Maryland
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
[doublepost=1465915940][/doublepost]
[doublepost=1465916011][/doublepost]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)
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???
 
Last edited: