Nagios Support Forum

At the moment I manage the situation in this way

When a monitored server has to do a scheduled boot sends a input to nagios by send_nsca , then waits 1 minute
before to run the reboot.

This event sent by send_nsca starts a nagios EventHandler .
This event handler is linked to a unix script that sends to nagios command
SCHEDULE_FORCED_HOST_CHECK
SCHEDULE_FORCED_HOST_SVC_CHECKS

these command move 15 minutes forward the next checks .. but ....
these command ignore the check_period , and to force the checks .
So I got some FALSE CRITICAL services status
Just for example
check_period is configure to check from 8am to 9pm
The server reboots to 3 am
On this host I check discs , memory , cpu and some windows services
The checked windows services are down during the nigth but the SCHEDULE_FORCED_HOST_SVC_CHECKS
creates the CRITICAL STATUS on Nagios console.

I attempt to substitue the SCHEDULE_FORCED command by SCHEDULE_HOST_DOWNTIME
and SCHEDULE_HOST_SVC_DOWNTIME but the situation doesn't change because the during
the DOWNTIME the checks work however .
So if during the server reboots , nagios checks the memory we
got a false CRITICAL status (I say false because the boot is scheduled so the problem is not a true problem)

My need is to find a commad or solution to suspend checks during scheduled situation (as a boot) without
generate FALSE allarms

Many thanks for your help
Emilio

Would it work to temporarily disable active checks during the reboot?

I'm assuming the reason you don't want to use scheduled downtime is because it would affect an availability report? If not, downtime is still the best option.