[ZBX-25130] Zabbix agent2 crashing on Windows server 2016 Created: 2024 Aug 28  Updated: 2024 Dec 13  Resolved: 2024 Oct 10

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 6.4.18
Fix Version/s: None

Type: Problem report Priority: Blocker
Reporter: Victor Breda Credidio Assignee: Michael Veksler
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2024-08-28-10-57-38-844.png    
Issue Links:
Duplicate
duplicates ZBX-24672 Replace the sync collector for Agent2... Closed
Team: Team B
Sprint: Prev.Sprint, S24-W34/35, S24-W36/37
Story Points: 1

 Description   

The issue at hand is not easily reproduced.
The service for Zabbix agent2 just stops (crash).
No information is logged on the Zabbix agent2 log files.
The only information available for this is on the Windows event logs:

 

Faulting application name: zabbix_agent2.exe, version: 6.4.18.2400, time stamp: 0x00000000
Faulting module name: thl.dll_unloaded, version: 18.3.0.7033, time stamp: 0x5f72f8ac
Exception code: 0xc0000005
Fault offset: 0x0000000000006d87
Faulting process id: 0x24ec
Faulting application start time: 0x01daf4a3ec177153
Faulting application path: C:\Zabbix\zabbix_agent2.exe
Faulting module path: thl.dll
Report Id: 44464c50-f615-4de9-8de2-d7508cb14d13
Faulting package full name: 
Faulting package-relative application ID:

 

Zabbix agent (classic) is being used as a workaround to be able to monitor the server.

There's a similar issue reported for Zabbix agent (classic) as well on ZBX-22501. 

 Comments   
Comment by Brian Coverstone [ 2024 Aug 31 ]

The agent is also crashing on occasion on Windows 2019. Interesting thing, there isn't an entry in the Application Log. Just that the service stopped unexpectedly. It is very strange. The Zabbix log shows nothing, but I also don't have it set on full debug.

 

I did notice an event viewer entry just a few seconds before and after it crashed:

  The WMI Performance Adapter service entered the running state.

and then

  The WMI Performance Adapter service entered the stopped state.

 

So I feel this problem might have something to do with WMI keys.

The current host has the following two WMI requests:
 
   wmi.getall[root/cimv2,"select * from Win32_Baseboard"]
 
   wmi.getall[root\cimv2,"select Name,Description,NetConnectionID,Speed,AdapterTypeId,NetConnectionStatus,GUID from win32_networkadapter where PhysicalAdapter=True and NetConnectionStatus>0"]
 

Comment by Michael Veksler [ 2024 Oct 08 ]

Hi Brain2000,

Taken into consideration that there is no log entry I conclude that the crash happening outside of zabbix binary, but in zabbix process. (for example in any vendor dll involved in wmi process)

Try using zabbix_agentd.exe with debug log level 5. It has more advance error handling and i hope we can catch name of problematic dll.

But in any case  I don't see a reasonable way how we can fix crash in external dll

Comment by Michael Veksler [ 2024 Oct 08 ]

Given that the issue is not reproducible I hope it will be fixed within ZBX-24672, if you have any more questions, feel free to reopen this ticket!

(thl.dll, version: 18.3.0.7033)

Generated at Sun Apr 05 05:13:44 EEST 2026 using Jira 10.3.18#10030018-sha1:5642e4ad348b6c2a83ebdba689d04763a2393cab.