Nagios Support Forum

Thanks for the suggestion of SleepWatcher -- hadn't heard of it before; looks like a nifty tool for side-stepping the problem. Re: sleep duration, our developers are typically seeing it when they close the laptop and go home or come back into the office -- so at least a ~20 minute sleep period, but ...

Hmm. OS X API stuff is above my pay grade, but presumably there must be an API for registering for a call-back for system suspension/sleep. Seems like overkill. I don't think the underlying bug is caused by the system having been in hibernation, just that resuming from sleep happens to trigger a con...

Thanks!

The issue we're seeing is on single nodes -- Nagios running on OS X (on a dev laptop) checking services only on the same node -- e.g. all localhost.

Thanks! I'm happy to send in a bug report / patch, just didn't see where to do it.

-Jeff

Yes, fixing the '='/'==' error enables compiling of Nagios 4.0.8 on OS X. (But not sure if 4.0.8 fixes the load issues on OS X.) Nagios 4.0.8, as released, has a bug in it (using assignment "=" in place of comparison "==") that prevents it from compiling on OS X. The block of cod...

Hi abrist, I tried compiling 4.0.8 for OS X, but get the below error (and two warnings nearby) -- it looks like a missing '=' in what presumably should be "== -1"? runcmd.c:590:50: error: expression is not assignable if (asprintf(&env_string, "%s=%s", name, value) = -1) retur...

Sorry; just realized I didn't have "notify me when a reply is posted" checked on. The debugging info I pasted there was from dtruss'ing the process and from attaching lldb debugger to it. There's no error messages to speak off -- the process simply goes to 100% of CPU and burns cycles (and...

Oh, I forgot one important detail: we almost always see this happening after waking the laptops from sleep.

We're seeing similar issues as described in this post -- on multiple of our developer's OS X 10.9 boxes. Reverting to 3.5 solves it. When this happens, there are multiple nagios processes running at high CPU, like they're worker processes about to exec a plugin, or worker processes managing a plugin...