Trigger not sending action

[authex]

Hi there,

CONFIGURATION:
Item (script):

[B]60 seconds  [/B]Type of information = Text

When the item returns an acceptable response, it returns

HTTP/1.1 200 OK

Trigger:

{zabbix:ScriptCheck.regexp(HTTP/1.1 200 OK,1m)}=0

Action: Start a remote command (script) at D:\Zabbix\Script\Script1.bat

PROBLEM:
Last night, the item triggered as down, but the action script did not run. We had to manually get into the system to restart the service. After we did that, Zabbix saw the correct response and it brought the trigger as good.

any ideas?

[ingus.vilnis]

Hi,

Can you check zabbix_agend.conf file on that host and verify that you have set:

EnableRemoteCommands=1
LogRemoteCommands=1

Best Regards,
Ingus

[authex]

Hi there,
That's correct, those values are setup properly.

I forgot to mention, we had tested this before and it has worked just fine.
Last night the service went down but the trigger worked as expected, then this morning it went down but the trigger did not send the action.


any other ideas?

[ingus.vilnis]

Hi,

Let's separate two things here - trigger and actions.
Did the trigger go into PROBLEM state last night when you had the issue? If no, then the trigger is not adjusted properly and is not alarming on the required problems. Please check the Monitoring -> Events for this specific trigger.

Other thing are actions. If the trigger really was in Problem state, then maybe you have to look at the action conditions in Configuration -> Actions. Maybe some of the conditions were not met and therefore the script was not executed.

Best Regards,
Ingus

[authex]

Hi,

Let's separate two things here - trigger and actions.
Did the trigger go into PROBLEM state last night when you had the issue? If no, then the trigger is not adjusted properly and is not alarming on the required problems. Please check the Monitoring -> Events for this specific trigger.

Other thing are actions. If the trigger really was in Problem state, then maybe you have to look at the action conditions in Configuration -> Actions. Maybe some of the conditions were not met and therefore the script was not executed.

Best Regards,
Ingus

The trigger go into PROBLEM state, but the action did not begin.
As far as the configuration for the action, there's nothing out of the ordinary as far as conditions. It is just a trigger that went into a PROBLEM state, and it did not execute the script.