wrong readings given by nagios

Marc Powell marc at ena.com
Wed Mar 16 17:25:41 CET 2005



> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of vivek sharma sharma
> Sent: Wednesday, March 16, 2005 6:10 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] wrong readings given by nagios
> 
>   Dear all,
>         I am using following command to check service::
> 
> command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 450.0,40% -c
> 1000.0,98%
> 
> 
> I think this means give a warning when the loss goes to 40% with
latency
> upto 450ms
> and give the status as critical when loss is 98% over latency 1000

Almost, but not quite. The service will be in WARNING when the RTA is
between 450 and 999 ms _or_ the packet loss is between 40% and 98%. The
service will be CRITICAL when the RTA exceeds 1000 ms _or_ the packet
loss is 98% or greater.

> but still it shows it like this::
> 
> HYD-CORE check_ping WARNING 03-16-2005 17:27:36 0d 0h 8m 5s 2/3 PING
> WARNING - Packet loss = 28%, RTA = 147.91 ms
> 
> HYD-MERADPALLY check_ping WARNING 03-16-2005 17:25:17 0d 0h 3m 12s 1/3
> PING WARNING - Packet loss = 37%, RTA = 300.96 ms
> 
> MUM-CORE check_ping WARNING 03-16-2005 17:21:44 0d 0h 6m 45s 1/3 PING
> WARNING - Packet loss = 44%, RTA = 55.74 ms
> 
> MUM-NETMAGIC check_ping WARNING 03-16-2005 17:21:44 0d 0h 22m 48s 3/3
PING
> WARNING - Packet loss = 28%, RTA = 63.22 ms
> 
> This shows that it is giving warning even when rta is less than 450ms
and
> less than 40% loss
> 

Are you sure you're using the command above? Can you post the complete
command, service and host definitions for one of the hosts above
(HYD-CORE for example)? Was the command previously different than what
you have above? Do you have multiple nagios daemons running?
 
> My requirement is for 100% loss only it should show it as critical but
> what latency should i keep then and also in the n/w the
> latency can go upto anything like 1600ms also.Plz suggest b'cos i want
> reports of a service going totally down and nothing else.

You should choose a latency that is acceptable on your network. I use a
critical latency of 1000ms because that indicates a significant problem
on my network but it sounds like you need a value that's much higher
than that (1600-2000ms possibly).
 
--
marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
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





More information about the Users mailing list