[ZBX-16887] zabbix_sender crash on MS Windows Created: 2019 Nov 08  Updated: 2024 Apr 10  Resolved: 2019 Nov 15

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 4.2.8
Fix Version/s: 4.0.15rc1, 4.4.2rc1, 5.0.0alpha1, 5.0 (plan)

Type: Problem report Priority: Trivial
Reporter: Mikhail Grigorev Assignee: Andrejs Kozlovs
Resolution: Cannot Reproduce Votes: 0
Labels: Windows, sender
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2012R2


Attachments: JPEG File sender_crash.jpg     PNG File sender_crash_history.png    
Team: Team A
Sprint: Sprint 58 (Nov 2019)
Story Points: 1

 Description   

Steps to reproduce:

  1. Add in config of zabbix-agent 4 IP addresses of active zabbix-proxy (ServerActive=). But 3 proxies from the list are not available, only 1 is available.
  2. Run zabbix_sender:
    zabbix_sender.exe -c C:\DBS_Zabbix\Config\dbs_zabbix_agentd.win.conf -s MYSERVER -T -i C:\DBS_Zabbix\Send\xxxx.metric
  3. Periodically, zabbix-sender crashes with an error. See windows event log (application).

Result:

Windows event log (application):

 Faulting application name: zabbix_sender.exe, version: 4.2.8.2400, time stamp: 0x5db8412a
 Faulting module name: KERNELBASE.dll, version: 6.3.9600.19304, time stamp: 0x5c7f684f
 Exception code: 0xc0000142
 Fault offset: 0x00000000000ecf30
 Faulting process id: 0x7544
 Faulting application start time: 0x01d59636b2439cf1
 Faulting application path: C:\DBS_Zabbix\zabbix_sender.exe
 Faulting module path: KERNELBASE.dll
 Report Id: eff1228a-0229-11ea-80c6-9457a559daed
 Faulting package full name: 
 Faulting package-relative application ID: 

I can provide more information if you tell me exactly what is needed.



 Comments   
Comment by Andrejs Kozlovs [ 2019 Nov 14 ]

Hello, cherts . Is it possible to get content of xxxx.metric file that cause crash?  How often crash happens, not 100%? Does sender write something in the log before crash? Is it 32 or 64 bit version? Is values from xxx.metrics seen in the servers frontend after sender crash?

Comment by Mikhail Grigorev [ 2019 Nov 14 ]

Hi

zabbix-sender crashes only if the configuration file C:\DBS_Zabbix\Config\dbs_zabbix_agentd.win.conf in the ServerActive parameter contains all 4 IP addresses of zabbix-proxy (only 1 out of 4 proxies is available).
If you leave 1 working proxy in ServerActive, then zabbix-sender will not crash.

Comment by Vladislavs Sokurenko [ 2019 Nov 14 ]

Does it crash when it is launched from command line ? Is there any output when it crash ?

Comment by Mikhail Grigorev [ 2019 Nov 14 ]

>>Is it 32 or 64 bit version?

OS Name: Microsoft Windows Server 2012 R2 Standard
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free

System Manufacturer: HP
System Model: ProLiant DL360 Gen9
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.

 

Comment by Mikhail Grigorev [ 2019 Nov 14 ]

I tried running zabbix-sender from cmd with metric files of different sizes (from 1 kb to 90 kb), but one crash did not happen.

In a real situation, zabbix-agent runs scripts on powershell, and from them run zabbix-sender and crashes.

I analyzed the data from the server, everything comes as it should, that is, the crash happens somewhere after sending data to one of the working zabbix-proxy.

While I do not know how to repeat this problem

Comment by Mikhail Grigorev [ 2019 Nov 14 ]

Are there any zabbix_sender assemblies with debugging information, can they help?

Is it possible to configure detailed logging of everything that zabbix-sender does with writing to a separate file?

ak there is no log in sender, you can use -vv option for more verbose information

Comment by Mikhail Grigorev [ 2019 Nov 15 ]

I used the -vv option, but it displays too little information. It also displays all the information on the console, when running zabbix-sender from powershell scripts, this information is difficult to log.

The most correct thing is to make the option so that zabbix-sender writes logs to a separate file, as the agent does.

Comment by Vladislavs Sokurenko [ 2019 Nov 15 ]

If it is executed by Zabbix agent, could you please provide a log of Zabbix agent ? And perhaps increase to log level debug, currently cannot reproduce.

Comment by Mikhail Grigorev [ 2019 Nov 15 ]

zabbix-agent runs scripts on powershell, they collect data in the mssql server and save them in files, then the scripts run zabbix-sender and it sends the files.

 

zabbix-agent -> run powershell script -> collect msql stat -> save to file -> run zabbix-sender

 

how in that case will help increase the level of logging zabbix-agent?

 

Comment by Vladislavs Sokurenko [ 2019 Nov 15 ]

Do I correctly understand that Zabbix agent run powershell script ? If yes then it might write something in the log about failed powershell script.

Comment by Mikhail Grigorev [ 2019 Nov 15 ]

Yes, you understood correctly.

But in the log there are no problems with the work of scripts on powershell, they work out correctly and save all metrics to files. I checked the correctness and integrity of the metric files.

I also noticed that along with the zabbix-sender.exe crash and cmd.exe crashes. But where cmd.exe comes from, I can’t say in the scripts there is no call to cmd.exe

Faulting application name: zabbix_sender.exe, version: 4.2.8.2400, time stamp: 0x5db8412a
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19304, time stamp: 0x5c7f684f
Exception code: 0xc0000142
Fault offset: 0x00000000000ecf30
Faulting process id: 0xc350
Faulting application start time: 0x01d59bb07db84736
Faulting application path: C:\DBS_Zabbix\zabbix_sender.exe
Faulting module path: KERNELBASE.dll
Report Id: bb65f3e5-07a3-11ea-80c6-9457a559daed
Faulting package full name: 
Faulting package-relative application ID:

 

 

Faulting application name: cmd.exe, version: 6.3.9600.17415, time stamp: 0x545042b1
Faulting module name: KERNELBASE.dll, version: 6.3.9600.19304, time stamp: 0x5c7f684f
Exception code: 0xc0000142
Fault offset: 0x00000000000ecf30
Faulting process id: 0x18c8
Faulting application start time: 0x01d59bb07d867e1c
Faulting application path: C:\Windows\system32\cmd.exe
Faulting module path: KERNELBASE.dll
Report Id: bb5f3bb4-07a3-11ea-80c6-9457a559daed
Faulting package full name: 
Faulting package-relative application ID:

 

Comment by Vladislavs Sokurenko [ 2019 Nov 15 ]

Zabbix agent launches script using cmd, are there any "Failed to execute command" entries in the log file ?

Comment by Mikhail Grigorev [ 2019 Nov 15 ]

There are no errors like "Failed to execute command" in the log file

Comment by Andrejs Kozlovs [ 2019 Nov 15 ]

there are 2 screenshots of artificial sender crash attached. JPG is from event log and PNG is from frontend history. sender is activated from agent UserParameter script.

here "Faulting module path" is zabbix_sender.exe, not KERNELBASE.dll

Can you send similar screenshot of event log with "Source" value?

Comment by Mikhail Grigorev [ 2019 Nov 19 ]

I found a crash problem, zabbix-sender is not to blame.

Thanks so much for the help.

Comment by Vladislavs Sokurenko [ 2019 Nov 19 ]

Could you please be so kind and share more details on what was the issue, maybe this information will help someone else, thanks !

Comment by Mikhail Grigorev [ 2019 Nov 19 ]

The problem was that zabbix-agent was version 3.4.15 and zabbix-sender 4.2.8
After upgrading zabbix-agent to 4.2.8, the problem disappeared.

Generated at Sun Jun 29 06:27:03 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.