Ad Widget

Collapse

triggers firing - actions not

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • milosz
    Junior Member
    • Jan 2007
    • 5

    #1

    triggers firing - actions not

    hi all,

    i'm setting up a new install of 1.1.4 on an ubuntu dapper vm and i've run into an irritating problem with actions. i've successfully set up two test windows hosts with the windows_t template. i've set up a test action to email on trigger = on.

    the triggers fire: when i shut down the machine, unreachable is set to "ON." as i understand it, at this point an action should fire and i should be emailed. however, the actions don't fire. nothing in the server log, nothing in monitoring > actions. searched around the forums and haven't found anything helpful (no one seems to have a problem as basic as this).

    anyone have any ideas?

    thanks,

    Milosz.
  • dantheman
    Senior Member
    • May 2006
    • 209

    #2
    Can you post a screenshot of your trigger config and your action config so we can make sure it's setup correctly?

    Comment

    • milosz
      Junior Member
      • Jan 2007
      • 5

      #3
      ok, here they are.
      Attached Files

      Comment

      • milosz
        Junior Member
        • Jan 2007
        • 5

        #4
        here's a relevant snippet from the debug logs:

        <code>
        008854:20070119:171716 In update_trigger_value. Before apply_actions. Triggerid [12214] prev [0] curr [1] new [0]
        008854:20070119:171716 In apply_actions(triggerid:12214,alarmid:158,trigger_ value:0)
        008854:20070119:171716 Applying actions
        008854:20070119:171716 Executing query:select actionid,userid,subject,message,recipient,maxrepea ts,repeatdelay,scripts,actiontype from actions where status=0
        008854:20070119:171716 SQL [select actionid,userid,subject,message,recipient,maxrepea ts,repeatdelay,scripts,actiontype from actions where status=0]
        008854:20070119:171716 In check_action_conditions [actionid:1]
        008854:20070119:171716 Executing query:select conditionid,actionid,conditiontype,operator,value from conditions where actionid=1 order by conditiontype
        008854:20070119:171716 In check_action_condition [actionid:1,conditionid:7:cond.value:1]
        008854:20070119:171716 Condition is FALSE
        008854:20070119:171716 Conditions are FALSE
        008854:20070119:171716 Conditions do not match our trigger. Do not apply actions.
        008854:20070119:171716 In check_action_conditions [actionid:2]
        008854:20070119:171716 Executing query:select conditionid,actionid,conditiontype,operator,value from conditions where actionid=2 order by conditiontype
        008854:20070119:171716 Conditions are TRUE
        008854:20070119:171716 Conditions match our trigger. Do apply actions.
        008854:20070119:171716 In substitute_macros([{TRIGGER.NAME}: {STATUS}])
        008854:20070119:171716 In substitute_simple_macros [{TRIGGER.NAME}: {STATUS}]
        008854:20070119:171716 In substitute_simple_macros [Processor load is too high on {HOSTNAME}]
        008854:20070119:171716 Executing query:select distinct h.host from triggers t, functions f,items i, hosts h where t.triggerid=12214 and f.triggerid=t.triggerid and f.itemid=i.itemid and h.hostid=i.hostid
        008854:20070119:171716 Result expression [Processor load is too high on copier351.lsny.org]
        008854:20070119:171716 Result expression [Processor load is too high on copier351.lsny.org: OFF]
        008854:20070119:171716 Result expression:Processor load is too high on copier351.lsny.org: OFF
        008854:20070119:171716 In substitute_macros([{TRIGGER.NAME}: {STATUS}])
        008854:20070119:171716 In substitute_simple_macros [{TRIGGER.NAME}: {STATUS}]
        008854:20070119:171716 In substitute_simple_macros [Processor load is too high on {HOSTNAME}]
        008854:20070119:171716 Executing query:select distinct h.host from triggers t, functions f,items i, hosts h where t.triggerid=12214 and f.triggerid=t.triggerid and f.itemid=i.itemid and h.hostid=i.hostid
        008854:20070119:171716 Result expression [Processor load is too high on copier351.lsny.org]
        008854:20070119:171716 Result expression [Processor load is too high on copier351.lsny.org: OFF]
        008854:20070119:171716 Result expression:Processor load is too high on copier351.lsny.org: OFF
        008854:20070119:171716 Executing query:select mediatypeid,sendto,active,severity,period from media where active=0 and userid=3
        008854:20070119:171716 Trigger severity [3] Media severity [0] Period [1-7,00:00-23:59;]
        008854:20070119:171716 Won't send message
        008854:20070119:171716 Actions applied for trigger 12214 0
        008854:20070119:171716 Executing query:update services set status=0 where triggerid=12214
        008854:20070119:171716 Executing query:select serviceid from services where triggerid=12214
        008854:20070119:171716 End of update_triggers [17216]
        </code>

        looks like zabbix is applying the action and attempting to fire it... can anyone show me a debug log snippet of a successfully fired action?

        Comment

        • Alexei
          Founder, CEO
          Zabbix Certified Trainer
          Zabbix Certified SpecialistZabbix Certified Professional
          • Sep 2004
          • 5654

          #5
          It looks like trigger severity doesn't match list of severities defined for your
          user's media (obviously email).
          Alexei Vladishev
          Creator of Zabbix, Product manager
          New York | Tokyo | Riga
          My Twitter

          Comment

          • milosz
            Junior Member
            • Jan 2007
            • 5

            #6
            thanks alexei, i actually figured that out last night, when i created the user medium i hadn't checked off any of the trigger severity boxes...

            why did you guys decide to make it possible for a setting in user media to affect whether an action fires or not? that doesn't really make sense to me, which is part of why it took me so long to figure this out. i mean, you can already set a trigger severity condition in the action itself, does setting it in the medium provide you with any extra level of functionality that's worth the potential headache? it just seems like it adds an unnecessary level of complexity.

            just wondering about that.

            Milosz.

            Comment

            • Alexei
              Founder, CEO
              Zabbix Certified Trainer
              Zabbix Certified SpecialistZabbix Certified Professional
              • Sep 2004
              • 5654

              #7
              You may have high-severity events sent by SMS, other by Email, for example.
              Alexei Vladishev
              Creator of Zabbix, Product manager
              New York | Tokyo | Riga
              My Twitter

              Comment

              • tigerx
                Junior Member
                • Oct 2006
                • 3

                #8
                I'm also experiencing such a problem and took the advice but i still getting triggers being fired and not actions. i am using zabbix 1.1.4 as well.
                Attached Files

                Comment

                Working...