Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    zabbix-agent7 Crashing

    Scheduled Pinned Locked Moved pfSense Packages
    1 Posts 1 Posters 82 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N Offline
      neuf_16
      last edited by

      I'm running into an issue across multiple sites where the zabbix-agent7 will 'randomly' crash and not come back.
      I haven't made any changes to the Zabbix server items and the issue did not happen on zabbix-agent6.
      Wondering if any one else has run into this?

      Here are the logs I see every time it crashes.
      The "Active check data upload started to fail" errors have always been there which is a potential problem but never had the SIGBUS crash issue before.

      86155:20260429:035229.506 Active check data upload started to fail
      86155:20260429:035232.798 active check data upload to [zabbixserver-ipv6:10051] is working again
      86155:20260429:113810.527 Unable to connect to [zabbixserver-ipv6]:10051 [cannot connect to [[zabbixserver-ipv6]:10051]: connection timed out]
      86155:20260429:113810.527 Active check data upload started to fail
      86155:20260429:113818.847 Got signal [signal:10(SIGBUS),reason:3,refaddr:0x2795b3]. Crashing ...
      86155:20260429:113818.847 ====== Fatal information: ======
      86155:20260429:113818.847 program counter not available for this architecture
      86155:20260429:113818.847 === Registers: ===
      86155:20260429:113818.847 register dump not available for this architecture
      86155:20260429:113818.847 === Backtrace: ===
      86155:20260429:113818.848 15: 0x269fab <zbx_backtrace+0x4b> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.848 14: 0x26a142 <zbx_log_fatal_info+0x92> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.848 13: 0x26a9ab <zbx_set_common_signal_handlers+0x21b> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.848 12: 0x823b648aa <pthread_sigmask+0x54a> at /lib/libthr.so.3
      86155:20260429:113818.848 11: 0x823b63e6b <pthread_setschedparam+0x85b> at /lib/libthr.so.3
      86155:20260429:113818.848 10: 0x82106b2d3 <???> at ???
      86155:20260429:113818.848 9: 0x2795b3 <zbx_json_next+0xe3> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.848 8: 0x27a2e7 <zbx_json_pair_next+0x27> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 7: 0x27a6c3 <zbx_json_value_by_name+0x53> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 6: 0x24243a <active_checks_thread+0x372a> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 5: 0x240f25 <active_checks_thread+0x2215> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 4: 0x267c3c <zbx_thread_start+0x2c> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 3: 0x23bc2b <MAIN_ZABBIX_ENTRY+0x3fb> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 2: 0x269c59 <zbx_daemon_start+0x1e9> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 1: 0x23c550 <main+0x510> at /usr/local/sbin/zabbix_agentd
      86155:20260429:113818.849 0: 0x8280ec9a5 <__libc_start1+0x145> at /lib/libc.so.7
      86155:20260429:113818.849 === Memory map: ===
      86155:20260429:113818.849 memory map not available for this platform
      86155:20260429:113818.849 ================================
      84798:20260429:113818.850 One child process died (PID:86155,exitcode/signal:1). Exiting ...
      84798:20260429:113818.852 Zabbix Agent stopped. Zabbix 7.0.6 (revision c1d7a081969).
      
      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.