[Nagiosplug-devel] return code 139, 142

[Subhendu Ghosh]

139 or 142 are the return codes received by Nagios from the popen process 
- they are usually related to the error code generated by the shell .

For Bash (linux): 

"EXIT STATUS
       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 failure.  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."

139 = 128+11 ==> SIGSEGV - invalid memory reference
142 = 128+14 ==> SIGALRM - Timer signal from ALARM

-sg

On Thu, 5 Dec 2002, Gunnar Hellekson wrote:

> 
> We've recently begun receiving "Return code 139 is out of bounds" on a
> number of our home-grown perl checks.  "Return code 142 is out of bounds" is
> pretty popular, too.  We've combed through the scripts -- we're not
> returning this, and none of the libraries are (documented to) return these
> error codes.  What's worse, they're almost impossible to reproduce from the
> command line.
> 
> Load, memory, etc. are all under control. We're using:
> 
> SunOS 5.8 Generic_108528-16 sun4u sparc SUNW,Ultra-Enterprise
> Nagios 1.0b6
> perl 5.6.1
> DBI 1.30
> DBD::Oracle 1.12
> 
> I've googled myself crosseyed on this error code, and I can't find any
> mention of it anywhere.  Any suggestions on how to debug this?
> 
> -Gunnar
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagiosplug-devel mailing list
> Nagiosplug-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> 

--