-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check_cpu return abnormal (negative billions) percentage #780
Comments
Also have exact issue after upgrading to windows server 2022 on a physical server with 96 cores. check_cpu shows right CPU load when the actual cpu load is below ~40% and negative billons percentage when cpu load is higher. Details |
I have the same issue on Windows 2022. It worked fine on Windows 2019. |
Deprecated API functions https://learn.microsoft.com/en-us/windows/win32/procthread/numa-support Workaround - to restrict nscp to only one processor node group by setting cpu affinity (for example, in task manager - rightclick on process, select "set affinity", set to allow to run on only one processor group). However, it will monitor only this cpu node group. |
Also have exact issue but only occure on google cloud compute engine with windows 2016 std NSClient++ version: 0.5.2.35 |
Issue and Steps to Reproduce
run "check_cpu" with "nscp.exe test" shell on a physical computer with 64+ logical processors(threads) and windows 2022 (running hyper-v)
Expected Behavior
I should get something like this, with perfdata value between 0 and 100%
Actual Behavior
I get this with extremly high negative number (around -32G%)
Details
Additional Details
it only happens with physical server with more than 64 thread running hyper-v on 2022,
unfortunately I don't that many server to test if it's physical server, or more than XX threads, or non-hyper-v, this are the first servers with this kind of combo hard/os we had to provision
I do have some old windows 2016 with more than 32 threads and hyper-v that never add this issue, no way to test more broadly
I can just confirm a 2x20core/80threads and a 2x18/72 server (HPe, DL380Gen10 intel xeon)
The text was updated successfully, but these errors were encountered: