Alerts log file

frank ratty at they.org
Wed Apr 13 21:32:42 CEST 2005


For your error message:
http://www.nagios.org/faqs/viewfaq.php?faq_id=17

The mystery number in your line is the attempt counter. The number 
increments on consecutive failures of that service. When it reaches 
"max_check_attempts" (defined in the service definition) notifications are 
sent out. I'm guessing your config has "max_check_attempts 5".

Hope this helps
-frank

On Wed, 13 Apr 2005, Stephane Auger wrote:

> Date: Wed, 13 Apr 2005 14:46:40 -0400
> From: Stephane Auger <sauger at pre2post.com>
> 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
>
> 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?
>
> Thanks!
>
> Stephen


-------------------------------------------------------
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_id=6595&alloc_id=14396&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





More information about the Users mailing list