Ad Widget

Collapse

Empty host name provided in expression

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nleaman
    Member
    • May 2010
    • 35

    #1

    Empty host name provided in expression

    I am having trouble tracking down what is causing this error when saving a trigger:

    Code:
    Trigger "{HOSTNAME} is not reachable via ICMP PING" updated for host "abc.domain.com"
    Empty host name provided in expression.
    Check expression part starting from " {:icmpping.avg(300)}#1 "
    Trigger "{HOSTNAME} is not reachable via ICMP PING" updated for host "xyz.domain.com"
    Checked the hosts table and didn't see any obvious errors in hostnames. There are enough hosts that this trigger is assigned to that it's been tricky to find any host by process of elemination.

    I have debug logging on, but failed to find anything.

    Any pointers on where to look? I'm rather new to Zabbix so I am sure I overlooking something.
  • xibbaz
    Member
    Zabbix Certified Specialist
    • Jun 2009
    • 74

    #2
    Did you put {HOSTNAME} in the trigger expression? If so, it is not supported there. You must put the host name (not dns) or, if in a template, the template name.

    Comment

    • nleaman
      Member
      • May 2010
      • 35

      #3
      no, pretty straight forward expression I think:

      {t_ICMP:icmpping.avg(300)}#1

      Fortunately/unfortunately I the issue got resolved without me figuring out why. In the hopes of trying to narrow down if the problem was happening to a particular host, I unlinked the template from all hosts, then one by one linked it again. As I linked it to a new host, I would try a save of the trigger to see if the error would occur. I ended up linking it back to all the original hosts without finding a problem. So I somehow cleaned it up.

      Now that I am not able to recreate the error, It likely going to be very difficult to figure it out.
      Attached Files

      Comment

      • xibbaz
        Member
        Zabbix Certified Specialist
        • Jun 2009
        • 74

        #4
        Lets hope you fixed it and it will never come back

        Comment

        Working...