From: <joe...@va...> - 2013-05-02 11:28:54
|
Back in February our nagios host was shut down for almost 40 minutes. From my alert log: [02-06-2013 13:39:54] Nagios 3.4.4 starting... (PID=3687) [02-06-2013 13:01:17] Caught SIGTERM, shutting down... However looking at availability reports for this time period (e.g. 1st Feb -> 28th Feb) the row "Nagios Not Running" is set to "0d 0h 0m 0s 0.000%". In fact the entire "Undetermined" block is set to 0%. Is this a bug? Am I doing something wrong? P.s. Although it was 3.4.4 back in Feb, we are now running 3.5.0 |
From: Andreas E. <ae...@op...> - 2013-05-02 22:08:30
|
On 2013-05-02 13:15, joe...@va... wrote: > Back in February our nagios host was shut down for almost 40 minutes. > >>From my alert log: > > [02-06-2013 13:39:54] Nagios 3.4.4 starting... (PID=3687) > [02-06-2013 13:01:17] Caught SIGTERM, shutting down... > > However looking at availability reports for this time period (e.g. 1st > Feb -> 28th Feb) the row "Nagios Not Running" is set to "0d 0h 0m 0s > 0.000%". > > In fact the entire "Undetermined" block is set to 0%. > > Is this a bug? Am I doing something wrong? > Are you using the "guess states during program downtime" thingie? If so, 0% undetermined makes perfect sense. -- Andreas Ericsson and...@op... OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. |