basic help with plugin please

[Demetri Mouratis]

On Fri, 30 Jul 2004, - CT - wrote:

>  I am running into a very basic problem, I am sure everyone here has
> solved it...
>
> I get a "(Return code of 127 is out of bounds - plugin may be missing)"
> on every status. So I ran nagios in the foreground. I see errors like
> "sh: line 1: /check_disk: No such file or directory". It looks like
> nagios is expecting to find the libexec commands in the root directory.
>
> How do I set the libexec path? I did the standard installation,
> /usr/local/nagios. Everything is owned by nagios user and nagios group.
> The plugins are in the default /usr/local/nagios/libexec. I didn't find
> setting the libexec path in the document. Also, where is the shell
> script the error message was refering to?... please help.

The best approach I've found is to set the user variable $USER1$ to
/usr/local/nagios/libexec.  Do this in resource.cfg like so:

# Sets $USER1$ to be the path to the plugins
$USER1$=/usr/local/nagios/libexec

Then, configure all your checks with a $USER1$ prefix.  From
checkcommands.cfg:

# 'check_local_disk' command definition
define command{
        command_name    check_local_disk
        command_line    $USER1$/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
        }

Hope that helps.

---------------------------------------------------------------------
Demetri Mouratis
dmourati at linfactory.com



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
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