hi
here is the post just on http://www.nsclient.org/
on nagios web console, i can see my windows client ,status is up, and i only config one service (uotime)for it , and status of uptime is unknown ,and info is : invalid password the password of administrator of the windows machine is aaaaaa and the line in nsc.ini:
***************
;# OBFUSCATED PASSWORD
; This is the same as the password option but here you can store the password in an obfuscated manner.
; *NOTICE* obfuscation is *NOT* the same as encryption, someone with access to this file can still figure out the
; password. Its just a bit harder to do it at first glance.
;obfuscated_password=Jw0KAUUdXlAAUwASDAAB
;
;# PASSWORD
; This is the password (-s) that is required to access NSClient remotely. If you leave this blank everyone will be able to access the daemon remotly.
;password=secret-password
;
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
; The syntax is host or ip/mask so 192.168.0.0/24 will allow anyone on that subnet access
;allowed_hosts=127.0.0.1/32
;
;# USE THIS FILE
; Use the INI file as opposed to the registry if this is 0 and the use_reg in the registry is set to 1
; the registry will be used instead.
use_file=1
allowed_hosts=192.168.0.11
password=aaaaaa
***************************
}}
so can anyone tell me how to ?
thanks a lot
betst regards
Reply Quote Edit
ituren
04/03/11 12:12:56 (25 hours ago)
Tree View Flat View (newer first) Flat View (older first)
*
Message #2125
The password (specified in the nsc.ini file) is not related to admin password. It is the password used by check_nt (-s option) to "authenticate" the user.
So given above file you should run:
check_nt -H ... -s aaaaaa ...
from 192.168.0.11.
// Michael Medin
Reply Quote
mickem
04/03/11 15:31:30 (22 hours ago)
o
Message #2126
hi
mickem
on 192.168.0.11 /usr/local/nagios/libexec/check_nt check_nt: Could not parse arguments Usage: check_nt -H host -v variable [-p port] [-w warning] [-c critical] [-l params] [-d SHOWALL] [-u] [-t timeout]
u see , no -s option
and
/usr/local/nagios/libexec/check_nt -H winserver -d SHOWALL check_nt: Could not parse arguments
so how ?
very thanks
best regards
waiting ...
Reply Quote Edit
ituren
04/04/11 04:42:05 (9 hours ago)
+
Message #2127
mickem@gotrek:~$ /usr/lib/nagios/plugins/check_nt -h
check_nt v1.4.15 (nagios-plugins 1.4.15)
Copyright (c) 2000 Yves Rubin (rubiyz@yahoo.com)
Copyright (c) 2000-2007 Nagios Plugin Development Team
<nagiosplug-devel@lists.sourceforge.net>
This plugin collects data from the NSClient service running on a
Windows NT/2000/XP/2003 server.
Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]
Options:
-h, --help
Print detailed help screen
-V, --version
Print version information
Options:
-H, --hostname=HOST
Name of the host to check
-p, --port=INTEGER
Optional port number (default: 1248)
-s, --secret=<password>
Password needed for the request
-w, --warning=INTEGER
Threshold which will result in a warning status
-c, --critical=INTEGER
Threshold which will result in a critical status
-t, --timeout=INTEGER
Seconds before connection attempt times out (default: -l, --params=<paramete rs>
Parameters passed to specified check (see below) -d, --display={SHOWALL}
Display options (currently only SHOWALL works) -u, --unknown-timeout
Return UNKNOWN on timeouts10)
-h, --help
Print this help screen
-V, --version
Print version information
-v, --variable=STRING
Variable to check
Valid variables are:
CLIENTVERSION = Get the NSClient version
If -l <version> is specified, will return warning if versions differ.
CPULOAD =
Average CPU load on last x minutes.
Request a -l parameter with the following syntax:
-l <minutes range>,<warning threshold>,<critical threshold>.
<minute range> should be less than 24*60.
Thresholds are percentage and up to 10 requests can be done in one shot.
ie: -l 60,90,95,120,90,95
UPTIME =
Get the uptime of the machine.
No specific parameters. No warning or critical threshold
USEDDISKSPACE =
Size and percentage of disk use.
Request a -l parameter containing the drive letter only.
Warning and critical thresholds can be specified with -w and -c.
MEMUSE =
Memory use.
Warning and critical thresholds can be specified with -w and -c.
SERVICESTATE =
Check the state of one or several services.
Request a -l parameters with the following syntax:
-l <service1>,<service2>,<service3>,...
You can specify -d SHOWALL in case you want to see working services
in the returned string.
PROCSTATE =
Check if one or several process are running.
Same syntax as SERVICESTATE.
COUNTER =
Check any performance counter of Windows NT/2000.
Request a -l parameters with the following syntax:
-l "\\<performance object>\\counter","<description>
The <description> parameter is optional and is given to a printf
output command which requires a float parameter.
If <description> does not include "%%", it is used as a label.
Some examples:
"Paging file usage is %%.2f %%%%"
"%%.f %%%% paging file used."
INSTANCES =
Check any performance counter object of Windows NT/2000.
Syntax: check_nt -H <hostname> -p <port> -v INSTANCES -l <counter object>
<counter object> is a Windows Perfmon Counter object (eg. Process),
if it is two words, it should be enclosed in quotes
The returned results will be a comma-separated list of instances on
the selected computer for that object.
The purpose of this is to be run from command line to determine what instances
are available for monitoring without having to log onto the Windows server
to run Perfmon directly.
It can also be used in scripts that automatically create Nagios service
configuration files.
Some examples:
check_nt -H 192.168.1.1 -p 1248 -v INSTANCES -l Process
Notes:
- The NSClient service should be running on the server to get any information
(http://nsclient.ready2run.nl).
- Critical thresholds should be lower than warning thresholds
- Default port 1248 is sometimes in use by other services. The error
output when this happens contains "Cannot map xxxxx to protocol number".
One fix for this is to change the port to something else on check_nt
and on the client service it's connecting to.
Send email to nagios-users@lists.sourceforge.net if you have questions
regarding use of this software. To submit patches or suggest improvements,
send email to nagiosplug-devel@lists.sourceforge.net
Reply Quote
mickem
04/04/11 08:50:42 (5 hours ago)
#
Message #2128
hi
mickem
i just exec such cmds , but can not work confused
cc:/usr/local/nagios # ./usr/local/nagios/libexec/check_nt -H 192.168.0.1 -p 12489 -s aaaaaa
-bash: ./usr/local/nagios/libexec/check_nt: No such file or directory cc:/usr/local/nagios # /usr/local/nagios/libexec/check_nt -H 192.168.0.1 -p 12489 -s aaaaaa check_nt: Could not parse arguments Usage: check_nt -H host -v variable [-p port] [-w warning] [-c critical] [-l params] [-d SHOWALL] [-u] [-t timeout] cc:/usr/local/nagios # /usr/local/nagios/libexec/check_nt -H 192.168.0.1 -v uptime -p 12489 -s aaaaaa check_nt: Could not parse arguments Usage: check_nt -H host -v variable [-p port] [-w warning] [-c critical] [-l params] [-d SHOWALL] [-u] [-t timeout]
thank you a lot best regards
Reply Quote Edit
ituren
04/04/11 11:16:01 (2 hours ago)
*
Message #2130
Uhmm..
the path I used is the one in my system (Debian box) your binaries could be elsewhere.
But I feel this discussions is sort of drifting from NSClient++ to unix support.
// Michael Medin
Reply Quote
mickem
04/04/11 12:12:37 (75 minutes ago)
o
*
Message #2131
Also note that check_nt is not part of NSClient++ it is a part of nagios-plugins so you can maybe get help there as well...
ok
mickem think that is the reason about plugin
could anyone tell me the reason
iam confused
thanks a lot
best regards