Its actually a web interface inconsistency. The current attempts in
this case actually represents what check # Nagios is currently
"working on". I'll have to modify the CGI code to fix this. Thanks!
On 20 Jan 2003 at 15:20, Pettersson, Magnus wrote:
>
> Ethan.
>
> I have found a minor bug with that when a service goes into a problem state,
> the web-page immediatly displays it as a second failure.
>
> Example.
> I have servicecheck called HTTP, that has a max check attempts of 5.
> When it fails the first check, the web-page states Warning 2/5 instead of
> 1/5.
>
>
> I think this is due to a logic problem in checks.c line 1023 (nagios 1.0),
> where an increment on the value is done, without checking if this is the
> first time the service changes status. Thus it will go from OK 1/5 to
> Warning 2/5 the first time it changes status.
>
>
> At least this is where I *think* the problem lies.
>
> /magnus
> (definitely NOT a c -programmer
>
>
>
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by: FREE SSL Guide from Thawte
> are you planning your Web Server Security? Click here to get a FREE
> Thawte SSL guide and find the answers to all your SSL security issues.
> http://ads.sourceforge.net/cgi-bin/redi ... thaw0026en
> _______________________________________________
> Nagios-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/lis ... gios-devel
>
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]