getting warnings for connection refused with check_nrpe instead of critical

[Klaus Umbach]

On 26/02/09 12:06, Lee Azzarello wrote:
> On Thu, Feb 26, 2009 at 5:21 AM, Klaus Umbach
> <treibholz at sozial-inkompetent.de> wrote:
> > Hi,
> >
> > I have a problem with unstable lines and/or machines under stress.
> >
> > Sometimes they just don't reply on nrpe, but are still working, so I get a
> > lot of false alarms. Is it possible, to tell check_nrpe to exit with a
> > warning instead of critical?
> 
> I believe that a state of "socket timeout" will always be flagged as
> "critical", though you can increase the max_check_attempts so it won't
> throw a notification so soon if you know of false positives.

Sometimes these periods last for a an hour so, on some machines it's
because of shitty connections to another continent or in countries with
unstable infrastructure.

> Of course figuring out the cause of your false positives is probably
> the better solution.

Most of time I know the cause, but it is not solvable in a cheap way :-)
The relevant services are still working, but if the monitored values pass
the thresholds, I want to know it, not if connection fails.

Cheers
	Klaus

-- 
BOFH excuse #159:

Stubborn processes

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
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