Unable to launch scripts based on actions

[greenwulf]

Hello,

We are using Zabbix 7.0 LTS and we separated our proxy groups in two groups. Each group is using its own VMWare AVI load balancer

I have created a script and an action to restart a windows service when a trigger detects that this service is down.
The action performs as it should, but unfortunately, when I check, I can see that the script could not be run because the host sounds to not be associated to a proxy.
I was hoping this issue is LB related, but even if I change the Agent config file Server and ServerActive values to use the proxies names (comma separated) instead of the load balancer DNS name, I get the same error

I also checked in the Zabbix UI, the host appears with as a proxy assigned

Of course, I tried to associate the host to a specific proxy instead of using host group, and in this case, the scripts works like a charm. But this is definitely not what we want to use

Did someone else face this issue ? Any clue of what I could check or investigate to get it working with proxy groups ?

[greenwulf]

hello
Other option that could be investgated is to run the commands from the server instead of proxy groups
What should I take in consideration if I want to use it and not disturb the performances (we monitor approximatif 4000 hosts)

[cyber]

Hello,

We are using Zabbix 7.0 LTS and we separated our proxy groups in two groups. Each group is using its own VMWare AVI load balancer

I have created a script and an action to restart a windows service when a trigger detects that this service is down.
The action performs as it should, but unfortunately, when I check, I can see that the script could not be run because the host sounds to not be associated to a proxy.
I was hoping this issue is LB related, but even if I change the Agent config file Server and ServerActive values to use the proxies names (comma separated) instead of the load balancer DNS name, I get the same error

I also checked in the Zabbix UI, the host appears with as a proxy assigned

Of course, I tried to associate the host to a specific proxy instead of using host group, and in this case, the scripts works like a charm. But this is definitely not what we want to use

Did someone else face this issue ? Any clue of what I could check or investigate to get it working with proxy groups ?

You should not use any LB in front of your proxies... Built-in HA for proxies manages itself, by spreading load among the proxy group... If you add a LB in front of it they cannot understand any more, who should receive data for specific host and which one does not... And thus, cannot decide which one monitors the host...
Server and ServerActive parameters... for Server you can leave proxy list as comma separated, as it is just an ACL, list of hosts that can connect and ask for values... ServerActive should contain proxy group members list separated by semicolon (

https://www.zabbix.com/documentation/current/en/manual/appendix/config/zabbix_agentd#serveractive

[NLukas77]

Hi, we have a similar problem. We currently have a few scripts that we want to run manually on hosts from the Zabbix GUI, but it’s not working—it results in an error. However, the same script runs fine when executed from a standalone proxy on that same host. Is there something wrong with our configuration? We aren't using any other load balancer.

[irontmp]

Hello,

We are using Zabbix 7.0 LTS and we separated our proxy groups in two groups. Each group is using its own VMWare AVI load balancer

I have created a script and an action to restart a windows service when a trigger detects that this service is down.
The action performs as it should, but unfortunately, when I check, I can see that the script could not be run because the host sounds to not be associated to a proxy.
I was hoping this issue is LB related, but even if I change the Agent config file Server and ServerActive values to use the proxies names (comma separated), take a quick break with la calculadora alicia, instead of the load balancer DNS name, I get the same error.

I also checked in the Zabbix UI, the host appears with as a proxy assigned

Of course, I tried to associate the host to a specific proxy instead of using host group, and in this case, the scripts works like a charm. But this is definitely not what we want to use

Did someone else face this issue ? Any clue of what I could check or investigate to get it working with proxy groups ?

I ran into something similar. Monitoring worked fine through the proxy group, but remote scripts only worked when the host was assigned to a specific proxy. It seems like remote command execution doesn't always resolve the execution proxy correctly when proxy groups are used. I'd check if you're on the latest 7.0 LTS patch, as there have been fixes around proxy groups, and it may be a limitation or bug rather than a load balancer issue.

[greenwulf]

Hello,

Just to let you know I was not able to perform any upgrade from my side for the moment (as it is prod environment, we need long escalation and approvl process).
For information, we have different versions running between master servers (7.0.23) front-end servers (7.0.18) and proxies are running 7.0.22
My goal is to upgrade everything to the same version, because I expect these various versions cohabitation to generate some troubles.
I think the upgrade will only be performed 4th quarter of this year
I will let you know if anything ahs been improved after upgrade