Change timeout alerts from CRITICAL to WARNING

[nathan]

grep "CRITICAL - Plugin timed out" * pointed me to popen.c modify lines 240-2:
        printf ("WARNING - Plugin timed out after %d seconds\n",
                        timeout_interval);
        exit (STATE_WARNING);

After modifying just popen.c or utils.c there was still a CRIT in the
resulting binary. Editing both appears to have resulted in a "warn on plugin
timeout". Keep in mind that the check_ping specificly will still CRIT on host
or network unreachable or if the rta or pl is above threshold.

See if that doesn't do the trick for you.

Nathan

On Fri, Sep 27, 2002 at 09:26:45AM -0500, Nolan Martin wrote:
> Well, in my environment, I would attribute the timeouts to latency in
> our network connections to the offending devices.  The server I run
> Nagios on is fairly robust, and is not the issue.  I only receive the
> timeouts for remote sites that see off and on latency.  
> 
> Certainly, in these cases, I also need to look at increasing the
> timeout threshold, but I still would like to see the timeouts appear as
> warnings, and not critical alerts. 
> 
> >>> "Bishop, Dean" <dean.bishop at tcdsb.org> 09/27/02 09:16AM >>>
> Does anyone have a guess as to the source of the problem?
> 
> i have this from time to time as well but have been attributing it to
> processor overload and am (or at was) expecting this problem to
> disappear
> once i get a new box.
> 
> anyone have thoughts?
> 
> dean
> 
> -----Original Message-----
> From: Nolan Martin [mailto:Nolan.Martin at co.travis.tx.us] 
> Sent: Friday, September 27, 2002 9:38 AM
> To: nagios-users at lists.sourceforge.net; nathan at sysadminsith.org 
> Subject: Re: [Nagios-users] Change timeout alerts from CRITICAL to
> WARNING
> 
> 
> Okay... Unfortunately, I am still not seeing the desired results... 
> Here are the steps I have done.  Perhaps someone can identify
> something
> I have left out.  
> 
> * In a separate directory (to isolate my test modifications), I
> downloaded and expanded the latest Nagios plugins.
> * Ran the configure: ./configure --prefix=/usr/local/nagios
> --with-nagios-user=nagios --with-nagios-group=nagios 
> --with-cgiurl=/nagios/cgi-bin 
> * Modified the check_ping.c file, lines 119 to 122 (see original
> e-mail
> posting below).
> * Did a make all
> * Copied the compiled executable to libexec
> * Stopped and restarted Nagios, waiting for a timeout.  Timeout still
> shows critical
> * Posted to group and received recommendation to change the utils.c
> * Went back to same directory
> * Modified utils.c, lines 122 to 124 (as described by Nathan)
> * Ran make all again
> * Copied the new compiled executable check_ping plugin to libexec
> * Stopped and restarted Nagios, waiting for a timeout.  Timeout still
> shows critical
> 
> Thoughts or suggestions?  Thanks in advance.
> 
> Nolan
> 
> >>> nathan <nathan at sysadminsith.org> 09/26/02 04:12PM >>>
> If I remember correctly I believe I had to modify utils.c (line
> 122/124)
> and change CRITICAL to WARNING and recompile the plugins....
> 
> When I did this I had compiled all plugins "stock" and then modified
> and
> recompiled so I had a modified version of check_by_ssh which was the
> one
> specific plugin I wanted only warnings for timeouts from.  
> 
> I think I ran strings on the binary plugin and found that modifying
> the
> .c for the plugin alone was not returning desired results 8-)
> 
> Best of luck,
> 
> Nathan
> 
> On Thu, Sep 26, 2002 at 12:41:49PM -0500, Nolan Martin wrote:
> > I am just now getting around to trying to implement the workaround
> > Nathan suggested awhile back, and have been unsuccessful so far.
> > 
> > I modified the check_ping.c file, lines 119 through 122 to the
> > following:
> > 
> > 	if (pl >= cpl || rta >= crta)
> > 		result = STATE_CRITICAL;
> > 	else if (pl >= wpl || rta >= wrta || rta < 0)
> > 		result = STATE_WARNING;
> > 
> > Basically, I moved the rta < 0 statement from resulting in a
> CRITICAL
> > state to resulting in a WARNING state, assuming that that the rta <
> 0
> > statement is what is determining a timeout. 
> > 
> > I then recompiled the plugins and copied over the new check_ping
> > executable to libexec.  However, timeouts continue to generate
> CRITICAL
> > alerts, and not WARNING alerts.
> > 
> > Admittedly, I have limited development experience, particularly with
> C.
> >  Can you tell me if I am completely off base or just missing some
> steps?
> >  I would greatly appreciate the additional assistance.
> > 
> > Nolan Martin
> > 
> > >>> nathan <nathan at sysadminsith.org> 08/20/02 04:35PM >>>
> > To stop the spam of alerts I recompiled my plugins so that timeouts
> > were
> > warnings and not critical then setup my contacts to not get alerted
> on
> > service warnings.
> > 
> > On Tue, Aug 20, 2002 at 04:24:20PM -0500, Nolan Martin wrote:
> > > I've seen this issue pop up several times in the archives, but
> > without
> > > any apparent resolution...  Perhaps someone can shed some light
> this
> > > time.  
> > > 
> > > I receive on-going (unexpected and undesired) service alerts due
> to
> > > timed out plugins.  This occurs for pretty much any service,
> > including
> > > the check_ping, the check_http and check_nwstat (for abends,
> etc.).
> > > 
> > > The problem is that the plugin timed out alerts do not seem to
> > follow
> > > the max_check_attempts for the service.  So, even if the previous
> > ping
> > > was okay, if the next ping check generates a time out, it
> > immediately
> > > generates a service alert (despite the fact that
> max_check_attempts
> > is
> > > set to 5.
> > > 
> > > Can someone tell me if this is working as designed, a bug, or
> > (always
> > > unlikely) administrator error?
> > > 
> > > I am currently running Nagios 1.0b3 on Red Hat Linux 7.3.  
> > > 
> > > Thanks.
> > > 
> > > Nolan
> > > 
> > > 
> > > 
> > > 
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by: OSDN - Tired of that same old
> > > cell phone?  Get a new here for FREE!
> > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 
> > > _______________________________________________
> > > Nagios-users mailing list
> > > Nagios-users at lists.sourceforge.net 
> > > https://lists.sourceforge.net/lists/listinfo/nagios-users 
> > 
> > -- 
> > Nathan
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by: OSDN - Tired of that same old
> > cell phone?  Get a new here for FREE!
> > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net 
> > https://lists.sourceforge.net/lists/listinfo/nagios-users 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf 
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net 
> > https://lists.sourceforge.net/lists/listinfo/nagios-users 
> 
> -- 
> Nathan the human
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf 
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/nagios-users 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf 
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/nagios-users

-- 
Nathan the human


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf