trouble getting started: getting error 127 out of bounds on check_http

[Aleksey Tsalolikhin]

Hi.  I am trying to install Nagios for the first time.  I have a host,
"hockey", I want to run an HTTP check on.  I've got everything
configured correctly near as I can tell, but I am getting:

  Return code of 127 for check of service 'HTTP' on host 'hockey' was
out of bounds. Make sure the plugin you're trying to run actually
exists.

Please help.

$ ls -l /usr/local/nagios/etc/*cfg
-rw-r--r--    1 nagios   nagios      17496 Nov 29 18:06
/usr/local/nagios/etc/cgi.cfg
-rw-r--r--    1 nagios   nagios       4607 Nov 29 19:04
/usr/local/nagios/etc/checkcommands.cfg
-rw-r--r--    1 nagios   nagios        789 Nov 29 19:12
/usr/local/nagios/etc/contactgroups.cfg
-rw-r--r--    1 nagios   nagios       1076 Nov 29 19:11
/usr/local/nagios/etc/contacts.cfg
-rw-r--r--    1 nagios   nagios        667 Nov 29 19:14
/usr/local/nagios/etc/dependencies.cfg
-rw-r--r--    1 nagios   nagios       1589 Nov 29 19:13
/usr/local/nagios/etc/escalations.cfg
-rw-r--r--    1 nagios   nagios        832 Nov 29 19:03
/usr/local/nagios/etc/hostgroups.cfg
-rw-r--r--    1 nagios   nagios       2196 Nov 29 19:02
/usr/local/nagios/etc/hosts.cfg
-rw-r--r--    1 nagios   nagios       4246 Nov 29 18:36
/usr/local/nagios/etc/misccommands.cfg
-rw-r--r--    1 nagios   nagios      21329 Nov 30 16:44
/usr/local/nagios/etc/nagios.cfg
-rw-r--r--    1 nagios   nagios       3069 Nov 29 18:36
/usr/local/nagios/etc/resource.cfg
-rw-r--r--    1 nagios   nagios       2907 Nov 29 18:50
/usr/local/nagios/etc/services.cfg
-rw-r--r--    1 nagios   nagios       1589 Nov 29 18:37
/usr/local/nagios/etc/timeperiods.cfg
$

checkcommands.cfg contains:

# 'check_http' command definition
define command{
        command_name    check_http
        command_line    $USER1$/check_http -H $HOSTADDRESS$
        }


services.cfg contains:

define service{
        use                             generic-service         ; Name
of service template to use

        host_name                       hockey
        service_description             HTTP
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           5
        retry_check_interval            1
        contact_groups                  admins
        notification_interval           120
        notification_period             24x7
        notification_options            w,u,c,r
        check_command                   check_http
        }


resource.cfg contains:

$USER1$=/usr/local/nagios/libexec



I can run check_http manually:
$ id
uid=504(nagios) gid=505(nagios) groups=505(nagios)
$ /usr/local/nagios/libexec/check_http -H hockey
HTTP OK HTTP/1.1 200 OK - 14678 bytes in 0.035 seconds
|time=0.035396s;;;0.000000 size=14678B;;;0
$

nagios -v looks happy:

Total Warnings: 0
Total Errors:   0



Everything under /usr/local/nagios is owned by user nagios and group
nagios, except for the lockfile,
/usr/local/nagios/var/nagios.lock, which is owned by root, probably
from the start-up script.

Everything seems to be configured correctly.  However, service checks
are failing:

[1133392048] Warning: Return code of 127 for check of service 'HTTP'
on host 'hockey' was out of bounds. Make sure the plugin you're trying
to run actually exists.

Please advise.  I've read FAQ ID F0017 and searched the mailing list
archives and Google.

$ uname -a
Linux my.node.name 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT
2005 i686 i686 i386 GNU/Linux
$

Thanks,
Aleksey


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&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