mDNSResponder error at start up 10.5.5

Discussion in 'macOS' started by rpaloalto, Sep 16, 2008.

  1. rpaloalto macrumors 6502a

    rpaloalto

    Joined:
    Sep 19, 2005
    Location:
    Palo Alto CA.
    #1
    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?

    [​IMG]

    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
     

    Attached Files:

  2. rpaloalto thread starter macrumors 6502a

    rpaloalto

    Joined:
    Sep 19, 2005
    Location:
    Palo Alto CA.
    #2
    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.
     
  3. TheJackal macrumors member

    Joined:
    Mar 15, 2008
    #3
    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
     
  4. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #4
    Same messages for me

    Same for me on both my Mac Pro and MacBook.

    Both went from 10.5.4 to 10.5.5. The Mac Pro used the combo updater, the MacBook used the software update.

    Anyone have any clue on what these mean? I think mDNSResponder has to do with Bonjour.
    http://developer.apple.com/opensource/internet/bonjour.html

    -Kevin
     
  5. rpaloalto thread starter macrumors 6502a

    rpaloalto

    Joined:
    Sep 19, 2005
    Location:
    Palo Alto CA.
    #5
    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.
     
  6. codeyh macrumors newbie

    Joined:
    Sep 16, 2008
    Location:
    Nashville
    #6
    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.
     
  7. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #7
    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
     
  8. codeyh macrumors newbie

    Joined:
    Sep 16, 2008
    Location:
    Nashville
    #8
    Maybe unrelated then. regardless, error still present.
     
  9. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #9
    Could still be related....who knows :confused: My printer is connected via a Time Capsule....not shared through another Mac.

    -Kevin
     
  10. UselessObserver macrumors newbie

    Joined:
    Jul 17, 2007
    #10
    Im getting the same thing...

    Anyone solved this yet?
     
  11. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #11

    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
     
  12. rpaloalto thread starter macrumors 6502a

    rpaloalto

    Joined:
    Sep 19, 2005
    Location:
    Palo Alto CA.
    #12
    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. :)
     
  13. netnothing macrumors 68040

    netnothing

    Joined:
    Mar 13, 2007
    Location:
    NH
    #13
    Thank UselessObserver.....only reason I remembered was because he added a post :D

    -Kevin
     
  14. UselessObserver macrumors newbie

    Joined:
    Jul 17, 2007

Share This Page