FW: [Nagiosplug-help] check_disk problems

[Yanek Korff]

Well I'm not using -e, I just have different lines in my nrpe.cfg for
each filesystem I want checked since I want to indpendently specify
warning and critical levels on a filesystem-by-filesystem basis.  In any
case, out of curiosity I looked at the check_disk function today...
looks like under ideal circumstances:

if (disk_result==STATE_OK && erronly && !verbose)
	continue;

This if statement results in the following line not executing:

result = max_state (result, disk_result);

Which means result retains its initialized value of STATE_UNKNOWN, so
later it errors out.  I'd contact whomever wrote this, or perhaps just
place a copy of the result-assigning line in the aforementioned if
statement and rebuild check_disk.  I just confirmed this seems to work
okay -- for your sanity you may want to use the -m option.

-Yanek.

> -----Original Message-----
> From: David Olbersen [mailto:DOlbersen at stbernard.com] 
> Sent: Friday, October 24, 2003 11:33
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] FW: [Nagiosplug-help] check_disk problems
> 
> 
> David Olbersen wrote:
> 
> > Hello all!
> > 
> > I have a problem with check_disk on FreeBSD.
> > 
> > I happen to have FreeBSD 3, 4, and 5 machines, they all 
> show the same problem:
> > 
> > running `check_disk -e -w 10% -c 5%` I get:
> > Unable to read output
> > /bin/df <df options>
> > <last line of df output>
> > 
> > If I take out the -e the error goes away, but I get back 
> MUCH more output
> > than I wanted. I don't expect I've misconfigured something, 
> is this a known
> > bug?  
> > 
> > This is check_disk out of the nagios-plugins-1.3.1 FreeBSD 
> port and nagios
> > v1.1. 
> 
> This didn't get much (any) attention on nagiosplug-help, can 
> anybody in nagios-users help me out?
> 
> -- 
> David Olbersen
> iGuard Engineer
> St. Bernard Software
> 15015 Avenue of Sciences
> San Diego, CA 92127
> x2152
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: The SF.net Donation Program.
> Do you like what SourceForge.net is doing for the Open
> Source Community?  Make a contribution, and help us add new
> features and functionality. Click here: http://sourceforge.net/donate/
> _______________________________________________
> 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 electronic message transmission contains information that may be
confidential or privileged.  The information contained herein is intended
solely for the recipient and use by any other party is not authorized.  If
you are not the intended recipient (or otherwise authorized to receive this
message by the intended recipient), any disclosure, copying, distribution or
use of the contents of the information is prohibited.  If you have received
this electronic message transmission in error, please contact the sender by
reply email and delete all copies of this message.  Cigital, Inc. accepts no
responsibility for any loss or damage resulting directly or indirectly from
the use of this email or its contents.
Thank You.
----------------------------------------------------------------------------


-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
_______________________________________________
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