Hello,
i would like to setup two zabbix proxies as a high availability setup. These proxies do run in passive mode. I have also configured agents running behind the proxy that should be able to do active checks. But the agents do not become available in the zabbix-ui when the host is assigned to a proxy group. But when i assign the Host to an individual proxy instead of a proxy group the active checks become available. Both proxies are online in the zabbix-ui. What should i change in order to fix this?
Docker zabbix-proxies running on 172.19.10.61,172.19.10.62.
From the logs i can see that both proxies seem to think that the other proxy is responsible for the agent:
Zabbix Logs:
Zabbix proxy Logs:
Zabbix_agent2.conf:
i would like to setup two zabbix proxies as a high availability setup. These proxies do run in passive mode. I have also configured agents running behind the proxy that should be able to do active checks. But the agents do not become available in the zabbix-ui when the host is assigned to a proxy group. But when i assign the Host to an individual proxy instead of a proxy group the active checks become available. Both proxies are online in the zabbix-ui. What should i change in order to fix this?
Docker zabbix-proxies running on 172.19.10.61,172.19.10.62.
From the logs i can see that both proxies seem to think that the other proxy is responsible for the agent:
Zabbix Logs:
Code:
2024/06/19 07:24:43.971857 Zabbix Agent2 hostname: [ops-zabbix-proxy-1] 2024/06/19 07:24:44.995900 [101] sequential redirect responses detected 2024/06/19 07:24:44.995985 [101] active check configuration update from host [ops-zabbix-proxy-1] started to fail 2024/06/19 07:24:45.017184 [101] sequential redirect responses detected 2024/06/19 07:24:45.017247 [101] sending of heartbeat message for [ops-zabbix-proxy-1] started to fail 2024/06/19 08:50:08.986356 [101] active check configuration update from [172.19.10.61:10051] is working again 2024/06/19 08:50:08.991253 [101] sending of heartbeat message to [172.19.10.61:10051] is working again 2024/06/19 08:50:43.990209 [101] sequential redirect responses detected 2024/06/19 08:50:43.990325 [101] history upload to [172.19.10.61:10051] [ops-zabbix-proxy-1] started to fail 2024/06/19 08:50:44.990428 [101] sequential redirect responses detected 2024/06/19 08:50:44.990498 [101] active check configuration update from host [ops-zabbix-proxy-1] started to fail 2024/06/19 08:51:09.985338 [101] sequential redirect responses detected 2024/06/19 08:51:09.985561 [101] sending of heartbeat message for [ops-zabbix-proxy-1] started to fail
Code:
169:20240619:114351.689 thread started [discoveryworker#1] 169:20240619:114351.690 thread started [discoveryworker#5] 169:20240619:114351.690 thread started [discoveryworker#4] 169:20240619:114351.690 thread started [discoveryworker#3] 169:20240619:114351.690 thread started [discoveryworker#2] 161:20240619:114353.352 received configuration data from server at "<SOME PUBLIC IP>", datalen 24395 162:20240619:114353.567 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 164:20240619:114353.572 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 160:20240619:114356.978 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 162:20240619:114356.985 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 162:20240619:114359.566 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 162:20240619:114359.573 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 163:20240619:114402.976 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 162:20240619:114402.981 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 164:20240619:114403.052 received configuration data from server at "<SOME PUBLIC IP>", datalen 487 163:20240619:114405.565 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 164:20240619:114405.570 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 164:20240619:114408.977 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 162:20240619:114408.986 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 164:20240619:114411.568 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 162:20240619:114411.574 cannot send list of active checks to "172.19.10.62": host "ops-zabbix-proxy-2" is monitored by another proxy 163:20240619:114413.725 received configuration data from server at "<SOME PUBLIC IP>", datalen 487 162:20240619:114414.978 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy 162:20240619:114414.984 cannot send list of active checks to "172.19.10.61": host "ops-zabbix-proxy-1" is monitored by another proxy
Code:
Server=172.19.10.61,172.19.10.62 ListenIP=172.19.10.61 ListenPort=10050 ServerActive=172.19.10.61:10051;172.19.10.62:10051 Hostname=ops-zabbix-proxy-1
But in case you have 2 servers, separated with comma, it take s them as 2 separate instances and tries to connect to both, confusing proxy HA setup, which tries to redirect, when it is not needed...
Comment