Zabbix 7.0: custom global scripts executed on server instead of proxy

[PsP]

Custom global scripts defined as Execute on "Zabbix proxy or server" are always started on server (as per logs trace).
Official doc states:"Zabbix proxy or server - the script will be executed by Zabbix proxy or server - depending on whether the host is monitored by proxy or server."

Any thoughts?

[Markku]

If you think that's a bug (you did ask this earlier already), you can open a ticket in the Zabbix support portal (shortlink).

Markku

[PsP]

I will do. Sorry for double post.
Thanks for your feedback.

[Markku]

I didn't find an issue for this, so I opened one: ZBX-24800 ("Remote command not executed on proxy but on server")

Please vote for that issue if you experience the same problem.

Markku

[PsP]

Thanks Markku, we have exactly the problem you described. Since we use this method for many pro-active actions, as a temporary workaround for our high priority actions here is one (less than ideal) solution:

1. On every proxy install zabbix-agent2
2. Move the Command defined in Action Script from the server to the relevant Proxy (or Proxies) as UserParameter
3. Invoke the Action Script using zabbix_get command passing the right Proxy as a parameter (defined for example as a tag in the trigger): zabbix_get -s {EVENT.TAGS.proxyagent} -k CommandName[...]

Of course in this way we have to "statically" indicate the proper Proxy that monitor the host instead of using the one defined in the standard configuration...

[PsP]

Upgraded to v7.0.1, same issue (actually ZBX-24800 in not present on release notes as fixed).

[Markku]

Yeah, there isn't any kind of progress logged yet in the issue.

Markku

[PsP]

Just a quick update: thanks to Markku the issue has been raised and managed. It is currently under QA state.

[PsP]

I can confirm that v.7.0.3 fixes ZBX-24800. Custom global scripts are now properly executed.