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

Double notification messages (double-generated alert)

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 1.9.9 (beta)
    • None
    • Server (S)
    • last trunk revision 13781

      See attached screen shot.
      I can not understand when and why this happens (there is an assumption that it is connected with the moment when the server updates the cache configuration).
      Server debuglog exists and if you want I can send directly to the developers.

      My config (easy to understand that in the picture, the problem is not relevant):
      DEBUG

      {HOSTNAME}

      :

      {STATUS}

      |

      {ITEM.NAME}

      | EVENT.ID:

      {EVENT.ID}

      | Server timestamp =

      {DATE}

      {TIME}

      | TRIGGER.NAME:

      {TRIGGER.NAME}

      ***************************************************
      ITEM.VALUE1:

      {ITEM.VALUE1}

      ITEM.LOG.EVENTID1:

      {ITEM.LOG.EVENTID1}

      ITEM.LOG.SOURCE1:

      {ITEM.LOG.SOURCE1}

      ITEM.LOG.AGE1:

      {ITEM.LOG.AGE1}

      ***************************************************
      ITEM.LASTVALUE1:

      {ITEM.LASTVALUE1}

        1. 1_double_message_#1.png
          1_double_message_#1.png
          39 kB
        2. 2_double_message_#2.png
          2_double_message_#2.png
          37 kB
        3. 2action.log
          6 kB
        4. 3_double_message_#3.png
          3_double_message_#3.png
          38 kB
        5. rev24046_improvement.png
          rev24046_improvement.png
          86 kB
        6. rev24046_improvement+DB_usage.png
          rev24046_improvement+DB_usage.png
          114 kB
        7. zabbix_server_patched.log.gz
          90 kB
        8. ZBX-2806-trunk.patch
          1 kB

            Unassigned Unassigned
            zalex_ua Oleksii Zagorskyi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: