Hello List . I have encountered an odd occurrence in the Availability reports I produce . When i dig to see Full view , i have many entries of "Program restart" (attached below ) , but there are no matching records in the nagios log to indicate a reload or a restart was issues .
Has any one ever experienced such behaviour from nagios previously ? I am using 3.2.0 from source on SLES 10.2 64 bit . Thanks 13-05-2010 00:00:00 13-05-2010 11:41:34 0d 11h 41m 34s SERVICE OK (HARD)HTTP OK: HTTP/1.1 200 OK - 95912 bytes in 0.272 second response time 13-05-2010 11:41:34 13-05-2010 11:41:34 0d 0h 0m 0s PROGRAM (RE)START Program restart 13-05-2010 11:41:34 13-05-2010 11:43:35 0d 0h 2m 1s PROGRAM (RE)START Program start 13-05-2010 11:43:35 13-05-2010 11:43:35 0d 0h 0m 0s PROGRAM (RE)START Program restart 13-05-2010 11:43:35 13-05-2010 12:05:45 0d 0h 22m 10s PROGRAM (RE)START Program start 13-05-2010 12:05:45 13-05-2010 12:05:45 0d 0h 0m 0s PROGRAM (RE)START Program restart 13-05-2010 12:05:45 13-05-2010 12:11:15 0d 0h 5m 30s PROGRAM (RE)START Program start 13-05-2010 12:11:15 13-05-2010 12:11:15 0d 0h 0m 0s PROGRAM (RE)START Program restart 13-05-2010 12:11:15 14-05-2010 00:00:00 0d 11h 48m 45s PROGRAM (RE)START Program start 14-05-2010 00:00:00 14-05-2010 10:26:13 0d 10h 26m 13s SERVICE OK (HARD)HTTP OK: HTTP/1.1 200 OK - 95552 bytes in 0.290 second response time -- Never,Ever Cut A Deal With a Dragon I am doing a Charity Bike ride On the 27 of June for the Capital to Coast Charity. Please help by Donating http://www.justgiving.com/Lovefilm-capital-to-coast ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null