Hi Mahesh,

How does your check_nt command look like?

Have you defined it with the proper variables?

 

I don't know how you have defined it but it should look something like
this,

 

Check_nt $ARG1$ $ARG2$ ... 

 

Have you tried running the command from your shell?

 

If you want to learn more about macros etc in your commands this is a
good page,

http://nagios.sourceforge.net/docs/2_0/macros.html

 

Best regards,

--
Dan



________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mahesh
Vernekar
Sent: Monday, December 03, 2007 9:21 AM
To: [email protected]
Subject: [Nagios-users] Monitoring Large hard disk partition

 

Hi,
 
I have installed and Configured Nagios 3.0b7
 
I am getting following error, for monitoring a large capacity Hard disk
partition
Usage:check_nt -H host -v variable [-p port] [-w warning] [-c
critical][-l params] [-d SHOWALL] [-t timeout] 
 
The hard disk partition size is 683GB and the Drive letter is F:
I did following settings for the hard disk in windows.cfg file
 
define service[
          use                        generic_service
          host_name              guru
          service_description   F:\ Drive Space
          check_command      check_nt!USEDDISKSPACE!-l f -w 80 -f 90
          ]
 
This same settings work for other partitions that are of small capacity
(about 80GB). 
 
Can you helpd me solving this problem.
 
 
 
Regards
 
Mahesh Vernekar
ClearPoint Learning Systems
Pune, India

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Nagios-users mailing list
[email protected]
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

Reply via email to