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

zabbix_server crash on macro expansion with invalid value

    XMLWordPrintable

Details

    • Problem report
    • Resolution: Fixed
    • Minor
    • 3.4.12rc1, 4.0.0alpha9, 4.0 (plan)
    • 3.4.11, 4.0.0alpha8
    • Server (S)
    • "zabbix appliance image (Ubuntu)" on HyperV
      /usr/sbin/zabbix_server --version
      zabbix_server (Zabbix) 3.4.2
      Revision 72885 25 September 2017, compilation time: Sep 26 2017 11:11:28
    • Team A
    • Sprint 37
    • 0.125

    Description

      Steps to reproduce:

      1. Have some process discovery and item prototypes for monitoring memory usage
      2. Have a macro {$PROC_MAX_MEMORY:someProcessName} with value '1G'
      3. Have some trigger(prototype) using an expression containing the context-macro ie. '{discovered item} > {$PROC_MAX_MEMORY:"{#PROCNAME}"}'
      4. Change the amount of allowed memoryUsage and make some typo by changing the value to '1GG'

      I didn't test these exact steps, but I came across this problem. suddenly zabbix_server crashed and after restart it immediately crashes again. After thinking and double-checking the changes I made, and the 'DCexpression_expand_user_macros' in the backtrace, I noticed this typo. Removing the double 'G' fixed the issue, the server started again without issues.

      Result:
      zabbix_server crashes
      See backtrace (attachment)

      Expected:
      Some 'Not Supported' state with some indication there is an issue with a trigger expression

      Attachments

        1. objdump_DSswx.gz
          7.21 MB
          Andy Bertier
        2. zabbix_server_backtrace.log
          3 kB
          Andy Bertier
        3. zabbix_server_logAtCrash.log
          223 kB
          Andy Bertier

        Issue Links

          Activity

            People

              vso Vladislavs Sokurenko
              abertier Andy Bertier
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: