Zabbix Agent 2 Performance Counter items become unsupported

[ed00ble]

The performance counter items on several Windows hosts have become unsupported with a "The handle is not a valid PDH object." error message. This has happened a few times and the only thing that has restored collection has been a restart of the agent2 service. Unfortunately the server and agent logs had purged by the time the issue was identified. Is there a known bug/fix that anyone is aware of?
Zabbix server 5.0.8; agent2 5.0.9

[Glencoe]

There have been quite a few bug fixes in Agent2 5.0.x on Windows. Can you try the latest version?

[ed00ble]

Thanks for reply. There is nothing specific to this issue mentioned in the release notes but I have manually updated a few agents without the problem reoccurring. It's possible that I haven't waited long enough or these hosts have not met the conditions again that caused the performance counters to fail. We are going to push the latest agent 2 (v5.0.15) to all of our Windows hosts over the next week. I will post an update in a couple of weeks as to whether the issue has returned.

[ed00ble]

Update: After pushing the agent2 updates to our Windows hosts things appeared to being running smoothly. There were no errors for 2-3 weeks and then about 100 hosts stopped collecting on the performance counter items around the same time with another 75 stopping a few days later. The only error in the logs is still the "The handle is not a valid PDH object." message.

[[email protected]]

I too am having this issue on Zabbix Agent2 5.4.9, Any luck on figuring what is causing this issue?

[pgatty]

I converted from the original agent 5.4.10 to Agent2 v 6.0 when I upgraded the server. I'm seeing the same issue. It seems to happen mostly with these two counters.

704385:20220223:044245.228 item "xxxx:system.cpu.load[percpu,avg15]" became not supported: No data available.
704386:20220223:044743.340 item "xxxx:system.cpu.load[percpu,avg15]" became supported

704386:20220223:190322.411 item "xxxxx: perf_counter[\Processor(_Total)\% Processor Time]" became not supported: A counter with a negative denominator value was detected.
704384:20220223:190351.602 item "xxxxx: perf_counter[\Processor(_Total)\% Processor Time]" became supported

[ed00ble]

Unfortunately, we're still experiencing the issue. I still haven't found anything in Zabbix or Windows logs to narrow it down. We've upgraded the server to 5.0.18 but are still on 5.0.15 for the agents. We'll probably push the latest version of agent2 in the near future but I haven't seen anything in the release notes/bug fixes that addresses this issue. Please post any updates if you have better luck than me.

[pgatty]

Do you need any of the enhanced functionality of agent2? If not, you might want to revert to the standard agent.

[Glencoe]

There was a fix specifically for this: https://support.zabbix.com/browse/ZBX-20269

Can you please test if the problem still persists in the fixed versions and if yes then comment in the ticket.

[ed00ble]

Thanks for the feedback. The fix mentioned looks like it addresses the issue with the IIS related performance counters. We are not monitoring those in our environment and I haven't experienced the "A counter with a negative denominator value was detected." error... just the "The handle is not a valid PDH object." error. We are going to push the latest version of agent 2 and I will comment on the results.

[Glencoe]

Sorry, I didn't realize there are two different problems. For your errors please comment here https://support.zabbix.com/browse/ZBX-20356