Status: Unknown

[Darren Bentley]

Thanks for the help,

Turns out I'm a dumbass...ping wasn't SUID root.

It's all good now.

- Darren

On Fri, 2003-01-03 at 01:09, Steve Freegard wrote:
> Darren,
> 
> It sounds like a configuration error somewhere, have a look at your configs
> - I've attached a couple of examples that you can use to check.
> 
> For example:
> 
> define service{
>  use                            default_service
>  hostgroup_name                 nt_servers
>  service_description            PING
>  check_command                  check_ping     <-- should be a valid command
> definition
>  contact_groups                 nt_admins
> }
> 
> Also check your command definition for check_ping:
> 
> # 'check_ping' command definition
> define command{
>         command_name    check_ping
>         command_line    /usr/local/nagios/libexec/check_ping -H
> $HOSTADDRESS$ -w
>  50:20% -c 100:100%
>         }
> 
> Nagios relies on the return code from the check_ping plugin to determine the
> status so you can test this by running:
> 
> [root at trip etc]# /usr/local/nagios/libexec/check_ping -H 10.0.0.1 -w 50:20%
> -c 100:100% ; echo $?
> PING OK - Packet loss = 0%, RTA = 0.95 ms     <-- Output from the plugin
> 0	<-- Return code (0=OK, 1=WARNING, 2=CRITICAL, any other
> value=UNKNOWN)
> [root at trip etc]# 
> 
> Hope this helps, if it doesn't I would suggest posting your problematic
> service & command definitions to the mailing-list.
> 
> Kind regards,
> 
> 
> 
> Steve Freegard
> Systems Manager
> Littlehampton Book Services Ltd.
> DDI: +44 (0)1903 82 8594
> FAX: +44 (0)1903 82 8620
> 
> -----Original Message-----
> From: Darren Bentley [mailto:darren at bcgroup.net]
> Sent: 02 January 2003 23:47
> To: nagios-users at lists.sourceforge.net
> Cc: nagiosplug-help at lists.sourceforge.net
> Subject: [Nagios-users] Status: Unknown
> 
> 
> I installed Nagios 1.0 on Red Hat 7.3 box and I'm running into some
> problems. The install went fine, Nagios loads fine. There is a strange
> PING problem.
> 
> I used the default sample files, removed all the junks hosts and added
> one host.
> 
> On the Service Detail page the hosts allways shows UNKNOWN in pumpkin
> orange color. Status Information shows: /bin/ping -n -U -c 5
> 192.168.123.10
> 
> I can run that manually and it works fine. I can also run CHECK_PING
> manually and it also works fine.
> 
> Here's what the log files show:
> 
> [1041550596] HOST ALERT: slocan-lamonte;DOWN;SOFT;8;/bin/ping -n -U -c 1
> 192.168.123.10
> [1041550596] HOST ALERT: slocan-lamonte;DOWN;SOFT;9;/bin/ping -n -U -c 1
> 192.168.123.10
> [1041550596] HOST ALERT: slocan-lamonte;DOWN;HARD;10;/bin/ping -n -U -c
> 1 192.168.123.10
> [1041550596] HOST NOTIFICATION:
> nagios;slocan-lamonte;DOWN;host-notify-by-epager;/bin/ping -n -U -c 1
> 192.168.123.10
> [1041550596] HOST NOTIFICATION:
> nagios;slocan-lamonte;DOWN;host-notify-by-email;/bin/ping -n -U -c 1
> 192.168.123.10
> [1041550596] SERVICE ALERT: slocan-lamonte;PING;UNKNOWN;HARD;1;/bin/ping
> -n -U -c 5 192.168.123.10
> 
> 
> Any ideas? I've removed it and recompiled and tried again.
-- 
Darren Bentley <darren at bcgroup.net>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf