simple config - check_ping ignores parameters?

Jim Cheetham jim.cheetham at ecosm.com
Sun Feb 15 22:06:30 CET 2004


On Sat, 2004-02-14 at 07:40, Subhendu Ghosh wrote:
> On Fri, 13 Feb 2004, Jim Cheetham wrote:
> 
> > Hi, I've just installed nagios from Debian packages (nagios-text
> > 1.1-9.backports.org.1), and given it what I hoped was a simple config to
> > get used to the program ...
> > 
> > I've put in a number of hosts that should use check-host-alive, which I
> > believe is a very generous ping test (5000ms?)
> > 
> > I've also added a ping service for these hosts, and they are generally
> > responding as OK.
> > 
> > However, a set of them are over 100ms away from me, (between 150 and 250
> > ms) and generated critical errors (I was expecting warning messages?).
> > 
> > I edited services.cfg to give these services a new threshold
> > (check_command check_ping!300.0,20%!800.0,60%) and restarted (both with
> > the same service_description, and with a different one, in case that
> > helped), but these changes do not seem to have come into action, I'm
> > still seeing a critical service error.
> > 
> > So, where do I need to look to get the behaviour I'm expecting?
> > i.e.
> > 	Warnings, not criticals
> > 	More appropriate thresholds for these services

> posting snippets of config would help debug...

Very well ...

hosts.cfg (comments stripped)
---------
define host{
        name                            ecosm-host
        notifications_enabled           1
        event_handler_enabled           0
        flap_detection_enabled          1
        process_perf_data               1 
        retain_status_information       1
        retain_nonstatus_information    1
        register                        0
        }
define host{
        use                     ecosm-host
        host_name               gaku.ecosm.com
        alias                   gaku.ecosm.com
        address                 69.59.157.40
        check_command           check-host-alive
        max_check_attempts      10
        notification_interval   60
        notification_period     24x7
        notification_options    d,u,r
        }

checkcommands.cfg
-----------------
define command {
                command_name    check-host-alive
                command_line    /usr/lib/netsaint/plugins/check_ping -H
$HOSTADDRESS$ -w 5000,100% -c 5000,100% -p 1
                }


services.cfg
------------
define service{
        name                            ecosm-service
        active_checks_enabled           1
        passive_checks_enabled          1
        parallelize_check               1
        obsess_over_service             1
        check_freshness                 0
        notifications_enabled           1
        event_handler_enabled           0
        flap_detection_enabled          1
        process_perf_data               1
        retain_status_information       1
        retain_nonstatus_information    1
        register                        0
        }
define service{
        use                             ecosm-service       
	host_name                       gaku.ecosm.com
        service_description             PING
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           5
        retry_check_interval            1
        contact_groups                  admins
        notification_interval           240
        notification_period             24x7
        notification_options            c,r
        check_command                   check_ping!300.0,20%!800.0,60%
        }

From the web interface :-
Host details for gaku.ecosm.com (all seems OK here)
------------
Host Status:		UP    
Status Information:	PING OK - Packet loss = 0%, RTA = 166.80 ms	
Last Status Check:	2004-02-14 02:53:20	
Status Data Age:	2d 7h 9m 14s	
Last State Change:	2004-02-13 12:14:18	
Current State Duration:	2d 21h 48m 16s	
Last Host Notification:	N/A	
Current Notification Number:  	0  	
Is This Host Flapping?	N/A	
Percent State Change:	N/A	
In Scheduled Downtime?	NO  
Last Update:	2004-02-14 02:54:00

Service details for PING on gaku.ecosm.com
---------------
Current Status:		CRITICAL  (Has been acknowledged)  
Status Information:	PING CRITICAL - Packet loss = 0%, RTA = 166.90 ms	
Current Attempt:	3/3	
State Type:	HARD	
Last Check Type:	ACTIVE	
Last Check Time:	2004-02-14 02:53:10	
Status Data Age:	2d 7h 11m 33s	
Next Scheduled Active Check:  	2004-02-14 02:58:10	
Latency:	< 1 second	
Check Duration:	5 seconds	
Last State Change:	2004-02-13 12:16:24	
Current State Duration:	2d 21h 48m 19s	
Last Service Notification:	2004-02-13 12:16:24	
Current Notification Number:	1	
Is This Service Flapping?	N/A	
Percent State Change:	N/A	
In Scheduled Downtime?	NO  
Last Update:	2004-02-14 02:54:00
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040216/1425e3c0/attachment.sig>


More information about the Users mailing list