Page 1 of 1
Problem using check_nt on windows desktop service
Posted: Mon Aug 15, 2011 12:02 pm
by cwscribner
Hi all.
I'm trying to monitor n4n.exe on a windows desktop but I keep getting "Could not parse arguements". Here's a screen shot of my attempted setup.
Re: Problem using check_nt on windows desktop service
Posted: Mon Aug 15, 2011 12:36 pm
by lmiltchev
Make sure the name of the service that you use in your command is exactly the same as written under the Name Tab (in Services and Applications->Services under Computer Management).
Is n4n.exe listed there?
You can try with another service (that is listed), for example: "Print Spooler" just to see if it would parse the arguments.
Re: Problem using check_nt on windows desktop service
Posted: Mon Aug 15, 2011 9:54 pm
by cwscribner
lmiltchev wrote:Make sure the name of the service that you use in your command is exactly the same as written under the Name Tab (in Services and Applications->Services under Computer Management).
Is n4n.exe listed there?
You can try with another service (that is listed), for example: "Print Spooler" just to see if it would parse the arguments.
Already checked. The service in particular is a TTY service that I'm just trying to monitor UP/DOWN on. A tech at my client's site has confirmed that the service is present and running.
Re: Problem using check_nt on windows desktop service
Posted: Tue Aug 16, 2011 11:16 am
by lmiltchev
Can you run your check in command line and post the output, so we can review it?
You can follow this document, which explains how to test-check your commands from the command line:
http://support.nagios.com/wiki/index.ph ... mmand-line
Re: Problem using check_nt on windows desktop service
Posted: Tue Aug 16, 2011 11:18 am
by cwscribner
Socket timeout after 10 seconds.
Re: Problem using check_nt on windows desktop service
Posted: Tue Aug 16, 2011 2:02 pm
by mguthrie
It would be helpful to see the full command-line call and the output from it (password removed of course).
Code: Select all
cd /usr/local/nagios/libexec
./check_nt -H <address> -p 12489 -v '-d SHOWALL' '-l n4n.exe'
The "socket timeout" points to a firewall issue somewhere, did you forget the port number?
Make sure you have the following settings in the nsc.ini file, and restart the nsclient service after any changes.
Code: Select all
allow_arguments=1
debug=1
file=nsclient.log
Check the nsclient.log file if you're able to get through to the windows machine but you're still getting an error.
Re: Problem using check_nt on windows desktop service
Posted: Tue Aug 16, 2011 2:34 pm
by cwscribner
My apologies. I tried the command that you listed from the libexec directory and it still says "Cannot parse command arguments". NSClient is picking up the other metrics properly (CPU, RAM, Disk) but it can't execute the command for the particular service (n4n.exe).
Re: Problem using check_nt on windows desktop service
Posted: Wed Aug 17, 2011 1:16 pm
by mguthrie
I did some snooping around NSClient's documentation site. It's got some examples for checking service states, but it's using the check_nrpe command. See if this gets you what you need.
http://nsclient.org/nscp/wiki/CheckServiceState