Bjoern Beutel wrote:
> Hello,
>
> on May 29th, Tony den Haan wrote:
>> 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.
>
> Ethan Galstad answered:
>> 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.
>
> We had the same problem at work, which was quite acute since it woke up our call-on
> duty during night-time several times per month.
> So I added an option "-u" (uncritical timeout) to "check_nrpe.c",
> which makes check_nrpe.c return STATUS_UNKNOWN in alarm_handler().
> See below for the diffs.
>
> Best regards,
>
> Björn Beutel
>
Thanks for the patch Bjorn. I applied it with just a few minor changes
and it will appear in CVS shortly.
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]