On Tue, Jan 31, 2012 at 2:03 AM, Claudio Kuenzler
wrote:
> But what's strange in your log are also the missing SOFT states, where are
> they?
>
You're correct, I'm missing some of the SOFT states. I'm going to have to
do some more testing before I can say for sure if there is a bug in either
Nag
Yes, you're right.
But what's strange in your log are also the missing SOFT states, where are
they?
Did you define the service to be checked only once (max_check_attempts 1),
every minute (check_interval and retry_interval 1) ?
Here's an example of a typical soft-to-hard-change:
Jan 31 05:15:09
On Mon, Jan 30, 2012 at 11:39 AM, Claudio Kuenzler
wrote:
> It looks like you use parent-child-relationships?
> That would explain why it's written "Host Unreachable (172.21.10.170) "
> instead of Host Down.
> Was the parent of this host down as well? In this case, Nagios 'knows'
> that it doesn't
It looks like you use parent-child-relationships?
That would explain why it's written "Host Unreachable (172.21.10.170) "
instead of Host Down.
Was the parent of this host down as well? In this case, Nagios 'knows' that
it doesn't make sense to continue checks on the child hosts.
On Mon, Jan 30, 2
Over the weekend I had a weird event happen in my monitoring set. I have a
host that has an Infiniband interface, and we are running the IP protocol
over Infiniband, while using the check_ping plugin to verify network
connectivity. This weekend our Ethernet to Infiniband gateway went down and
the c
