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

Events with wrong timestamp during high load on zabbix server -> wrong Availability report

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • None
    • 1.8.10
    • Frontend (F), Server (S)
    • Linux (EL 6), Mysql (5.1)

      Sometimes we observe a situation when zabbix produces false positive alerts (based on trigger

      {agent.ping.nodata(180)}

      =1) during high IO load on the server (i.e. while running a backup on FS, which holds the zabbix database). We suppose that this leads to a problem when events are stored in switched order, which is probably caused by wrong clock values. Although the event IDs seem to be stored in right order (please see the attached pictures). The Availability report generates then graphs with hosts mostly down.

      Maybe this is somehow related to #ZBX-4466.

        1. e0.png
          192 kB
          Daniel Kontsek
        2. e1.png
          192 kB
          Daniel Kontsek
        3. O_new_trigger_error.jpg
          250 kB
          Oleksii Zagorskyi
        4. zabbix_1.png
          14 kB
          Cristian Mammoli
        5. zabbix_2.png
          5 kB
          Cristian Mammoli

            Unassigned Unassigned
            dano Daniel Kontsek
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: