> On 24 Sep 2015, at 23:24, Eric Zounes wrote:
>
> So I just discovered the problem I was having. It won't relay checks back to
> the parent node correctly because the A record pointing at the static NAT
> address is different than the one pointing at the internal address. I'll file
> a bug re
> On 25 Sep 2015, at 09:46, Michael Friedrich
> wrote:
>
>>
>> On 24 Sep 2015, at 23:24, Eric Zounes wrote:
>>
>> So I just discovered the problem I was having. It won't relay checks back to
>> the parent node correctly because the A record pointing at the static NAT
>> address is different t
Hello!
Thank you for your responce.
I enable command feature.
url is
http://localhost/icinga2/dashboard#!/icinga2/monitoring/service/acknowledge-problem?host=custompartsdeport.co&service=check_snmp_storage
Could you help - what additional info i can set or what else i should check,
thank you!
M
Hello All,
For some reason an alert keeps flipping between critical then normal for
the apt service for a single host.
It was a valid alert in the morning, all packages were updated and it
should now be OK. Just like it is now on all other monitored hosts.
Already tried removing the host and rea
Hi guys,
Today I setup an icinga cluster consisting of one master and one satellite
according to the guide in the official documentation [0].
I got through the steps alright and both nodes are up and running but I've
got a problem with the configuration of the zones. I've got the host files
for b
Just a follow-up to this earlier question I had posed. My prior solution was
incorrect.
I have discovered a way in SQL to ignore subsequent HARD recoveries into an
"OK" state that follow any SOFT non-OK states.
The PostgreSQL query (on the icinga_statehistory table) is as follows:
state_type ==
