Microsoft Windows Server 2012 R2
HPE DL380
2 CPUs/2 Sockets (E5-2643 v4)

[email protected], could you please provide the following information? This bug seems to be a rare one and I hope your input might help us to find the root cause.

1) What is the service pack version of the Microsoft Windows Server 2012 R2?

2) Please provide us the output of the following commands:

1. typeperf -qx "Processor Information"
   (It looks this one is already provided.)
2. typeperf -qx "Processor"
3. typeperf "\Processor(_Total)% Processor Time" "\Processor Information(_Total)% Processor Time" "\Processor Information(0,_Total)% Processor Time" "\Processor Information(1,_Total)% Processor Time"
   The last command should be run for at least 10-20 seconds to collect some samples

3) If possible, please also send the output for CoreInfo command, available here: https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo

4) Please run the debug version of the agent with additional debug outputs in it, which is available zabbix_agent-6.0.5-windows-amd64-2c64a901cf8_v2.zip. Debug level should be set in the Zabbix agent config to DebugLevel=4 - for debugging before starting the agent. It might also be helpful remove the log before start.

5) Have you tried using Zabbix agent 2? Is the reported issue observed with agent 2?

UPD 1:

The same issue on forum:

https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/416705-zabbix-agent-on-windows-processor-group-limits-view-on-cpu-usage-and-number-of-cpu-s

Hello,

The server on which we initially observed the problem was already decommissioned. But I found one, where the problem persists and it is windows 2016. Indeed, not all servers are affected, I collected some info, I will attach output of typeperf commands and coreinfo, but for debugging I need client with TLS support. And no, we did not try agent2 on Windows systems yet. 

<mprihodko>Please find the version with TLS (OpenSSL) support zabbix_agent-6.0.5-windows-amd64-openssl-2c64a901cf8_v2.zip

zabbix_agent.log

^{Interesting, server has counters only for 16 logical processors under "\Processor\". However, under "Processor Information" there are counters for both sockets.} 

<mprihodko> Yes, indeed. This is probably the direction for the further investigation.

When the number of logical processors is less or equal to 64, Zabbix agent 1 relies on the "old" "Processor" counter, and not on the "new" "Processor Information" counter. It looks to be the cause of this bug.

The counters are initialized in init_cpu_collector() function around here https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/src/zabbix_agent/cpustat.c?at=refs%2Fheads%2Ffeature%2FZBX-20985-6.0#125

This problem seems to be similar to the one we have: https://stackoverflow.com/questions/28098082/unable-to-use-more-than-one-processor-group-for-my-threads-in-a-c-sharp-app

A possible fix is available for testing zabbix_agent-6.0.6rc1-windows-amd64-openssl_2945440bba8_fix.zip We do not have such setup at Zabbix, and we cannot test it ourselves.

[email protected], could you please test it when you have time?

Everybody with the same problem is also welcome to test it.

I just tested it on two identical servers, it seems to work. At least I'm getting some values from the agent.

Available in:

• 6.4.0alpha1 (master) in 4580d5d6dfd
• 6.2.2rc1 in 69050dce16c
• 6.0.8rc1 in f301667e275