On Sunday 11 Sep 2016 at 20:18, Jeff Reese wrote: > Hi All, > > I have found that restarting the machine on which my Icinga2 master > instance is installed causes checks to stop until I manually stop the > icinga2 service, delete the /var/lib/icinga2/icinga2.state file, and start > the icinga2 service.
> If I restart the machine, the "Last check" value in icingaweb2 stops > changing and "Next check" will be a negative value that continues to grow. > Performance data stops flowing to graphite. Deleting icinga2.state returns > everything to normal until the next time the machine is restarted. > Any suggestions on where to look next would be greatly appreciated. Maybe a shot in the dark, but are your clock and timezone correct? Are you running NTP to get a good time source for the machine, and is the clock correct when it boots up? I'm just thinking about those negative values for "next check" - does the machine somehow think it's in the future on bootup, and only corrects this by the time you restart icinga2? A check of your /var/log/syslog and/or /var/log/messages should show what date/time the machine thinks it is during various parts of startup. -- Is it venison for dinner again? Oh deer. Please reply to the list; please *don't* CC me. _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users