Re: [Nagios-devel] check_nrpe timeout triggering criticial service
Posted: Tue May 30, 2006 9:03 am
Tony den Haan wrote:
> hi,
>
> I ran into nagios mailing me CRITICALs when it couldn't connect to remote
> nrpe daemon. This looks a bit strange, since it couldn't possible know if
> a filesystem if full or whatever when it can't query daemon.
> I suggest making check_nrpe return STATUS_UNKNOWN in alarm_handler(),
> instead of STATUS_CRITICAL.
> Another option might be having a service check on the remote nrpe and use
> dependencies?
> Which solution is wise?
>
> Tony
>
I'll put this on my TODO list for NRPE. I'll add a command line option
that will allow either CRITICAL or UNKNOWN on timeouts for check_nrpe.
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]
> hi,
>
> I ran into nagios mailing me CRITICALs when it couldn't connect to remote
> nrpe daemon. This looks a bit strange, since it couldn't possible know if
> a filesystem if full or whatever when it can't query daemon.
> I suggest making check_nrpe return STATUS_UNKNOWN in alarm_handler(),
> instead of STATUS_CRITICAL.
> Another option might be having a service check on the remote nrpe and use
> dependencies?
> Which solution is wise?
>
> Tony
>
I'll put this on my TODO list for NRPE. I'll add a command line option
that will allow either CRITICAL or UNKNOWN on timeouts for check_nrpe.
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]