[patch] Workaround for 'Host DOWN' false-positives

[Jan Kratochvil]

Hi Joerg,

On Sun, 21 May 2006 16:08:40 +0200, Joerg Linge wrote:
...
>         command_line    $USER1$/check_dummy $ARG1$ "$ARG2$"
...
>         check_command           check-host-adaptive!$SERVICESTATEID:server1:Connectivity$!$SERVICEOUTPUT:server1:Connectivity
...
> In this way the host check_command produces the same state as the
> "Connectivity" Service on the same Host.

This looks very clever and it would be mostly the right workaround, still...

...
> This ist still a quick hack, but it works ;-)
> This is IMHO the fastest way without parsing status.dat.

Do you have it tested? I do not think it will work. The goal is to reflect the
field "last_hard_state", not the field "current_state". "SERVICESTATEID"
unfortunately corresponds to "current_state" while "last_hard_state" has no
corresponding macro.

If you think about the problem, its goal was to delay the host-status-change
after stabilizing the state in many attempts, this goal has no opportunity to
use the immediately changing "current_state" field. In fact my first version of
the Perl script was using "current_state" and IRL it just did not work.

It would be fine to provide macro for "last_hard_state" in the next release.



Regards,
Lace


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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