Nagios Support Forum

Dear all,
I am using NagiosCore 3.4.1
I received email alert from NagiosCore like below:

***** Nagios *****

Notification Type: PROBLEM

Service: PING
Host: london-public-ip
Address: ipaddress
State: WARNING

Date/Time: Sat Aug 25 00:24:05 PHT 2012

Additional Info:

PING WARNING - Packet loss = 0%, RTA = 285.54 ms

I wonder that why notification type is warning while the default value is

# 'check-host-alive' command definition
define command{
command_name check-host-alive
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 5000.0,80% -c 8000.0,100% -p 5
}

I read an article about check_ping command on Nagios site :

THRESHOLD is <rta>,<pl>% where <rta> is the round trip average travel
time (ms) which triggers a WARNING or CRITICAL state, and <pl> is the
percentage of packet loss to trigger an alarm state.

So, why Nagios noticed Warning while packet loss =0% only.

Could you please explain to me and advice me how to fix problem

Many thanks for your support,

Trung Le Viet

I think you have fallen into a bit of a beginners trap (I think nearly everyone falls for this one).

check-host-alive and check_ping are not the same thing. So your check-host-alive in your host definition will have a high RTA/PL (as you have shown in the config you provided) but if you look at your PING (check_ping) service definition you will probably see that it is set to something like warning at 250, critical at 500 by default.

I'm hoping that makes sense to you? Sometimes I feel like the PING service should be removed as a default check because this confusion is quite common.

Many thanks for your reply.
In the config file below (this is the defaul vallue)
# 'check-host-alive' command definition
define command{
command_name check-host-alive
command_line $USER1$/check_ping -H $HOSTADDRESS$ -w 5000.0,80% -c 8000.0,100% -p 5
}

And i recorrected service definition for check_ping command to -w 120 and -c 500

Hope that the email alert will be OK with me

Many thanks for your supports!

I think you might have misunderstood, to solve your problem either remove the PING service definition from your hosts or make the check_ping command definition the same as check-host-alive. Otherwise you will get the same notification when it happens next.

Haha, you are true.
Many thanks Jsmurphy; i received the same notifications.
I recorrected to -w 350 and -c 500 and the notificatioins are ok now.

Many thanks for your support, Jsmurphy.

Trung Le Viet