should we forget actions?

[kopspa]

i'd like to know WHY actions are NOT working at all!
and why nobody answer to this problem, this is not the first post and i'm not the first person that has this problem...


{test.hostroc.num[apache2].last(0)}<1 is the trigger

the action is configured, so if i do /etc/init.d/apache2 stop, the trigger become red, and the action starts...
in fact on monitoring - actions, i can see the mail sent (and in mailbox too)

if i do /etc/init.d/apache2 stop, on a SECOND host, configured with the same items/triggers, zabbix doesn't do nothing (triggers goes red, but no action)...

same thing for other triggers/actions.

why it works when it wants? it's a bug? i remember that older beta were bugged, but developers tells that the 1.1 is fixed...

[Alexei]

How are your actions configured?

[kopspa]

Action type send messages
Source trigger
Conditions Trigger = "Apache"

Send message to single user
User admin

subject {IPADDRESS}
message is irrilevant


Trigger Apache IS {test.host: proc.num[apache2].last(0)}<1 without the space... btw :

[stever]

Triggers and actions are working for us.

for example, I have this trigger defined:
({craig:usr.icutil.last(0)}<1)&({craig:usr.icutil. prev(0)}<1)

And a corresponding action, with the condition Trigger = "trigger name"

I get emails when its down. Make sure you test that your trigger is working, and not just the action.

[kopspa]

all the triggers i've configured are working
for example if i stops asterisk, or apache, or mysql or any services that zabbix is monitoring, the triggers become red (and then green if i start them)

i've no ideas...

[kopspa]

strange, if i set a actions based on 'trigger value' or 'trigger severity' it works

[kurt]

before i upgraded to 1.1, i was using 1.1beta4. My database became corrupt, and after repairing it, my triggers would fire, but the actions woulndn't fire.

So i had to re-add the triggers. once i did that, they all worked again...

I never found an easier solution, but that one worked

[Alexei]

If your database was seriously corrupt, I would suggest unloading of all data and recreation of the database from scratch.