check_cluster for hosts and warning state not yellow.

[Eric F Crist]

Sounds like a web interface problem.  Keep in mind that 3.0 is still  
not a release.


On Jan 7, 2008, at 10:47 AM, js wrote:

> Hi list,
>
> I'm using Nagios 3.0RC1.
> I'm using the latest check_cluster plugin in order to implement  
> cluster
> logic into Nagios.
> I'm monitoring clustered hosts and NOT services.
> The whole thing seems to work correct but when the clusterhost is in a
> warning state, it is still displayed in GREEN, while that should be  
> YELLOW
> not?
> When the cluster check is critical, Nagios displays the host status  
> RED,
> which is OK.
>
> Here's the verbose output of the plugin.
>
> check_cluster - Warning: start=1 end=1: Critical: start=2 end=2  
> CLUSTER
> WARNING: Host Cluster: 1 up, 1 down, 0 unreachable
>
> Am I missing something?
>
> Cheers, and thanks in advance.
>
>
> Js
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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

-----
Eric F Crist
Secure Computing Networks



-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
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