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

Server crash with incorrect string in preprocessing step

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Cannot Reproduce
    • Icon: Trivial Trivial
    • None
    • 5.4.1, 5.4.2
    • None
    • None
    • Ubuntu 20.04, mysql 14.14, zabbix installed from package repository

      Steps to reproduce:

      1. create preprocessing step in discovery with the following syntax in an item prototype

      Result:

      See forum entry Zabbix Server 5.4.1 and 5.4.2 crash - ZABBIX Forums

      mysql> select item_preprocid,params from item_preproc where params like '%display_name%';
      +----------------+--------------------------------------------------+
      | item_preprocid | params                                           |
      +----------------+--------------------------------------------------+
      |         167069 | $.[?(@.display_name =~ "floating")].display_name |
      |         167070 | $.[?(@.display_name =~ "floating")].display_name |
      |         167071 | $.[?(@.display_name =~ "floating")].display_name |
      

      Expected:

      We removed the entries from the database with

       

      mysql> delete from item_preproc where params like '%display_name%';
      Query OK, 286 rows affected (0.01 sec)
      mysql> delete from item_rtdata where error like '%display_name%';
      Query OK, 286 rows affected (0.08 sec)
      
      

      and the issue is gone

       

        1. image-2021-06-30-21-17-30-986.png
          44 kB
          Johannes Hauf
        2. image-2021-07-02-13-16-14-929.png
          8 kB
          Johannes Hauf
        3. image-2021-07-02-13-17-38-183.png
          5 kB
          Johannes Hauf

            zalex_ua Oleksii Zagorskyi
            johansenfa Johannes Hauf
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: