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

Problem/OK event status swapped for nodata trigger, probably only for data received via trapper (port 10051)

    XMLWordPrintable

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 2.2.7
    • Fix Version/s: None
    • Component/s: Server (S)
    • Labels:
      None
    • Environment:
      Ubuntu Vivid Linux

      Description

      When Zabbix receives external events and there is a trigger like

      {hostname:somedata.nodata(300)}

      sometimes trigger will have wrong status and stay in it. Consequence: dashboard shows trigger in state error while in reality it is not.

      This might be related to processing of burst of messages via trapper, but that is not proven. The burst occurs, when trapper data network stream was stalled due to network errors. After network errors a burst of timestamp sorted messages is inserted, but some may have timestamps dating back more than the nodata(timeout) value.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ait Roman Fiedler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: