Possible BUG: Actions Self-Disabling

[btriem]

I have been having actions disabling on their own. This has happened twice now in the last few days.

This last time the two actions were:

Action 1: Trigger <> xxxx host unreachable (uses status)
Trigger severity = "High"
Trigger value = "ON"

Action 2: Trigger = "Server DITS.Linux is unreachable" (uses status)
Trigger value = "ON"

Both of these were disabled this morning when i was checking why I wasn't notified when a server was unavailable due its rebooting and the zabbix_agentd not restarting.

Zabbix server is running on FC3, version 1.1beta9, MySQL 5.0.20a, php 4.3.11-2.8

The only simularity I can find between both instances is I recall adding an action recently before the occurance. I do not remember which action(s) were disabled last time this occured, but it very well could have been the same two.

I searched the forums but didn't come up with anything, is there something that I have missed that can cause an action to auto-disable?

Thank you

[adam.vollrath]

Usually if an agent does not support a value (like status, which I believe has been deprecated) then the Zabbix server will disable monitoring of that key's value, and also its trigger.

Try setting your triggers to use another value that is still supported.

(edit): Also check both server and agent/client logs to make sure that value is supported.

[btriem]

You may be right....

You may be right on the deprecation of status. Allthough I did get alerts using status when a system was unavailable so it has not been removed as of 1.1beta9. It looks as if its new replacement is agent.ping.

Can anyone confirm/deny that if a server is unreachable and/or the agent is offline, that agent.ping is the proper way to determine this?

[makini]

indeed - confirmation needed from the developers...

so, to make it clear, was the "status" key depricated in 1.1 (or 1.1.1) ?
if so, what is the replacement for it in functionality? how can a host with "Unavailable" state be detected?

we're running 1.1.1 and the status there doesn't seem to return data or "Not supported" on the item in turn...

P.S.
self disabling Actions happened to me too - although these were initially and mistakenly assigned to monitor triggers in a template instead of a host or trigger name expression.

[Alexei]

I do confirm that there is a bug which leads to incorrect disabling actions in ZABBIX frontend. It is already fixed and will be released as part of 1.1.2. Here is fix for file triggers.inc.php, function delete_trigger:

$db_actions = DBselect("select distinct c.actionid from conditions c, triggers t".
" where c.conditiontype=".CONDITION_TYPE_TRIGGER.
" and c.value=t.triggerid and t.triggerid=".$triggerid);
while($db_action = DBfetch($db_actions))