Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

mDNSResponder error at start up 10.5.5

rpaloalto

rpaloalto

macrumors 6502a
Original poster
Sep 19, 2005
733
2
Palo Alto CA.
I installed 10.5.5 and now I have this in my console at start up. does any one else get this.
I already repaired permissions. Should I worry?

attachment.php


9/15/08 8:54:34 PM mDNSResponder[21] WARNING: sandbox_init error Could not set Mach lookup policy for service com.apple.bsd.dirhelper err=1100Could not set Mach lookup policy for service com.apple.distributed_notifications.2 err=1100Could not set Mach lookup policy for service com.apple.ocspd err=1100Could not set Mach lookup policy for service com.apple.mDNSResponderHelper err=1100Could not set Mach lookup policy for service com.apple.SecurityServer err=1100Could not set Mach lookup policy for service com.apple.SystemConfiguration.configd er
 

Attachments

  • Picture 3.png
    Picture 3.png
    10.1 KB · Views: 5,806
Well I just got home from work. Rebooted my mac, and I still get this in the console log at start up. Now I'm worried. No one else is getting it.

It wasn't their before because when I look at my start up log before the 10.5.5 update it's not their.

Does any one know what it means. Has anyone looked in their console start up log after a reboot.
 
Hi,

I'm getting the exact same error as you....

Sep 16 20:53:45 localhost mDNSResponder mDNSResponder-176.2 (Aug 15 2008 14:58:54)[16]: starting
Sep 16 20:53:47 localhost mDNSResponder[16]: WARNING: sandbox_init error Could not set Mach lookup policy for service com.apple.bsd.dirhelper err=1100Could not set Mach lookup policy for service com.apple.distributed_notifications.2 err=1100Could not set Mach lookup policy for service com.apple.ocspd err=1100Could not set Mach lookup policy for service com.apple.mDNSResponderHelper err=1100Could not set Mach lookup policy for service com.apple.SecurityServer err=1100Could not set Mach lookup policy for service com.apple.SystemConfiguration.configd
 
Thanks for your response
It may or may not be a issue. At least I know that I'm not the only one.

I even did a full erase and reinstall, not on my main boot drive, but on my number 2 hard drive. I installed 10.5.2 Repaired permissions, then installed the 10.5.5 combo updater. Still shows up.
 
not the only one

I'm getting it too... as a result, I can't see AFP share or shared printer.

assuming it's related.
 
codeyh said:
I'm getting it too... as a result, I can't see AFP share or shared printer.

assuming it's related.
Click to expand...

Interesting....I'm able to see both of my Macs on the network and I can still print to my printer which is attached to a Time Capsule.

-Kevin
 
Im getting the same thing...

10/10/2008 18:01:38 mDNSResponder[23] WARNING: sandbox_init error Could not set Mach lookup policy for service com.apple.bsd.dirhelper err=1100Could not set Mach lookup policy for service com.apple.distributed_notifications.2 err=1100Could not set Mach lookup policy for service com.apple.ocspd err=1100Could not set Mach lookup policy for service com.apple.mDNSResponderHelper err=1100Could not set Mach lookup policy for service com.apple.SecurityServer err=1100Could not set Mach lookup policy for service com.apple.SystemConfiguration.configd er
Click to expand...

Anyone solved this yet?
 
UselessObserver said:
Im getting the same thing...

Anyone solved this yet?
Click to expand...


Have you applied yesterdays Security Update 2008-007 yet? I'm not sure, but I think that may have fixed it for me. I can't restart my Mac Pro right now, but looking back in my logs, I don't see the message since the Security Update 2008-007.

Rebooting my MacBook......and I don't see the error anymore.

Anyone else not seeing it after the update?

-Kevin
 
Yes kbmb, it is gone. I didn't even think to check. I guess since it was not causing any problems, for my mac. I had just ignored it.

Thanks kbmb for remembering and updating this post. :)
 
rpaloalto said:
Yes kbmb, it is gone. I didn't even think to check. I guess since it was not causing any problems, for my mac. I had just ignored it.

Thanks kbmb for remembering and updating this post. :)
Click to expand...

Thank UselessObserver.....only reason I remembered was because he added a post :D

-Kevin
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back