Install problem

Subhendu Ghosh sghosh at sghosh.org
Sat Jun 7 02:54:54 CEST 2003


see FAQ# 17

also:
From the bash man page:

       For  the  shell's  purposes,  a command which exits with a
       zero exit status has succeeded.  An exit  status  of  zero
       indicates success.  A non-zero exit status indicates fail­
       ure.  When a command terminates on a fatal signal N,  bash
       uses the value of 128+N as the exit status.

       If  a  command  is not found, the child process created to
       execute it returns a status of 127.  If a command is found
       but is not executable, the return status is 126.

       If a command fails because of an error during expansion or
       redirection, the exit status is greater than zero.

       Shell builtin commands return a status of 0 (true) if suc­
       cessful,  and  non-zero  (false)  if an error occurs while
       they execute.  All builtins return an exit status of 2  to
       indicate incorrect usage.

       Bash  itself  returns  the exit status of the last command
       executed, unless a syntax error occurs, in which  case  it
       exits  with  a  non-zero value.  See also the exit builtin
       command below.


On Thu, 5 Jun 2003, Bill Hults wrote:

> Hi
> I'm working on a new install of Nagios. I'm working on RH7.3 w/Apache
> 1.3.27. I've installed Nagios from source & the plugins from RPM. The
> startup check returns 0 errors.
> I have the web interface working with authentication but the hosts show up
> with "(Return code of 126 is out of bounds - plugin may be missing)"
> messages. I can't find anything specific to this return code in the archives
> though there is a FAQ about the generic issue.
> The plugins are in /usr/lib/nogias/plugins & I have set that path for
> $USER1$. Nagios is in /usr/local/nagios with cgi.cfg & nagios.cfg in ../etc.
> The other config files are in /etc/nagios with the appropriate pointers in
> nagios.cfg.
> The Tactical Overview page shows a warning that the monitering process is
> not running which suggests that the check_nagios plugin suffers from the
> same problem.
> When I start Nagios from inet.d it starts and gives a message "This account
> is currently not available". I'm running Nagios as apache & the nagios start
> script shows that user.
> Any thoughts?
> TIA
> 
> Bill Hults
> 
> This e-mail was scanned by RAV Antivirus. (www.ravantivirus.com)
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.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
> 

-- 





-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.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





More information about the Users mailing list