[icinga-users] Problems with using send_nsca
whitetr6 at gmail.com
Thu Feb 16 17:01:29 CET 2012
We have a jobs script that runs nightly on one of our production servers.
For each task that happens in the script, there is a send_nsca command
which in turn updates the Icinga server. Icinga has services defined for
each of these, as a passive. Each one looks something like this:
service_is_stale.sh looks like this:
/bin/echo "CRITICAL: No Current Results for this Service"
The problem I'm having is this: when the script runs nightly and all of the
alerts get updated, I'm expecting them to stay that way for the 90,000
second timeout defined in the service description. However, they do not
wait that long, and will all go critical before the next night's run. I
should also explain why I did 90,000, since that may be part of my problem.
90,000 seconds is 25 hours, or one hour later than the next time the job
should run. My understanding of the send_nsca process is that the timer
will restart once a message is received. So if the message is received by
11:15 PM, the 90,000 seconds will start then, and Icinga should not show
this service as critical unless no new message is received by 12:15 AM the
I would really rather use a method where each service checks at an exact
time (active) rather than wait for a timeout (passive). I'd be open to any
other suggestions, or if it looks like I'm not using send_nsca and passive
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the icinga-users