-
Problem report
-
Resolution: Unresolved
-
Trivial
-
None
-
None
-
None
-
None
-
Windows Server 2022, zabbix agent2 7.0.6
Steps to reproduce:
- Agent configured with PSK in active mode, pointed toward proxy
- In Zabbix frontend enable host, monitort by proxy. (at 09:21:xx)
Result:
after a few log lines about no active check on server you see config is available.
Agent starts working on it and I think it crashed but log stops, and agent windows services is stopped.
Expected:
Agent just to keep running after it's being added.
After starting the agent service again, it does work.
Below the log of both windows clients, noticeable is that both have a line about WindowsPerfMon takes to long and it's either the last line of just one custom item after it.
"plugin 'WindowsPerfMon': time spent in collector task 2.368739 s exceeds collecting interval 1 s"
[code]
2024/12/19 09:21:34.022383 [101] no active checks on server [myproxy:10051]: host "host-01" not monitored
2024/12/19 09:21:39.021723 [101] no active checks on server [myproxy:10051]: host "host-01" not monitored
2024/12/19 09:21:47.040352 check 'perf_instance_en.discovery[PhysicalDisk]' is not supported: Timeout occurred while gathering data.
2024/12/19 09:21:47.113026 plugin 'Cpu': time spent in collector task 2.048228 s exceeds collecting interval 1 s
2024/12/19 09:21:47.118089 plugin 'WindowsPerfMon': time spent in collector task 2.031292 s exceeds collecting interval 1 s
2024/12/19 09:21:59.039171 check 'updates.missing' is not supported: Timeout occurred while gathering data.
2024/12/19 09:21:16.020984 [101] no active checks on server [myproxy:10051]: host "host-02" not monitored
2024/12/19 09:21:21.021760 [101] no active checks on server [myproxy:10051]: host "host-02" not monitored
2024/12/19 09:21:26.020837 [101] no active checks on server [myproxy:10051]: host "host-02" not monitored
2024/12/19 09:21:31.021640 [101] no active checks on server [myproxy:10051]: host "host-02" not monitored
2024/12/19 09:21:36.020526 [101] no active checks on server [myproxy:10051]: host "host-02" not monitored
2024/12/19 09:21:41.022527 [101] no active checks on server [myproxy:10051]: host "host-02" not monitored
2024/12/19 09:21:49.031326 check 'perf_instance_en.discovery[PhysicalDisk]' is not supported: Timeout occurred while gathering data.
2024/12/19 09:21:49.040290 check 'system.uptime' is not supported: Timeout occurred while gathering data.
2024/12/19 09:21:49.385632 plugin 'WindowsPerfMon': time spent in collector task 2.368739 s exceeds collecting interval 1 s
[/code]
Both hosts where activated with mass update feature, not that I expect that this is an issue but that is why both host are almost simultaneous updated.
My colleague had a similar not running agent on a different windows host as well also 7.0.6 but he trashed the log so not sure what the reason was for that one but 3 within 24hours and all 3 after it's initial installation gives me the impression that something could be wrong.