Problems using check_nt

[Andreas Ericsson]

Just out of curiousity...

Eduardo Kraemer Góes wrote:
> 	Hello people,
> 
> 	I have a server farm using Windows 2003 and I'm trying to use Nagios and check_nt to monitor them.
> 
> 	The problem is that the client doesn't alert when there are a warning or critical alarm. For example:
> 
> [kraemer at linux etc]$ sudo ../libexec/check_nt -H server1 -v CPULOAD -l 10,10,20
> CPU Load (10 min. 27%)

... why sudo?

If you try 'echo $?' after having run the plugin you'll get the 
exit-status of it. Not all of them make use of warning messages in output.

> [kraemer at linux etc]$ sudo ../libexec/check_nt -H server1 -w 10 -c 20 -v USEDDISKSPACE -l c
> c:\ - total: 8.79 Gb - used: 3.88 Gb (44%) - free 4.90 Gb (56%)
> 
> 	As you can see, even if I put very low values to force an alarm to be generated, it doesn't show any alarm. :-/
> 
> 	I'm trying nsclient with Windows 2003, but I have some W2000 that I'll monitor also, although I haven't tried nsclient with them yet.
> 
> 	Thanks for any help you can provide;
> 	Kraemer

-- 
Mvh / Best Regards
Sourcerer / Andreas Ericsson
OP5 AB
+46 (0)733 709032
andreas.ericsson at op5.se


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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