Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-20649

Repeated crashes in History Syncer

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • 5.4.10
    • Server (S)
    • None
    • RHEL 8.5, Mysql 5.7.34, 768GB Ram, SSDs, PowerEdge R640
    • Sprint 85 (Feb 2022)
    • 0.5

      I apologize in advance that I can't send the backtrace since it is on a closed off network.
      There are repeated crashes occurring with the following:

      backtrace
      758715:20220222:121036.018 Got signal [signal:11(SIGSEGV),reason:128,readdr:(nil)]. Crashing ...
      758715:20220222:121036.018 ====== Fatal Information: ======
      758715:20220222:121036.018 Program counter:0x7ffff4adc6b7
      758715:20220222:121036.018 === Registers: ===
      ...Too much information to hand type...
      758715:20220222:121036.018 === Backtrace: ===
      758715:20220222:121036.018 16: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history](zbx_backtrace+0x35) [0x5767c5]
      758715:20220222:121036.018 15: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history](zbx_log_fata_info+0x29d) [0x576b5d]
      758715:20220222:121036.018 14: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history]() [0x576fe6]
      758715:20220222:121036.018 13: /usr/lib64/libpthread.so.0(+0x12c20) [0x7ffff7604c20]
      758715:20220222:121036.018 12: /usr/lib64/libc.so.0(+0x15d6b7) [0x7ffff4adc6b7]
      758715:20220222:121036.018 11: /usr/lib64/libc.so.0(+0x__strdup+0x12) [0x7ffff4a08802]
      758715:20220222:121036.018 10: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history](zbx_strdup2+0x33) [0x587a23]
      758715:20220222:121036.018 9: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history]() [0x51b902]
      758715:20220222:121036.018 8: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history](DCconfig_get_triggers_by_itemids) [0x52d488]
      758715:20220222:121036.018 7: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history]() [0x513d39]
      758715:20220222:121036.018 6: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history](dbsyncer_thread+0x17c) [0x544115c]
      758715:20220222:121036.018 5: /usr/share/zabbix/sbin/zabbix_server: history syncer #5 [processed 2 values, 5313 triggers in 0.155864 sec, syncing history](zbx_thread_start+0x20) [0x581c40]
      Rest of backtrace truncated since its just start, main, daemonstart, and MAIN_ZABBIX_ENTRY
      Then zabbix server gets stuck in an infinite loop with this log line:
      syncing history data... 99.166667%
      syncing history data... 99.166667%
      syncing history data... 99.166667%
      

      We've written a script to detect this and pkill -9 zabbix server and restart because the crash happens randomly.
      The crash has occurred 3 times since we upgraded to 5.4.10 10 days ago and happens every few days. If you need additional information, let me know and I can do my best to get it to you.

            wiper Andris Zeila
            GRyan337 Ryan Eberly
            Team A
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: