Remote commands aren't working

[ezoltan]

Hello community,

In my Zabbix 7.4 environment I have Server -> Proxy -> Agent (Windows server), all components at the latest version. Monitoring and alerting works perfectly.

I configured these two lines in my Windows agent config file and restarted the agent to prep the environment to take automatic remediation actions by means of trigger alerts and scripts:

AllowKey=system.run[*]
Plugins.SystemRun.LogRemoteCommands=1

As a first test I tried to run the built-in "Detect operating system" script against the agent. I am getting the famous "Remote commands are not enabled" error.

I looked in the server, proxy and agent log files, but I cannot find any trace of the command ever being attempted to run. Not even a faint mention. I searched the Internet far and wide to no avail.

Can you please point me into the right direction.

Thank you.

[ezoltan]

Ignore. I bumped into this thread: https://www.zabbix.com/forum/zabbix-...ric-system-run. I confirm it solved the problem.

Reading the Operations documentation at https://www.zabbix.com/documentation...g-an-operation, the "Target List" under "Operation type: remote command" is rather confusing:


Just look at the descriptions of "Current host", "Host" and "Host group". The way I read it there is no difference whatsoever: I want to run the command on any of the hosts that match the Host and Host group filter if the trigger is fired on those hosts. "Current host" makes no sense whatsoever and it is redundant. Meaningless. Confusing. Showstopper. Gray hair generator. Hair thinner.

Bottom line:
1. Must tick the "Current host" checkbox. No tick -> no script will run and you'll waste days trying to work out why.
2. Must specify the exact host in the Host field, or the host group of which my host is member of in the Host group field. You must still specify the scope of the action.

It would be nice if the documentation would disambiguate this section, or the entire remote command ecosystem as a matter of fact, as, in my experience, is one of the most used scenarios in an admin's life in terms of monitoring and automatic remediation.

Given how many have asked the same question, some consistency would be in order.

Having finished venting my frustration, I must also say that Zabbix is a great software and I love it. I am confident the documentation will catch up at some point.

[ezoltan]

Ignore. I bumped into this thread: https://www.zabbix.com/forum/zabbix-...ric-system-run. I confirm it solved the problem.

Reading the Operations documentation at https://www.zabbix.com/documentation...g-an-operation, the "Target List" under "Operation type: remote command" is rather confusing:


Just look at the descriptions of "Current host", "Host" and "Host group". The way I read it there is no difference whatsoever: I want to run the command on any of the hosts that match the Host and Host group filter if the trigger is fired on those hosts. "Current host" makes no sense whatsoever and it is redundant. Meaningless. Confusing. Showstopper. Gray hair generator. Hair thinner.

Bottom line:
1. Must tick the "Current host" checkbox. No tick -> no script will run and you'll waste days trying to work out why.
2. Must specify the exact host in the Host field, or the host group of which my host is member of in the Host group field. You must still specify the scope of the action.

It would be nice if the documentation would disambiguate this section, or the entire remote command ecosystem as a matter of fact, as, in my experience, is one of the most used scenarios in an admin's life in terms of monitoring and automatic remediation.

Given how many have asked the same question, some consistency would be in order.

Having finished venting my frustration, I must also say that Zabbix is a great software and I love it. I am confident the documentation will catch up at some point.