CPU usage just stopped working

[hsmith]

How realistic is upgrading to one of the newer versions of NSClient?

[steve.chambers]

as long as I don't have to upgrade Nagios or make any major changes otherwise that should not be a problem.
Can I just install over top of what is already there or is there a different recommended procedure?

[hsmith]

as long as I don't have to upgrade Nagios or make any major changes otherwise that should not be a problem.
Can I just install over top of what is already there or is there a different recommended procedure?

This should not affect Nagios whatsoever. I'd back up your .ini from the Windows folder, and then uninstall via control panel (if it is an option in your version) and then install the new one.

[steve.chambers]

OK removed old client after saving my nsc.ini (program folder rather than "Windows") installed new version (0.4.3) from here http://www.nsclient.org/download/.
Copied my nsc.ini back to the install location and restarted the service. No change

Rebooted system, still the same...

[ssax]

If you open up and admin powershell shell and run this command (with the exact counter your using), what does it show?

Code: Select all

Get-Counter "\Processor Information(*)\Processor Frequency"

[steve.chambers]

I am not sure I understand where I plug in the counter or what name I use.

In the NagiosXI GUI it shows as CPU Usage, in the command that is sent by Nagios

Code: Select all

check_xi_service_nsclient!PASSWORD!CPULOAD!-l 5,80,90

I assume that it is CPULOAD

If I do just a get-counter with no arguments I get this

Code: Select all

Timestamp                 CounterSamples
---------                 --------------
9/11/2015 10:30:58 AM     \\stagedb\network interface(vmxnet3 ethernet adapter)\bytes total/sec :
                          814.670164577896

                          \\stagedb\network interface(isatap.{35aa846e-3f41-4533-a1b5-e36b7ff9adcb})\bytes total/sec :
                          0

                          \\stagedb\processor(_total)\% processor time :
                          0.10638669816645

                          \\stagedb\memory\% committed bytes in use :
                          32.806102812547

                          \\stagedb\memory\cache faults/sec :
                          0

                          \\stagedb\physicaldisk(_total)\% disk time :
                          0

                          \\stagedb\physicaldisk(_total)\current disk queue length :
                          0

[tgriep]

Lets try and rebuild the performance counters on your Windows system.

To rebuild the Counters, open Command Prompt with Run as administrator and type:

Code: Select all

cd c:\Windows\System32
lodctr /R
cd c:\Windows\SysWOW64
lodctr /R
WINMGMT.EXE /RESYNCPERF

You must stop and start the Performance Logs and Alerts service, open Command Prompt with Run as administrator and type:

Code: Select all

net stop pla && net start pla

And the Windows Management Instrumentation service, open Command Prompt with Run as administrator and type:

Code: Select all

net stop Winmgmt && net start Winmgmt

Try this and see if that fixes it.

[steve.chambers]

Unfortunately all those commands completed successfully but there is no change in the CPU Usage counter.
Even after submitting several forced immediate checks

[Box293]

Are there any errors in the Event Viewer under Application or System?

[steve.chambers]

There are errors but none that seem to be related to events surrounding the CPU or error reporting, WMI or NSClient