EnableRemoteCommands Vs AllowKey

[nathanm]

Hi Everyone

We are using Zabbix 5.0 to monitor a number of Windows servers, and I have been trying to use remote commands to restart Windows services when they stop, however I'm having issues when following the documentation.

I followed Dmitry Lambert's blog (https://blog.zabbix.com/zabbix-remote-commands/7500/), but when editing the zabbix_agentd.conf file it states that "EnableRemoteCommands" function has been depreciated and advises to use "AllowKey" instead.
e.g. "Option: EnableRemoteCommands - Deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead"

If I add AllowKey=system.run[*] to the zabbix_agentd.conf and then restart the Zabbix agent service, it fails to start. I also tested with DenyKey=system.run[*] and it's the same problem - the agent service fails to start.

Eventually out of frustration I decided to just try "EnableRemoteCommands=1" and it worked! Even though it's clearly stated that this is replaced with AllowKey, I still need to use EnableRemoteCommands in order to enable that functionality.

I'm happy that it's working, but I'm concerned that I've misconfigured something for this to be the case.

Have I missed something?

Thank you
Nathan

[jsrozo]

Maybe is a space in the command or character invalid.
So weird. The command is ok. You can copy the command in notepad and reviewed.

[bbrendon]

You might have an old agent that doesn't support

AllowKey=system.run[*]