Alerts log file

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Stephane Auger
> Sent: Wednesday, April 13, 2005 1:47 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Alerts log file
> 
> Hi everyone,
> 
> 	I'm trying to use the Nagios log files to create stats using a
> custom made program.  Now, I figured out most of the log file except
for
> one field, and I can't find any docs on it.  Between the Soft/Hard
state
> and the Message, there's a field with a number, which from what I've
> seen is always between 1 and 5.  Does anyone know what it is?
> 
> [1113417698] SERVICE ALERT:
> testPC;Ping;CRITICAL;SOFT;***HERE***1;CRITICAL - Plugin timed out
after
> 10 seconds

It's the retry number. You probably have max_check_attempts set to 5.
 
> Also, from time to time I get the error message
> "Warning: Return code of 139 for check of service 'Ping' on host
> 'testPC' was out of bounds."
> in the log file.  I'm trying to ignore that line through my app, but
> would still love to know why it's doing that.  Any ideas on this one?

The plugin, or the ping binary it calls is probably segfaulting.
139-128=11. Signal 11 == Segfault. Do you have memory issues on that
machine or is the hardware stressed in any way? It's probably dumping
core somewhere if you wanted to take a look at it. This link may be
useful --

http://www.bitwizard.nl/sig11/

--
Marc


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&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