Take a look at this link. This is another way to rebuild the counters on your system. See if this helps.
http://social.technet.microsoft.com/wik ... nters.aspx
CPU usage just stopped working
Re: CPU usage just stopped working
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
steve.chambers
- Posts: 17
- Joined: Wed Aug 14, 2013 10:43 am
Re: CPU usage just stopped working
Hmmm... it is clear enough once you know what counter you are looking for, which would be the problem, what service am I looking for? There are a lot when it comes to CPU, somewhere north of 40...
Re: CPU usage just stopped working
Run perfmon as admin on your Windows system.
See if you can add the Processor Information, % Processor Time, _Total
I think it uses that one.
See if you can add the Processor Information, % Processor Time, _Total
I think it uses that one.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
steve.chambers
- Posts: 17
- Joined: Wed Aug 14, 2013 10:43 am
Re: CPU usage just stopped working
I seem to have been unclear.
Perfmon actually opens with Processor Time selected as the default "example" the problem comes in when following the specific instructions in the link provided.
One of the examples was this:
What is needed is the specific .ini file corresponding to the specific service that is being targeted. From that page they provide this example:
Taking that example and plugging "Processor" in place of USBPERF in the above example gives me in excess of 30 .ini files that have "processor" in their name or description. Some of which are not even in English (a casual glance shows Spanish and German).
So in order to run lodctr against the correct .ini file one has to know the specific name of the service.
Getting properties on the counter in PERFMON does not give that information nor do I see anything in Nagios that gives us the actual Windows service. If I use the "CPULOAD" keyword from the command line of the monitor in NagiosXI The command returns no results.
So in order to follow the instructions at the link provided I need to know what the exact service name is as I have not been able to determine that from the information I have available to me. Any ideas?
Perfmon actually opens with Processor Time selected as the default "example" the problem comes in when following the specific instructions in the link provided.
One of the examples was this:
Code: Select all
cd c:\Windows\Inf\usbhub
lodctr .409\usbperf.ini
This would work on any performance counter navigating to the appropriate folder and targeting the correct .ini file.
Code: Select all
From C:\Windows\Inf>
get-childitem -recurse *.ini | Select-String -pattern "usbperf" -context 0
So in order to run lodctr against the correct .ini file one has to know the specific name of the service.
Getting properties on the counter in PERFMON does not give that information nor do I see anything in Nagios that gives us the actual Windows service. If I use the "CPULOAD" keyword from the command line of the monitor in NagiosXI The command returns no results.
So in order to follow the instructions at the link provided I need to know what the exact service name is as I have not been able to determine that from the information I have available to me. Any ideas?
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: CPU usage just stopped working
I suggest asking this on the NSClient++ forums: http://forums.nsclient.org/
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
-
steve.chambers
- Posts: 17
- Joined: Wed Aug 14, 2013 10:43 am
Re: CPU usage just stopped working
Unfortunately there has been no response to my query on those forums.
Any other ideas?
Any other ideas?
Re: CPU usage just stopped working
You could try and reinstall the NSClient software or update to the latest stable release.
I don't know why resetting the counters won't fix it, that should do it.
I don't know why resetting the counters won't fix it, that should do it.
Be sure to check out our Knowledgebase for helpful articles and solutions!