-
Problem report
-
Resolution: Unresolved
-
Trivial
-
None
-
5.0.0alpha2
Problem description: when configuring zabbix agent to be able to allow remote commands, the following message can be seen next to the EnableRemoteCommands parameter in zabbix_agentd.conf:
EnableRemoteCommands - Deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead
The same message is observed when starting zabbix agent.
But if the EnableRemoteCommands key is actually replaced by DenyKey and AllowKey parameters, system.run items become unavailable and the following error is returned:
Remote commands are not enabled.
Steps to reproduce:
1 - Open zabbix_agentd.conf and set the following configuration
DenyKey=some.key
AllowKey=system.run[*]
Comment or remove EnableRemoteCommands parameter
2 - Open zabbix frontend and open configuration of any existing host
3 - Add the following item to the host:
Type: zabbix agent
Key: system.run[echo 1]
4 - Start zabbix server and zabbix agent. Note that the following warning is displayed when starting zabbix agent:
zabbix_agentd [4943]: Warning: EnableRemoteCommands parameter is deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead
5 - Open the previously created item and press "Execute now" button
Result: The system.run item becomes unavailable. The following error is returned:
Remote commands are not enabled.
Expected: Configuration file and warning message stated that EnableRemoteCommands flag is depricated, therefore it should not be mandatory when using system.run items if such items are configured in Allow.Key parameter.
- caused by
-
ZBXNEXT-1085 restrict available checks on the agent side
- Closed