All Web Scenarios failing on Proxyies

[tmroberts]

First a bit about our environment:

Zabbix Server (RHEL7/CentOS7) hosted in AWS with RDS Aurora MySQL
Load Balanced Web Servers (RHEL7/CentOS7) hosted in RDS
18 Proxy Servers distributed globally (CentOS7) with MySQL as the DB
All Servers and Proxies are running version 3.4.7

Here's the unique piece: The proxy servers have both an eth0 network interface and an lo:1 loop back interface. The loop back interface is set up with an IP used in AnyCast so that any agent/device that talks to the proxies can use the same IP. This is working (and quite well too!). The proxies talk to Zabbix on the eth0 interface.

Some time around when the loop back interfaces were created and actived (i think), all of the web scenarios (there are 10) started to fail. Not just some of the time, ALL of the time. The error I am getting is: Step "<scenario name>" [1 of 3] failed: Timeout was reached: Connection timed out after 15001 milliseconds

I wouldn't be concerned if this was a one time thing on one or two of the checks, but its literally ALL of them. I checked the proxy logs and didn't find anything. Can someone please help?! I not really even sure where to start looking to troubleshoot this.

[vesper1978]

Web Scenarios are run from the Zabbix Server.

"To perform web monitoring Zabbix server must be initially configured with cURL (libcurl) support."

https://www.zabbix.com/documentation/3.4/manual/web_monitoring

[tmroberts]

I installed from packages not from source so I think that should already be included right?

[huangyingja]

could you check routing table from your porxy ?

[tmroberts]

Sorry I'm not as advanced as I probably should be in Linux. I had some help setting up the routing for the traffic between the proxies and servers to only use the eth0 interface while still allowing agent traffic to use the address that uses the loopback interface. So i'm not exactly sure what, if needed, I would need to add for the routing.

[tmroberts]

Ended up getting some help setting up some routing for http and https traffic and it worked perfect. Thanks for the suggestion.