PDHCollector.cpp:215

[Equintana]

HI,

I´m deploying windows 2008r2 nsclient 0.3.9.328 64 bits and only ping check works.


Why? This error is shown


Error:

2015-12-02 22:42:28: error:modules\CheckSystem\PDHCollector.cpp:215: Failed to query performance counters: PdhCollectQueryData failed: : No data to return. (800007D5)
2015-12-02 22:42:29: error:modules\CheckSystem\PDHCollector.cpp:215: Failed to query performance counters: PdhCollectQueryData failed: : No data to return. (800007D5)


Any idea?

Regards

[hsmith]

Have you tried with a more modern version of NSClient?

[Equintana]

Hi,

Yes..0.4.3 64 bits.

[hsmith]

Have you tried posting on the NSclient forums? NSClient is not our product, so we only provide limited support for it. What happens when you try to do a check from the Nagios command line? Can you post your NSClient.ini here for us to review? What version of Nagios are you using?

[Box293]

It sounds like the performance counters on the Windows box need fixing.

From the windows box run:

Code: Select all

lodctr /R

After that restart the NSClient++ service.

[Equintana]

HI,

After ran lodctr /R

I can see at debug file:

2015-12-03 19:16:20: debug:modules\CheckSystem\PDHCollector.cpp:130: Found countername: CPU: \Processor(_total)\% Processor Time
2015-12-03 19:16:20: debug:modules\CheckSystem\PDHCollector.cpp:131: Found countername: UPTIME: \System\System Up Time
2015-12-03 19:16:20: debug:modules\CheckSystem\PDHCollector.cpp:132: Found countername: MCL: \Memory\Commit Limit
2015-12-03 19:16:20: debug:modules\CheckSystem\PDHCollector.cpp:133: Found countername: MCB: \Memory\Committed Bytes
2015-12-03 19:16:20: debug:include\Socket.h:683: Bound to: 0.0.0.0:5666
2015-12-03 19:16:20: debug:include\Socket.h:683: Bound to: 0.0.0.0:12489

But at nagios console:

172.30.0.33
View service status details for this host

CPU Usage
Critical 8d 19h 18m 9s 5/5 2015-12-03 19:15:42 CRITICAL - Socket timeout after 10 seconds

Drive C: Disk Usage
Critical 8d 19h 17m 39s 5/5 2015-12-03 19:11:35 CRITICAL - Socket timeout after 10 seconds

Memory Usage
Critical 8d 19h 16m 58s 5/5 2015-12-03 19:11:28 CRITICAL - Socket timeout after 10 seconds

Ping
Ok 8d 19h 16m 31s 1/5 2015-12-03 19:12:00 OK - 172.30.0.33: rta 1.127ms, lost 0%

Uptime
Critical 8d 19h 15m 46s 5/5 2015-12-03 19:12:21 CRITICAL - Socket timeout after 10 seconds

[rkennedy]

From the Nagios machine, can you attempt to run a check against NSClient over the command line and post the result?

You could also try adding the -t 30 to the end of one of the checks to give it a bit more time then 10 seconds - this could help as well.

[Box293]

Can you also post your NSC.ini file please.