Hi,
did you define a cluster check on your master?
object Service "cluster" {
check_command = "cluster"
check_interval = 60s
retry_interval = 10s
host_name = "your icinga master"
}
This reports problems with the satellite Icinga processes.
Regards
Volker
> Am 30.10.2017 um 00:22 schrieb Antony Stone
> <[email protected]>:
>
> Hi.
>
> I have 1 master Icinga2 plus 3 satellites. All machines run Icingaweb2; the
> 3
> satellites only show results from their local networks, the master shows
> everything.
>
> If the Icinga2 monitoring process stops on one of the satellites, the
> Icingaweb2 on that machine shows an alert under "System - Monitoring Health"
> saying "Backend icinga is not running", however nothing is shown on the
> master
> Icingaweb2 display - all information from that satellite is simply stuck at
> the last known values, with no indication that communications are no longer
> occurring.
>
> If you look (on the master) in detail at any of the service checks, you can
> see when they last ran, and that the next scheduled run is some time in the
> past, but unless you look for it, nothing stands out to say "Icinga2 on
> satellite X is not contactable".
>
> Have I missed some standard part of the master-satellite setup, or if not,
> what's the recommended way to have the master machine report when a satellite
> stops reporting check results?
>
> The host itself is not down; it's just that the icinga2 process is not
> running, but of course that means any service check to see whether a process
> is running is not running either, so it can't report a process not running...
>
>
> Thanks,
>
>
> Antony.
>
> --
> This sentence contains exacly three erors.
>
> Please reply to the list;
> please *don't* CC me.
> _______________________________________________
> icinga-users mailing list
> [email protected]
> https://lists.icinga.org/mailman/listinfo/icinga-users
>
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
