Help: Newbie - Return code of 127 is out of bounds - in status.log file

[Srinivas Kotapally]

Marc

I had missed one step in the nagios installation... Setting up of the
commands (macros).  I have done that but am still getting the permissions
problem!

It is important to note that the user you are logging in as (you do have
.htaccess configured properly, don't you?) must be an authorized contact
for the hosts and services that you want them to see.

I have set-up the .htaccess in the /usr/local/nagios/share directory with
the entry:
AuthName "Nagios Access"
AuthType Basic
AuthUserFile /usr/local/nagios/etc/htpasswd.users
require valid-user

I have both nagios and for myself set-up as users in the htpasswd.users
directory!  Both nagios and me are contacts and users on the system.  Both
are also the authorised contact for the 1 host that I have set-up.

I am still getting the permissions problem!

"It appears as though you do not have permission to view information for any
of the services you requested...


If you believe this is an error, check the HTTP server authentication
requirements for accessing this CGI
and check the authorization options in your CGI configuration file."

Can you please help?


Regards

KS



-----Original Message-----
From: Marc Powell [mailto:mpowell at ena.com]
Sent: Wednesday, October 08, 2003 5:09 PM
To: ksrinivas at bisil.com; Nagios (E-mail)
Subject: RE: [Nagios-users] Help: Newbie - Return code of 127 is out of
bounds - in status.log file




> -----Original Message-----
> From: Srinivas Kotapally [mailto:ksrinivas at bisil.com]
> Sent: Wednesday, October 08, 2003 3:46 PM
> To: Nagios (E-mail)
>
> Hi all
>
> I have just finished setting up Nagios.  I have a problem already... I
am
> looking at the log file (status.log) and have seen the following entry
in
> the log file:
> SERVICE;<my_host>;/dev/hda1 Free
>
Space;CRITICAL;1/3;HARD;1065646603;1065646903;ACTIVE;1;1;1;1065216471;0;
CR
> IT
> ICAL;0;0;0;429480;0;0;1;0;0;1;0;0.00;0;1;1;1;(Return code of 127 is
out of
> bounds - plugin may be missing)
>
> What does this indicate?

That the plugin is missing as far as nagios is concerned. Your specific
service definition and command definition would be useful. Some things
to check --

	* Verify in resource.cfg that $UER1$ points to your nagios
libexec directory.
	* Verify in commands.cfg that either $USER1$ is used in the
command_line for the specific plugin or the full path to the plugin is
specified
		e.g -
		define command{
        		command_name    verify_http
        		command_line    $USER1$/check_http  -H $ARG1$ -I
$HOSTADDRESS$ -s \/html
        	}
	* Verify that the plugin actually exists in the path specified
(typically /usr/local/nagios/libexec/) **and is executable by the nagios
user**. Test this by su -'ing to nagios and executing the plugin.

>
> Also, from my web interface when I try to see "Service Detail" I get
the
> following message:
> It appears as though you do not have permission to view information
for
> any
> of the services you requested...
> If you believe this is an error, check the HTTP server authentication
> requirements for accessing this CGI
> and check the authorization options in your CGI configuration file.
>
> Does this mean that my configuration is incorrect?

Yes.

> Can anyone please guide me in the configuration?

http://nagios.sourceforge.net/docs/1_0/cgiauth.html

It is important to note that the user you are logging in as (you do have
.htaccess configured properly, don't you?) must be an authorized contact
for the hosts and services that you want them to see.


--
Marc



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
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