Ad Widget

Collapse

Triggers without host and associated with *UNKNOWN* hostname

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • LEMORALES
    Junior Member
    • Sep 2014
    • 10

    #1

    Triggers without host and associated with *UNKNOWN* hostname

    Hi Forum

    I have upgraded my Zabbix server from 2.2.5 to 2.4.7 without issues following the upgrade notes for the version.

    After the upgrade, which ended sucessfully, the dashboard shows me 4 of 57 issues, the four issues are real, but I don't know from where comes the other 53 issues; those items aren't shown in the dashboard:

    [IMG] subir imagenes[/IMG]

    Looking for from where these "pseudo-issues" could come, I have found these in monitoring->triggers, and those items are shown without a host, with an age greater than a year (Almost the time since the server was installed) and with a host name labeled as *UNKNOWN*:

    [IMG][/IMG]

    All these triggers are associated to several hosts through templates. I'm not sure how to get rid of these triggers without host, what I'm guessing is that these triggers not shown in the dashboard and not associated with a host are orphaned records in the database left by previous versions of Zabbix (my server has been upgraded 2 times in the past two years, begining in 2.0), shown in 2.4.7 release.

    Any suggestion about how to delete these triggers will be appreciated. Thanks a lot for taking the time to read this.

    Luis Morales.
  • syndeysider
    Senior Member
    • Oct 2013
    • 115

    #2
    Tagging myself in so I can get updated when you find a solution. I've got a smiliar problem both with "Blank" host and also "No Events" under the Acknowledge column all mixed and matched....

    I upgraded from 2.0.7 -> 2.4.2 -> 2.4.7 recently.

    Comment

    • ingus.vilnis
      Senior Member
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Mar 2014
      • 908

      #3
      Hi,

      One "dirty" solution would be to select such triggers from the database and then set them to OK state.

      This query selects ALL triggers (good ones in real problem state as well).
      Code:
      select * from triggers where value=1;
      Then for selected bad triggers you can set value=0. But be very careful! Don't do this for orphaned triggers with no hosts and no events.

      Hope this helps!

      Best Regards,
      Ingus

      Comment

      • BDiE8VNy
        Senior Member
        • Apr 2010
        • 680

        #4
        I had encountered the very same with Zabbix 2.2. I solved it by deleting these orphaned triggers manually from the database. If I recall right, then these were mostly, if not all, related to LLD.

        Comment

        • LEMORALES
          Junior Member
          • Sep 2014
          • 10

          #5
          Hi Ingus, Hi BDiE8VN

          Thank you so much both of you for your suggestions. At the end, I solved my problem through the BDiE8VN's solution, but thanks to the answer from Ingus, I have known where and how look for.

          problem solved!

          Comment

          Working...