Hello, I'm currently running an Icinga2 (v2.4.7) instance in parallel to my existing Icinga1 in order to test the former before switching over to it from the latter. In both cases I use the Classic web UI (the one that comes standard with Icinga1).
I have noticed that whenever I restart my Icinga2 instance (using systemd on ArchLinux) the Event Log in my Classic UI shows a load of checks in either DOWN or UNKNOWN states with the mention "<Terminated by signal 15 (Terminated).>" This basically lights up the Classic UI like a Christmas tree until the checks are redone following the restart and everything quickly becomes green again. My Icinga1 does not exhibit this behavior in the UI whenever I restart the process. The Icinga Classic UI behavior with regards to an Icinga2 restart is very misleading as for a short time it suggests there is an overall problem in the network (I use Icinga to test our network nodes), even if only for a short time. Should this combined Icinga2/Classic UI behaviour be considered: 1) A less-than-ideal but perfectly normal and expected behaviour from this combo, or 2) A bug, or 3) A configuration mistake on my part? Thanks! -Martin
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
