Page 1 of 2
NS Client Error Failed to get PDH Value
Posted: Mon Feb 23, 2015 5:00 pm
by toleolu
This is a brand new physical install of Server 2008, never saw this error before, looking online indicates this error has something to do with the performance counters in Windows being jacked up. When I run the command to reset the performance counters (lodctr.exe /R) Windows throws this error:
"Error: Unable to rebuild performance counter setting from system backup store, error code is 5."
Digging into that error I found the lodctr commands to backup the original /S:Backup_Original.ini then do a restore R:PerfStringBackup.ini and that throws this error:
"Error: Unable to restore performance counter setting from backup file C:\Windows\System32\PerfStringBackup.ini, error code is 5".
In addition to the PDH Value issue, it's also having problems with"
Capture.JPG
Short of having the guy go back and wipe that drive and start from scratch on the OS install, does any have any suggestions?
Re: NS Client Error Failed to get PDH Value
Posted: Mon Feb 23, 2015 5:23 pm
by lmiltchev
Did you run "lodctr.exe /R" as administrator?
Re: NS Client Error Failed to get PDH Value
Posted: Mon Feb 23, 2015 5:46 pm
by toleolu
Crap!!!
Ran successfully as local admin, but did not fix the problem.
Thanks
Re: NS Client Error Failed to get PDH Value
Posted: Mon Feb 23, 2015 9:05 pm
by Box293
Is your problem now resolved?
Re: NS Client Error Failed to get PDH Value
Posted: Tue Feb 24, 2015 12:02 pm
by toleolu
No, I ran the reset as admin, it ran successfully, but it did not fix the problem with the three services.
Re: NS Client Error Failed to get PDH Value
Posted: Tue Feb 24, 2015 12:34 pm
by tgriep
Could you post how the service checks are configured so we can review them?
Re: NS Client Error Failed to get PDH Value
Posted: Tue Feb 24, 2015 12:45 pm
by toleolu
Just the standard CPU check from the Windows Server Monitoring Wizard:
define service {
host_name webterm2.hhsc.org
service_description CPU Usage
use xiwizard_windowsserver_nsclient_service
check_command check_xi_service_nsclient!nagios!CPULOAD!-l 5,90,95
max_check_attempts 3
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts cmasteller,lchong,ryamamoto
contact_groups CDC Help Desk
_xiwizard windowsserver
register 1
}
Is this what you were talking about, or did you need something else?
Mahalo
Re: NS Client Error Failed to get PDH Value
Posted: Tue Feb 24, 2015 1:41 pm
by toleolu
I'm going to sit down with the guy who installed the OS on this server (he's new) and blow it away and reinstall it.
Never saw this problem with a basic Nagios config on a Windows server so I'm wondering what else might be lurking in the background that might jump up and bite us when this box goes into production.
I'll post the results when we're done.
Mahalo
Re: NS Client Error Failed to get PDH Value
Posted: Tue Feb 24, 2015 3:29 pm
by abrist
Great, thanks for the update.
Re: NS Client Error Failed to get PDH Value
Posted: Tue Feb 24, 2015 4:58 pm
by Fred Kroeger
Are you using nsclient++ as the NRPE agent?
I've had similar issues with a Win2008 Exchange server where the check_pdh command is failing.
I'm still in the process of proving my solution, but indications so far has been that the there is a problem with nsclient.
I have upgraded a server to the latest version 0.4.3.x and the check_pdh command appears to be working correctly now
Regards... Fred