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.

I have a fresh install of r2.5.4-1 on Ubuntu Server 16.04.1 via
ppa:formorer/icinga.  Other installations on same server are icingaweb2,
graphite-api, and grafana.  No satellites, hosts, services, etc. have been
added.  I only have default, out of the box monitoring of localhost.  Setup
was exhaustively documented if that helps.

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.

I'm not seeing an errors in icinga2.err and the only reference to
icinga2.state in icinga2.log is "Dumping program state to file
'/var/lib/icinga2/icinga2.state'".

There are some previous mailing list messages and bug reports about parsing
errors related to the state file but I'm not seeing any such parsing errors
in the log.  It might be that I just don't have the appropriate logging
enabled.  I'm relatively new to Icinga2.

Any suggestions on where to look next would be greatly appreciated.
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to