-
New Feature Request
-
Resolution: Fixed
-
Major
-
None
-
Debian 5.0.3
-
Sprint 1, Sprint 2, Sprint 3, Sprint 4, Sprint 5, Sprint 8
-
10
This is the topology I tested:
(LAN1) Zabbix Server -> (LAN2) Zabbix Proxy -> (LAN2) Zabbix Agent
I've configured a basic item and linked trigger. They work good.
Then, I created an action for that trigger, which basically send an email to me and execute a remote command. When the trigger runs the action, the email is sent ok, but the remote command is not executed in the monitored machine (the one with Zabbix Agent).
The remote command, for instance, may look like this:
{HOSTNAME}:sudo /tmp/test.sh 1
(But I tried other simplier commands and they didn't work either)
If I configured the same (and I mean the same) item, trigger, action and remote command with the following topology it works:
(LAN2) Zabbix Server -> (LAN2) Zabbix Agent
So, it seems like Zabbix proxy do not proxy remote commands.
- causes
-
ZBX-13241 Memory leak when executing remote commands through proxy
- Closed
-
ZBX-13245 Unreliable Zabbix server response to Zabbix proxy
- Closed
-
ZBX-13403 Proxy does not execute remote commands on agents with encryption
- Closed
-
ZBX-15442 Zabbix proxy ignores DataSenderFrequency
- Closed
- depends on
-
ZBX-12936 'Last seen (age)' updates only when Heartbeat message was sent, ignores the value successful update
- Closed
-
ZBX-12018 Publish new templates for monitoring task manager process
- Closed