Nagios Support Forum

No, thanks. Pls. go ahead and lock it up.

The "automatic scheduled downtime" seems to provide the expected result, so I'm gonna mark this thread as "solved".

Hi npolovenko, thanks for your reply. Can you share the event handler script with us Not that easily as it contians "internal information", which I first would have to clear off. Again: It's basically the script from Nagios that I had linked previously, enhanced to send mails and to take c...

Hi swarm intelligence, I need your help: Setup: I have an important Web-Service that is supposed to run 24x7 and thus being monitored 24x7. check_interval 2 retry_interval 1 max_check_attempts 3 notification_interval 30 notification_period 24x7 An event handler has been installed and restarts the Ap...

Okay, an uneven amount of starts and stops seems to be explainable: reloading the config forces active downtimes to be re-initiated, see the following example: On Wed, 14 Jun 2017 11:27:13 GMT I scheduled a downtime for 2 minutes, starting at 1497439680 (i.e. Wed, 14 Jun 2017 11:28:00 GMT), see line...

Okay, today's test on my sandbox containing a fixed downtime of 2hrs showed a good result, as well as a single start and stop for the downtime. The error seems to be up -as you guestimated earlier- to multiple starts of a downtime with an unequal amounts of stops. Funny questions are: 1.) What would...

The report still fails with the same result after the upgrade. I will run a new scheduled downtime for 2 hrs for today on my sandbox, that only consists of this single service, in order to keep track of the logs. No idea, why there would be multiple starts and just a single stop. If that's still fai...

hmm... Please take a look e.g. @nagios-04-11-2017-00.log. This is the date, that's mentioned in the detailed description / screenshots. There's an entry that reads [1491812175] SERVICE DOWNTIME ALERT: myhost;my-webapp;STARTED; Service has entered a period of scheduled downtime May be, you've overrea...

As described earlier, the error only occurs, when a scheduled downtime took place during the report time period, so the logfile-format is obviously not an issue.
Setting the "First Assumed Service State" to "Service OK" leads to the same (erroneous) result.

Hi, many thanks again for looking into my issue. I have stripped down the logs to contain only (IMHO) relevant data. This is the data worth a full month and my tests after cleaning up the logs showed the expected "faulty" result. I have additionally attached some more screenshots as well a...