Hello everyone,
I am running Zabbix 7.4 on Windows hosts using Zabbix Agent 2, and I’m facing an issue where the same system.run command works in Manual Host Action, but fails when executed through a Trigger Action.
What works
In my zabbix_agent2.conf, I have explicitly allowed the command:
AllowKey=system.run[powershell.exe -Command "Restart-Service -Name 'service.service.service.exe' -Force"]
To test, I created a manual host action (Alerts → Scripts → Scope: Manual host action) with:
powershell.exe -Command "Restart-Service -Name 'Interflex.Workflow.Wakeup.exe' -Force"
When I manually execute this from the host’s frontend:
It works perfectly.
The service restarts, no errors.
What fails
Using the same exact script inside an Action → Operations (trigger-based automatic action), Zabbix shows the following error:
Unknown metric system.run
Agent 2 starts without error when using only AllowKey with a specific command
The manual execution confirms that the agent accepts this system.run key
The trigger action fails every time
Problem Summary
The Zabbix Agent allows this specific system.run[...] command when run manually, but rejects the same command when called automatically by a Trigger Action.
It looks like system.run is not treated the same way between:
Manual host actions (works)
Trigger actions (Unknown metric system.run)
What I need help with
Is this a known limitation or bug in Zabbix 7.4?
Does Zabbix handle manual actions and trigger-based actions differently regarding system.run permissions or AllowKey validation?
Is there some additional setting required for agent-initiated execution triggered from the server?
System info
Zabbix Server: 7.4
Zabbix Agent: Zabbix Agent 2 (Windows)
Windows Server 2019
Single host test environment
Any help, clarification, or confirmation would be greatly appreciated.
Thank you!
I am running Zabbix 7.4 on Windows hosts using Zabbix Agent 2, and I’m facing an issue where the same system.run command works in Manual Host Action, but fails when executed through a Trigger Action.
What works
In my zabbix_agent2.conf, I have explicitly allowed the command:
AllowKey=system.run[powershell.exe -Command "Restart-Service -Name 'service.service.service.exe' -Force"]
To test, I created a manual host action (Alerts → Scripts → Scope: Manual host action) with:
powershell.exe -Command "Restart-Service -Name 'Interflex.Workflow.Wakeup.exe' -Force"
When I manually execute this from the host’s frontend:
It works perfectly.
The service restarts, no errors.
What fails
Using the same exact script inside an Action → Operations (trigger-based automatic action), Zabbix shows the following error:
Unknown metric system.run
Agent 2 starts without error when using only AllowKey with a specific command
The manual execution confirms that the agent accepts this system.run key
The trigger action fails every time
Problem Summary
The Zabbix Agent allows this specific system.run[...] command when run manually, but rejects the same command when called automatically by a Trigger Action.
It looks like system.run is not treated the same way between:
Manual host actions (works)
Trigger actions (Unknown metric system.run)
What I need help with
Is this a known limitation or bug in Zabbix 7.4?
Does Zabbix handle manual actions and trigger-based actions differently regarding system.run permissions or AllowKey validation?
Is there some additional setting required for agent-initiated execution triggered from the server?
System info
Zabbix Server: 7.4
Zabbix Agent: Zabbix Agent 2 (Windows)
Windows Server 2019
Single host test environment
Any help, clarification, or confirmation would be greatly appreciated.
Thank you!
Comment