[ZBX-17974] WMI queries do not timeout correctly Created: 2020 Jun 25 Updated: 2024 Apr 10 Resolved: 2020 Aug 10 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Agent (G) |
| Affects Version/s: | 4.0.21 |
| Fix Version/s: | 4.0.24rc1, 5.0.3rc1, 5.2.0alpha1, 5.2 (plan) |
| Type: | Problem report | Priority: | Critical |
| Reporter: | Edgars Melveris | Assignee: | Artjoms Rimdjonoks |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
Strata.tar.gz
zabbix_agentd.log
|
||||||||
| Issue Links: |
|
||||||||
| Team: |  Team C |
||||||||
| Sprint: | Sprint 65 (Jun 2020), Sprint 66 (Jul 2020), Sprint 67 (Aug 2020) | ||||||||
| Story Points: | 0.75 | ||||||||
| Description |
|
If the wmi queries do not deliver result for some reason, the agent doesn't properly timeout after the configured period. Instead, the agent process is hanging and no longer answering other requests. After all processes are hanging, the agent no longer responds to server requests. This was tested with system.uname, which uses wmi to get data, but the same problem happens with any wmi.* items. 30484:20200625:131354.557 Requested [system.uname] |
| Comments |
| Comment by Alexander Vladishev [ 2020 Aug 07 ] |
|
Fixed in:
|