Hi Anthony, 

I am seeing the same effect on my installations. 

When that problem occurs, I also get repeated entries in icinga2.log: 

[2017-10-24 01:15:28 +0000] information/WorkQueue: #8 (IdoPgsqlConnection, 
ido-pgsql) items: 41, rate: 17.1833/s (1031/min 5352/5min 16240/15min); empty 
in 10 seconds

with an incresing estimated time for the WorkQueue to empty. It never does 
(although the DB is working perfectly well, no problems in the database logs at 
all, and I can connect to both the IDO and the Icinga Web 2 database), and the 
situation only clears up when I restart the database. After both Icinga 2 and 
Icinga Web 2 reconnected to the database, everything is OK again. 

Cheers, 

  Peter.

> On 30. Oct 2017, at 00:22, Antony Stone <antony.st...@icinga.open.source.it> 
> wrote:
> 
> 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
> icinga-users@lists.icinga.org
> https://lists.icinga.org/mailman/listinfo/icinga-users

_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to