I am currently in the process of setting up an Icinga2 environment that is planned to house quite a few zones that are handled by satellites in the future. I am currently running the master, a zone and satellite for the in-office infrastructure and a RaspberryPi 5 m.2 als a testsatellite with it’s own test zone, the check command on both host templates for the respective satellites is cluster-zone.
I set up and integrated the zones and satellites as described here by Michael Johnson and the checks within the zone all seem fine, the check source for hostalive checks within the testzone is the RasberryPi as it shuld be, the master sees the testsatellite with the icinga cluster check, but when I power down the Raspberry Pi the check just goes Overdue and never critical.
In the attached picture it seems that the scheduling and check source for the satellite is the satellite itself and not the master as it should logically be for this check.
My question now is where I went wrong. Is this a limitation with the linked method of deploying satellites or did I mess up somewhere? If this is a limitation with the former method will the “manual” way of editing the zones.conf, running the node wizzard on the satellite and then the Kickstart Agent again in Director as discribed in this Blog solve this issue for good?
- Director version (System - About): 1.11.5
- Icinga Web 2 version and modules (System - About): 2.12.5
- Icinga 2 version (
icinga2 --version): 2.15.0-1 - Operating System and version: Debian 12
- Webserver, PHP versions: