A normal problem in my setup:
One host get a too high load. This will time out the nrpe checks, giving=20
me 5-10 sms for the timeout, and then (2 minutes later) the same sms for=20
OK. The host isn't down, it's just in a very busy state, and I know this=20
since I don't get a host down message. If I change the check-host-alive=20
to nrpe I will then get a host down message, which can mean anything=20
from high load, host is unreachable or host is actually down. Host down=20
=3D I have to drop everything and get to work, High Load =3D let's give i=
t a=20
minute to cool down first.
I could do the same as =D8ysten Bleie suggest, but I'm not sure that's=20
good either. Actually I'm not sure what's best to do, so I've for the=20
moment stuck with all the sms.
Vegard
sean finney wrote:
>hi,
>
>On Fri, Apr 21, 2006 at 09:30:56AM +0200, [email protected] w=
rote:
> =20
>
>>If for some reason nrpe stops ( perhaps by mistake ) we get a CRITICAL =
message for each and every check on that particular host -
>>
>>Of course this may be due to a misconfiguration on our site but I seem =
to be unable to pin point exactly what we have misconfigured.
>> =20
>>
>
>i think the general consensus is that this is the way things are
>supposed to be. general consensus: please correct me if i
>am mistaken
a similar analogy would be check_http failing>to retrieve a specific URL if a web server were down.
>
>if you'd like to have a host w/nrpe show up as "down" if nrpe
>is not running, i would suggest to use some invokation of
>check_nrpe or check_tcp as the check_host_alive definition
>for such hosts.
>
>
>
> sean
> =20
>
--=20
Mvh / Kind regards
Vegard Hanssen
Xait A/S
[email protected]
For general enquiries please call Xait support at: +47 51 95 02 13
CONFIDENTIALITY. This e-mail and any attachments are confidential
and may also be privileged. If you are not the named recipient,
please notify the sender immediately and do not disclose the
contents to another person, use it for any purpose, or store
or copy the information in any medium.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]