Free disk space : Invalid drive

[Saletan, Jesse]

I'm having a problem with Nagios reporting "Invalid drive" when checking
free disk space on one particular server's D: drive.  Other servers
using the same services.cfg and checkcommands.cfg report free disk space
on D: without any problems.  The server that has this problem reports
free space on C: just fine.  And --here's the kicker-- while this
problem shows up in the web interface, I can run check_nt from a command
prompt and get the free space on that server's D: drive without any
trouble.

The server is running Nagios 2.5 on Red Hat Enterprise 4, and the client
I'm monitoring is a Windows Server 2003 SP1 system with NSClient 2.0.1.
I've checked D: drive permissions on the client and the SYSTEM account
has the same access to D: as it does to C:.

The relevant section of services.cfg is:

define service{
   host_name			server1,server2,server3,server4
   service_description		Disk_D
   check_command		check_nt_disk!D!80!90
   max_check_attempts		3
   normal_check_interval	5
   retry_check_interval		1
   check_period			24x7
   notification_interval	120
   notification_period		24x7
   notification_options		w,u,c,r,f
   contact_groups		localadmins
}

The check_nt_disk command from checkcommands.cfg:

define command{
    command_name check_nt_disk
    command_line $USER1$/check_nt -H $HOSTADDRESS$ -s mypasswd -v
USEDDISKSPACE -l $ARG1$ -w $ARG2$ -c $ARG3$
}

Any ideas?

Jesse



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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