Monitoring MS servers

Paul Aviles paviles at adjoined.com
Mon Jul 19 06:20:52 CEST 2004


I am looking at the documentation for NSClient and I have copied the
following text to my command.cfg

command[check_nt_disk]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
USEDDISKSPACE -l $ARG1$ -w $ARG2$ -c $ARG3$
command[check_nt_cpuload]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
CPULOAD -l $ARG1$
command[check_nt_uptime]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
UPTIME
command[check_nt_clientversion]=$USER1$/check_nt -H $HOSTADDRESS$ -p
1248 -v CLIENTVERSION
command[check_nt_process]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
PROCSTATE -l $ARG1$
command[check_nt_service]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
SERVICESTATE -l $ARG1$
command[check_nt_memuse]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
MEMUSE -w $ARG1$ -c $ARG2$
command[check_nt_fileage]=$USER1$/check_nt -H $HOSTADDRESS$ -p 1248 -v
FILEAGE -l $ARG1$ -w $ARG2$ -c $ARG3$

I have an entry in my service.cfg for monitoring the server and the only
diference is the command that I have as:

check_command check_nt -h 10.10.10.10 -p 1248 -v CPULOAD -l
10,80,95,60,80,95,1440,80,95 

But I get errors like this..

Checking services...
Error: Service check command 'check_nt -H 192.168.100.32 -p 1248 -v
CPULOAD -l 10,80,95,60,80,95,1440,80,95' specified in service 'CPU Load'
for host 'szmia000' not defined anywhere!

Is the service.cfg the correct place to monitor the server and is the
command.cfg the correct file for the commands above?

Thanks

-pa




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&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





More information about the Users mailing list