check disks - big disk problem?

[Phil Costelloe]

> From: Yanek Korff [mailto:ykorff at cigital.com] 
> 
> Maybe my math is off, but I'm observing the following with 
> Nagios 1.3.3 (and nrpe)
> 
> These two show up as WARNINGs:
> Drive D:\ - Total: 132.58 GB - Free: 131.69 GB (99%) - Used: 
> 912 MB (1%)
> 
> Drive E:\ - Total: 273.22 GB - Free: 270.24 GB (99%) - Used: 2.99 GB
> (1%)  
> 
> I have nrpe and check_disk.wsf configured like so (is this the wrong
> forum?):

The nrpe_nt plugin forum at http://support.tsmgsoftware.com is probably
more appropriate, especially as the author of the plugin will almost
certainly read it, but personally I enjoy the fact that the whole Nagios
world gets discussed here as it's sometimes the only way I find out
about some of the addons and techniques.

> command[check_disk_d]=c:\winnt\system32\cscript.exe //NoLogo 
> //T:10 "c:\program files\nrpe_nt\check_disk.wsf" /drive:"d:\" 
> /w:102400 /c:10240 
> command[check_disk_e]=c:\winnt\system32\cscript.exe //NoLogo 
> //T:10 "c:\program files\nrpe_nt\check_disk.wsf" /drive:"e:\" 
> /w:102400 /c:10240
> 
> Yeah, I'm asking for warning at 100GB.  But there's more than 
> that available.  Is it just late and I'm not seeing something?

It's a 640 Kb problem.

check_disk.wsf extracts the argument values using the VBScript
conversion function CInt which has a limit of 32768 (or so). Use (or get
the author to use) CLng and it should work.

Phil


-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
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