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

Events may show wrongly PROBLEM events after maintenance

    XMLWordPrintable

Details

    Description

      After maintenance an escalation took place for a trigger that's actually in OK state:

      zabbix=# SELECT triggerid,
      zabbix-#        value,
      zabbix-#        lastchange
      zabbix-# FROM   triggers
      zabbix-# WHERE  triggerid = 526432;
       triggerid | value | lastchange 
      -----------+-------+------------
          526432 |     0 | 1408436420
      (1 row)
      
      zabbix=#
      

      While corresponding chronological last event is a PROBLEM event what is probably the cause for escalation:

      zabbix=# SELECT *
      zabbix-# FROM   events
      zabbix-# WHERE  eventid IN
      zabbix-#        (SELECT eventid
      zabbix(#         FROM   events
      zabbix(#         WHERE  objectid = '526432' AND
      zabbix(#                clock >= '1407845566' AND
      zabbix(#                clock <= '1408450366')
      zabbix-# ORDER  BY clock DESC,eventid DESC;
       eventid  | source | object | objectid |   clock    | value | acknowledged |    ns     
      ----------+--------+--------+----------+------------+-------+--------------+-----------
       23576348 |      0 |      0 |   526432 | 1408437901 |     1 |            0 |         0
       23574987 |      0 |      0 |   526432 | 1408436436 |     1 |            0 | 707712147
       23575405 |      0 |      0 |   526432 | 1408436420 |     0 |            0 | 480516079
       23446409 |      0 |      0 |   526432 | 1408027204 |     1 |            0 | 709559043
       23446605 |      0 |      0 |   526432 | 1408027166 |     0 |            0 | 128809786
      (5 rows)
      
      zabbix=#
      

      Now I wonder why two successive PROBLEM events exist and why the last one has 'ns' set to 0.

      Possibly it's related to ZBX-8558.

      Scenario:

      • Maintenance turned to active.
      • Zabbix-database has been stopped for ~10 minutes.
      • Took ~15 minutes after db start to recover normal operation (history sync, etc.)
      • After further ~10 minutes of normal operation maintenance expired
      • the primary timer process was busy for ~10 minutes (ZBX-8630 happened)

      Attachments

        Activity

          People

            Unassigned Unassigned
            okkuv9xh Marc
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: