On 8/7/2012 8:33 AM, Andreas M. Iwanowski wrote:
I.e. if the primary gateway goes down and the standby takes over, I
would still like to be notified about host troubles behind the VPN. Only
if both were to be down nagios should stop sending messages.
Would setting parent/child relationships,
Hi all
Sometime happen that when I set active_checks_enabled 0 in a service
and reload the configuration, Nagios did not recognize the instruction.
The server still executes the check.
It is very strange, because I use several Nagios servers since 2003 and it
is the first time for me
Where did you set the directive ? in a template or in the individual
service ?
Can you share the relevant configuration data ?
On 08/08/12 14:16, Marco Borsani wrote:
Hi all
Sometime happen that when I set active_checks_enabled 0 in a
service and reload the configuration, Nagios did
On 08/08/2012 03:16 PM, Marco Borsani wrote:
Hi all
Sometime happen that when I set active_checks_enabled 0 in a service
and reload the configuration, Nagios did not recognize the instruction.
The server still executes the check.
It happens if you have enabled state retention
I set in the individual service.
define service {
host_name HOST
service_description Admin_Modem_PROCS
is_volatile0
check_commandcheck_modem_procs
Hi
1) state retention data enabled = YES (we need for maintain past data)
2) disable active checks from the webinterface = NO ( I delete many external
command in the web interface, I left only acknowledge and scheduled
downtime)
I change directly the parameters in the cfg files and
Thank you Chris!
This sounds great
So as I understand, if I define a parent-child relationship between the VPN
services (or core gateways) on the parent side and the remote gateway on the
other side, the remote gateway will be checked (and we notified) as long as one
core gateway is online?
