osx - Radiusd keeps getting restarted by launchd

13
2014-06
  • demet8

    I am reading these errors in the system log file. I have researched this introduction to radius in order to find a solution as to why Radiusd keeps getting restarted by launchd, but I haven't found a solution.

    Has anyone else experienced or solved this issue? btw I am running Mountain Lion on a Macbook Air.

     9/5/12 2:38:51.292 PM com.apple.launchd[1]:
     (org.freeradius.radiusd[3055]) Exited with code: 1 9/5/12 2:38:51.292
     PM com.apple.launchd[1]: (org.freeradius.radiusd[3055]) Exited with
     code: 1 9/5/12 2:38:51.292 PM com.apple.launchd[1]:
     (org.freeradius.radiusd) Throttling respawn: Will start in 10 seconds
     9/5/12 2:38:56.686 PM com.apple.launchd[1]: (org.isc.named[3056])
     Exited with code: 1 9/5/12 2:38:56.686 PM com.apple.launchd[1]:
     (org.isc.named) Throttling respawn: Will start in 10 seconds 9/5/12
     2:39:01.328 PM com.apple.launchd[1]: (org.freeradius.radiusd[3057])
     Exited with code: 1 9/5/12 2:39:01.328 PM com.apple.launchd[1]: 
    
     Process: SleepServicesD [48] Path:
     /System/Library/CoreServices/SleepServicesD Identifier: SleepServicesD
     Version: 1.43 Code Type: X86-64 (Native) Pare
    
  • Answers
  • Spiff

    It looks like FreeRADIUS's radiusd and BIND's named are crashing, and Mac OS X's centralized lazy-launch daemon launchd is configured to keep them alive (restart them if they crash).

    Is your complaint that they're crashing, or is your complaint that launchd is relaunching them? If you don't want them running you could use launchctl(1) to disable their launchd jobs, something like this:

    sudo launchctl unload -w /System/Library/LaunchDaemons/org.freeradius.radiusd.plist
    sudo launchctl unload -w /System/Library/LaunchDaemons/org.isc.named.plist
    

    If your complaint is that they're crashing, the first thing I'd check is to be sure they were properly compiled and installed for Mountain Lion. How did you install them? If you installed them before you upgraded to Mountain Lion, then maybe you need to update them.

    For example, if you installed them via MacPorts, you should probably do:

    sudo port selfupdate
    sudo port upgrade outdated
    

    ...to upgrade ALL of your MacPorts-installed open source software to the latest versions, which have probably been patched for Mountain Lion compatibility by now.

    If you use Homebrew or Fink, there are similar ways to make sure those package managers (and the packages they install) are fully up to date. I'm just not enough of a Homebrew or Fink user to tell you exactly how to do it.


  • Related Question

    osx - MDS Worker Not Found
  • Paul Ferderbar

    I've removed MDS worker (to get rid of spotlight). In my console it looks like launchd is trying to find it. Anyone know how I could stop launchd for searching for spotlight? (ha)

    10-12-10 9:39:27 AM com.apple.launchd[1] (com.apple.metadata.mds[834]) Exited with exit code: 1
    10-12-10 9:39:27 AM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
    10-12-10 9:39:37 AM com.apple.launchd[1] (com.apple.metadata.mds[838]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
    10-12-10 9:39:37 AM com.apple.launchd[1] (com.apple.metadata.mds[838]) Exited with exit code: 1
    10-12-10 9:39:37 AM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
    10-12-10 9:39:47 AM com.apple.launchd[1] (com.apple.metadata.mds[843]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
    10-12-10 9:39:47 AM com.apple.launchd[1] (com.apple.metadata.mds[843]) Exited with exit code: 1
    10-12-10 9:39:47 AM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
    10-12-10 9:39:57 AM com.apple.launchd[1] (com.apple.metadata.mds[844]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
    10-12-10 9:39:57 AM com.apple.launchd[1] (com.apple.metadata.mds[844]) Exited with exit code: 1
    10-12-10 9:39:57 AM com.apple.launchd[1] (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
    10-12-10 9:40:07 AM com.apple.launchd[1] (com.apple.metadata.mds[845]) posix_spawn("/System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Support/mds", ...): No such file or directory
    

  • Related Answers
  • Gordon Davisson

    Another option is to tell launchd to disable the mds daemon:

    sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
    

    (The -w makes the unload operation permanent -- without it, mds will be run again next time you reboot.)

  • Daniel Beck

    Try removing /System/Library/LaunchDaemons/com.apple.metadata.mds.plist.

    Also, you could have just disabled Spotlight:

    sudo mdutil -a -i off