check_cluster - Wrong service state

[Jim Avery]

On 24 February 2010 11:27, Brandino Andreas <ampranti at gmail.com> wrote:
> Hi all,
>
> I configured check_cluster plugin to monitor two services that work
> redundant (1 is up, 1 is down all the time).
>
> The plugin that check the services, returns "UNKNOWN" state for the
> service that are down. However, "check_cluster" return that both
> services are "OK" (CLUSTER OK: Disk-Cluster: 2 ok, 0 warning, 0
> unknown, 0 critical).
>
> Which can possible reasons for detecting incorrectly  the state of
> the services?


The syntax for check_cluster is quite subtle and not obvious.

I confess I don't use check_cluster for service checks, but I do for
host checks.

An example which I use for a pair of hosts is:

In the command definition:

command_line    $USER1$/check_cluster --host -l $ARG1$ -w $ARG2$ -c
$ARG3$ -d $ARG4$

And in the host definition:

check_command   check_host_cluster!"Storage
Server"!0!1!$HOSTSTATEID:ds4100y1a$,$HOSTSTATEID:ds4100y1b$

In my example I want to have a warning state if one of the two hosts
is down and have a critical state if both are down.


The important point to note is that the warning and critical
thresholds are set according to the documentation at

http://nagiosplug.sourceforge.net/developer-guidelines.html#THRESHOLDFORMAT

It can take a while to work out precisely how to set -w and -c to
achieve the result you want.

hth,

Jim

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null