Action - remote command is removed but still the triggers running remote commands

[registration_is_lame]

Hi,

We have a item which collects PID and a trigger based on that
We had enabled run remote command to kill the pid based on other items. (powershell -c "taskkill {#ITEM.VALUE1}

So it worked as expected. Whenever the alert comes in, in the email we will have the PID. And when it recovers, it'll have a new PID in the email.

Due to some problem I had to disable remove the remote action.

But even after that, we saw triggers and recovery in which the PID was new.
This means that the zabbix was still running the (powershell -c "taskkill {#ITEM.VALUE1}) command even though it was removed from action.

So I enabled debugging on the Agent and on the server (debuglevel=4).

But we did not notice any taskill comamnd run on both the logs(server and agent) and still it was restarting during every trigger.

how could this be happening?

I tested by creating another action with remote commnad "powershell -c "echo test"" and it was logged on the agent and on zabbix server log.

At last we had to remove the template and items.

Any idea what could be the problem? How could it run commands without even logging into the logs?

Thanks

[registration_is_lame]

Figured out the issue. The application was restarting itself and conflicted with zabbix polling time. Glad it isn't zabibx causing it.