[ZBX-21151] Agent crashing on SIGSEGV on Red Hat Linux 8.5 (Ootpa) Created: 2022 Jun 02  Updated: 2025 May 20

Status: READY TO DEVELOP
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 4.0.41, 5.0.24
Fix Version/s: 7.0.14rc1, 7.2.8rc1, 7.4.0rc1 (master)

Type: Problem report Priority: Trivial
Reporter: Milan Gvozdik Assignee: Jurijs Klopovskis
Resolution: Unresolved Votes: 0
Labels: Agent, Crashing, Redhat, linux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Enterprise Linux release 8.5 (Ootpa)
Linux 4.18.0-348.20.1.el8_5.x86_64

Attachments: Text File Zabbix Agent crashing.log    
Issue Links:
Sub-task
Team: Team I
Sprint: Sprint 89 (Jun 2022), Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Product delivery backlog, Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023), Sprint 107 (Dec 2023), S2401, S25-W6/7
Story Points: 1

 Description   

Steps to reproduce:

  1. Deploy Zabbix Agent on Linux servers Red Hat Enterprise Linux release 8.5 (Ootpa)
  2. Start Zabbix agent
  3. Agent is starting, various processes are started but  after 5 seconds it crashed on SIGSEGV
  4. I tried various agent versions - all behave the same:
    zabbix_agent-5.4.9-linux-2.6-amd64-static
    zabbix_agent-5.4.12-linux-3.0-amd64-static
    zabbix_agent-5.4.12-linux-2.6-amd64-static
    zabbix_agent-5.0.24-linux-2.6-amd64-static
    zabbix_agent-4.0.41-linux-2.6-amd64-static
  1. We are using Zabbix Server 5.4.9, and about 160 Agents running on various OS - Solaris, older Red Hat Linuxes, Windows etc. On those servers all is running properly.
    Problem happening just on new Red Hat servers 8.5.
    This new OS version will be deployed on more servers in the future so it is serious problem for our organization.

Result:
See log file...

Expected:
Agent is running years without any error



 Comments   
Comment by Jurijs Klopovskis [ 2022 Jun 08 ]

We should at least provide standalone agents for 4.* and 5.* kernels.

Comment by Jurijs Klopovskis [ 2022 Jun 08 ]

Is there any reason why using rpms from repo.zabbix.com is not an option, nalim27 ?
https://www.zabbix.com/download?zabbix=6.0&os_distribution=red_hat_enterprise_linux&os_version=8

Comment by Milan Gvozdik [ 2022 Jun 09 ]

Hello,
 we are not using standard repo version because we are application admins, and we don't have root access.
Secondary, it allows us to use much newer versions of Zabbix agent. 
We are using Zabbix successfully 10 years, from version 2.x on different OS - Solaris, Windows, Linux. Problem exists in the latest servers where Red Hat 8.0 is installed by default.

One important note:
I found a workaround for this problem - when I define Server via IP address and not via hostname then agent stops crashing and works correctly, BUT Active check server must be disabled completely! 
It was very strange because standard Unix utilities (ping, telnet, nc) works with Zabbix server hostname correctly, just Zabbix agent have this problem.
I tested ping, telnet to port 10050  all works both with server hostname and IP address.

So problem must be somewhere in network Zabbix library (or network Zabbix source code) - on new RedHat machines it is not working correctly with full domain hostnames.

Comment by Milan Gvozdik [ 2022 Jun 28 ]

Hello,
 just my thinking - maybe problem will be solved if you provide binnary Zabix agent compiled on new Linux kernels too - like you already have version for kernels:

  • 2.4
  • 2.6
  • 3.0

our Red Hat 8.0 have kernel 4.18

Comment by Juris Lambda [ 2023 Jul 20 ]

Hi, nalim27!

Apologies for the long wait there.

The reason the static agents don't work is because these were built with glibc targeting the 2.x and 3.x kernels at the time, as you already noted.

I'm trying to figure out if we have a userbase that requires an entirely static agent (i.e. one that would include all the libraries and a copy of glibc), which may or may not work on some kernels, or if an agent with static libraries (such as openssl, pcre, curl), but dynamic libc loading, would be sufficient. The latter would probably work on most systems and would be built on a per-distribution/version basis (so, separate builds for, say, RHEL 7, 8 and 9).

If I get enough feedback on this, we'll consider adding such builds and publishing them on a permanent basis.

Generated at Mon May 26 07:54:55 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.