On windows systems system.cpu.util does not work some times. The response is that it's not supported, but obviously it is since it's working on many other sytsems. Seems to be about a 5% failure rate, and is not consistent with hardware.
-
-
Actually it looks like I can expand this bug to include a wider scope. Agents some times arbitrarily decide certain keys are not supported. I have another system that has now decided net.if.in[{IPADDRESS},bytes] is not supported. False, it's a template item, works on 20 other servers that are also server 2008, and it WAS working for a while. Something seems to cause agents to just up and have certain keys fail, and then there seems no way to force them to work again. If you enable the item again, it just goes back to "not supported" on the next check, and you have no data. -
-
Issues of this nature persist in the 2.0.5 full release. This is being tracked in multiple bug tickets for different key values.Comment
-
I am still having this issue with Zabbix Agent 2.0.6 as well. It works on some systems, but not all, and the 'system.cpu.util[]' does not work, keeps returning ZBX_NOTSUPPORTED.
This is on RHEL 5 and 6 systems. The agent was just installed today from RPM's and is also allowed to have sudoers permissions.Comment
Comment