Re: [Nagios-devel] nagios_check_command issue
Posted: Thu Jun 09, 2005 12:36 am
Dmitry Sivachenko wrote:
> Hello!
>
> The usage of check_nagios_command was removed in rev. 1.31 of cgiutils.c.
>
> Now we have the situation when 'check_nagios_command' variable is
> documented, it's value is read by CGIs but it is not used at all.
>
> And we have no chance to notice via web interface that nagios process received
> SIGSEGV and died! We continue to monitor services and are happy that they
> are working properly (in fact, they are just not monitored).
>
> Why this was done?
>
Because the check was broken.
> Are there any plans to restore functionality that was present in nagios-1.x?
>
Not that I know of. It should be fairly simple to add a check for mtime
on the status.dat file and warn if it's higher than some predetermined
value though.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Lead Developer
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> Hello!
>
> The usage of check_nagios_command was removed in rev. 1.31 of cgiutils.c.
>
> Now we have the situation when 'check_nagios_command' variable is
> documented, it's value is read by CGIs but it is not used at all.
>
> And we have no chance to notice via web interface that nagios process received
> SIGSEGV and died! We continue to monitor services and are happy that they
> are working properly (in fact, they are just not monitored).
>
> Why this was done?
>
Because the check was broken.
> Are there any plans to restore functionality that was present in nagios-1.x?
>
Not that I know of. It should be fairly simple to add a check for mtime
on the status.dat file and warn if it's higher than some predetermined
value though.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Lead Developer
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]