Page 1 of 1

NSClient++ question

Posted: Fri Mar 07, 2014 5:12 pm
by Sbergonzi
I'm using the NSClient++ plugin and configuring one server it works fine, configuring another server and only the PING service works. Both are Windows2003 servers. The XI server is 10.aaa.bbb.cc, the server that works is 10.aaa.bbb.dd. The server that doesn't is 10.aaa.eee.ff. I would have thought if that was an issue with IP the ping wouldn't work. Password is correct as well.

Has anyone used this plugin?

Debug Log:
2014-03-07 17:07:44: message:modules\FileLogger\FileLogger.cpp:86: Starting to log for: NSClient++ - 0.3.9.327 2011-08-16
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:557: Attempting to start NSCLient++ - 0.3.9.327 2011-08-16
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: CheckDisk...
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: Event log Checker....
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: Helper function...
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: CheckSystem...
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: CheckWMI...
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: File logger...
2014-03-07 17:07:44: debug:CACHEmodules\CheckSystem\PDHCollector.cpp:73: Autodetected w2k or later, using w2k PDH counters.
2014-03-07 17:07:44: debug:CACHEmodules\CheckSystem\PDHCollector.cpp:110: Using index to retrive counternames
2014-03-07 17:07:44: message:CACHEmodules\FileLogger\FileLogger.cpp:87: Log path is: D:\Program Files\NSClient++\\nsclient.log
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: NRPE server (w/ SSL)...
2014-03-07 17:07:44: debug:CACHEmodules\CheckSystem\PDHCollector.cpp:130: Found countername: CPU: \Processor(_total)\% Processor Time
2014-03-07 17:07:44: debug:CACHEmodules\CheckSystem\PDHCollector.cpp:131: Found countername: UPTIME: \System\System Up Time
2014-03-07 17:07:44: debug:CACHEmodules\CheckSystem\PDHCollector.cpp:132: Found countername: MCL: \Memory\Commit Limit
2014-03-07 17:07:44: debug:CACHEmodules\CheckSystem\PDHCollector.cpp:133: Found countername: MCB: \Memory\Committed Bytes
2014-03-07 17:07:44: debug:CACHEmodules\NRPEListener\NRPEListener.cpp:92: Loading all commands (from NRPE)
2014-03-07 17:07:44: debug:CACHEmodules\NRPEListener\NRPEListener.cpp:122: Starting NRPE socket...
2014-03-07 17:07:44: debug:CACHENSClient++.cpp:1007: Loading plugin: NSClient server...
2014-03-07 17:07:44: debug:CACHEd:\source\nscp\branches\stable\include\Socket.h:683: Bound to: 0.0.0.0:5666
2014-03-07 17:07:44: debug:NSClient++.cpp:709: NSCLient++ - 0.3.9.327 2011-08-16 Started!
2014-03-07 17:07:44: debug:d:\source\nscp\branches\stable\include\Socket.h:683: Bound to: 0.0.0.0:12489

Re: NSClient++ question

Posted: Mon Mar 10, 2014 9:11 am
by slansing
What do you mean by, it wont work? What error output are you getting when you manually run checks against that windows system from the XI server's CLI?

Re: NSClient++ question

Posted: Mon Mar 10, 2014 11:49 am
by Sbergonzi
This command works against one of the hosts and not the other.
check_xi_service_nsclient!NagiosXI10!CPULOAD!-l 5,80,90

The error is:
CRITICAL - Socket timeout after 10 seconds

Re: NSClient++ question

Posted: Mon Mar 10, 2014 12:43 pm
by Sbergonzi
Running from the command line works in one instance and times out in another. Commands are exactly the same. I also checked the NSClient ini, also the same and the Nagios server IP is registered.

/usr/local/nagios/libexec/check_nt -H <badIP> -s "<password>" -p 12489 -v USEDDISKSPACE -l D -w 80 -c 95

/usr/local/nagios/libexec/check_nt -H <goodIP> -s "<password>" -p 12489 -v USEDDISKSPACE -l D -w 80 -c 95

Re: NSClient++ question

Posted: Mon Mar 10, 2014 2:48 pm
by Sbergonzi
I believe this has to do with our network setup as traceroute is not working as well. I'm further investigating with my network team.

Re: NSClient++ question

Posted: Mon Mar 10, 2014 2:50 pm
by tmcdonald
We'll keep this open until we head back from you.

Re: NSClient++ question

Posted: Wed Mar 12, 2014 10:25 am
by Sbergonzi
This was a firewall rule on our side, good to go. Thanks!

Re: NSClient++ question

Posted: Wed Mar 12, 2014 10:40 am
by slansing
Great! Locking er' up!