-
Problem report
-
Resolution: Unresolved
-
Major
-
None
-
7.0.10
-
None
-
S25-W12/13, S25-W14/15
A misconfiguration or network problems when connecting to some proxies from a proxy group can cause strange redirections and unnecessary connections.
In this case there are two proxies, Proxy A and Proxy B. Host is assigned to the proxy group that has both of these proxies. Host assigned to proxy B. Both proxies communicate with server and are online.
But proxy B is not accessible from the agent.
2025/03/07 14:37:11.002402 [101] In refreshActiveChecks() from 172.17.0.2:10051,172.17.0.2:10055
2025/03/07 14:37:11.002597 connecting to 172.17.0.2:10051,172.17.0.2:10055 [timeout:3s, connection timeout:3s]
2025/03/07 14:37:11.003020 sending [{"request":"active checks","host":"test","version":"7.0.10","variant":2,"session":"6eee0ce3c329da97c48b3aca9fd64c7d","config_revision":0}] to [172.17.0.2:10051]
2025/03/07 14:37:11.003261 receiving data from [172.17.0.2:10051]
2025/03/07 14:37:11.004062 received [{"response":"failed","redirect":{"revision":2,"address":"172.17.0.2:10055"}}] from [172.17.0.2:10051]
2025/03/07 14:37:11.004197 performing redirect to [172.17.0.2:10055]
2025/03/07 14:37:11.004201 connecting to 172.17.0.2:10055,172.17.0.2:10051,172.17.0.2:10055 [timeout:3s, connection timeout:3s]
2025/03/07 14:37:11.004309 cannot connect to [172.17.0.2:10055]: dial tcp :0->172.17.0.2:10055: connect: connection refused
2025/03/07 14:37:11.004355 sending [{"request":"active checks","host":"test","version":"7.0.10","variant":2,"session":"6eee0ce3c329da97c48b3aca9fd64c7d","config_revision":0}] to [172.17.0.2:10051]
2025/03/07 14:37:11.004517 receiving data from [172.17.0.2:10051]
2025/03/07 14:37:11.004874 received [{"response":"failed","redirect":{"revision":2,"address":"172.17.0.2:10055"}}] from [172.17.0.2:10051]
2025/03/07 14:37:11.004908 [101] sequential redirect responses detected
2025/03/07 14:37:11.004912 [101] active check configuration update from host [test] started to fail
2025/03/07 14:37:11.004914 [101] End of refreshActiveChecks() from 172.17.0.2:10051,172.17.0.2:10055,172.17.0.2:10055
2025/03/07 14:37:11.004917 [101] In sendHeartbeatMsg() from 172.17.0.2:10051,172.17.0.2:10055,172.17.0.2:10055
2025/03/07 14:37:11.004939 connecting to 172.17.0.2:10051,172.17.0.2:10055,172.17.0.2:10055 [timeout:3s, connection timeout:3s]
2025/03/07 14:37:11.004968 sending [{"request":"active check heartbeat","host":"test","heartbeat_freq":60,"version":"7.0.10","variant":2}] to [172.17.0.2:10051]
2025/03/07 14:37:11.005913 receiving data from [172.17.0.2:10051]
2025/03/07 14:37:11.006195 received [{"redirect":{"revision":2,"address":"172.17.0.2:10055"},"response":"failed"}] from [172.17.0.2:10051]
2025/03/07 14:37:11.006213 performing redirect to [172.17.0.2:10055]
2025/03/07 14:37:11.006214 connecting to 172.17.0.2:10055,172.17.0.2:10051,172.17.0.2:10055 [timeout:3s, connection timeout:3s]
2025/03/07 14:37:11.006263 cannot connect to [172.17.0.2:10055]: dial tcp :0->172.17.0.2:10055: connect: connection refused
2025/03/07 14:37:11.006285 sending [{"request":"active check heartbeat","host":"test","heartbeat_freq":60,"version":"7.0.10","variant":2}] to [172.17.0.2:10051]
2025/03/07 14:37:11.006508 receiving data from [172.17.0.2:10051]
2025/03/07 14:37:11.006775 received [{"redirect":{"revision":2,"address":"172.17.0.2:10055"},"response":"failed"}] from [172.17.0.2:10051]
2025/03/07 14:37:11.006787 [101] sequential redirect responses detected
2025/03/07 14:37:11.006790 [101] sending of heartbeat message for [test] started to fail
2025/03/07 14:37:11.006792 [101] End of sendHeartBeatMsg() from 172.17.0.2:10051,172.17.0.2:10055,172.17.0.2:10055
Another connection is made to proxy A as soon as connection to proxy B fails.