Hi,
> Can you run sudo icinga2 object list --name *hostname\!servicename* on
> the agent and make sure the files listed are configured properly?
That hint was helpful, thanks. I found out that Icinga was using the
example configuration for a service with the same name; I had to exclude the
conf
Message-
From: icinga-users [mailto:icinga-users-boun...@lists.icinga.org] On Behalf Of
Dominik George
Sent: Wednesday, August 8, 2018 10:53 AM
To: Icinga User's Corner
Subject: Re: [icinga-users] Service check not updated on agent (or so)
Hi,
On Wed, Aug 08, 2018 at 01:16:21PM +0200, V
Hi,
On Wed, Aug 08, 2018 at 01:16:21PM +0200, Václav Mach wrote:
> My guess is, that your master node has new configuration while the client
> does not. When you force run the check by "check now" the client only gets
> the check command along with parameters. When running by regular schedule,
> i
Hi Nik,
> I recently changed the parameters of this check (adding an ignored
> filesystem). When I click "Check now", the check is run with the correct
> parameters and returns OK. But if the check is run in Icinga's regular
> schedule, it returns CRITICAL because it is still running with the o
Hi,
On 08/07/2018 12:12 AM, Dominik George wrote:
Hi,
I have a configuration where some checks (in this case check_disk) are
executed on an Icinga agent running on the checked host. The setup is
configured with Icinga Director.
I recently changed the parameters of this check (adding an ignore
Hi,
I have a configuration where some checks (in this case check_disk) are
executed on an Icinga agent running on the checked host. The setup is
configured with Icinga Director.
I recently changed the parameters of this check (adding an ignored
filesystem). When I click "Check now", the check i
