I am running a distributed monitoring system using Nagios 2.11 on
FreeBSD 6.3. I use NSCA to send host and services events to the central
server from the slave servers and have always had the following problem:
A distributed server notices a host service is non-Ok and fires off
check-host-alive.
On Fri, 16 Jan 2009, Jonathan Call wrote:
I am running a distributed monitoring system using Nagios 2.11 on
FreeBSD 6.3. I use NSCA to send host and services events to the central
server from the slave servers and have always had the following problem:
A distributed server notices a host
-Original Message-
From: Patrick Morris [mailto:patrick.mor...@hp.com]
Sent: Friday, January 16, 2009 11:40 AM
To: Jonathan Call
Cc: nagios-users@lists.sourceforge.net
Subject: Re: [Nagios-users] Hosts report 'DOWN, HARD' after first
attempt.
...
I'm not sure exactly how
On Jan 16, 2009, at 12:40 PM, Patrick Morris wrote:
The max_check_attempts only applies to active checks, not the passive
ones you're sending the central server (at least I assume when you
said
max_retry_interval you meant max_check_attempts) -- and you may note
that SOFT and HARD are
-Original Message-
From: Marc Powell [mailto:m...@ena.com]
Sent: Friday, January 16, 2009 1:20 PM
To: nagios-users Mailinglist
Subject: Re: [Nagios-users] Hosts report 'DOWN, HARD' after first
attempt.
On Jan 16, 2009, at 12:40 PM, Patrick Morris wrote:
The max_check_attempts
On Jan 16, 2009, at 3:15 PM, Jonathan Call wrote:
http://nagios.sourceforge.net/docs/3_0/configmain.html#passive_host_chec
ks_are_soft
If they're all assumed to be SOFT, then a host failure would never
trigger a notification?
My interpretation of the parameter is that passive host results
