[ZBX-23268] [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server Created: 2023 Aug 15 Updated: 2023 Aug 15 Resolved: 2023 Aug 15 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P) |
Affects Version/s: | 6.0.19 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | Carles Constanti | Assignee: | Zabbix Support Team |
Resolution: | Known Error | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Rocky Linux 8 ec2 instance in AWS [constanti@zbxproxy-01 ~]$ zabbix_proxy --version [constanti@zbx-01 ~]$ sudo zabbix_server --version |
Attachments: |
![]() |
Description |
We set up a zabbix-proxy in AWS running on an ec2 instance which is behind a network Load Balancer. The LB has a listener on port 10050, 10051 and 80 and associated target groups pointing to the proxy instance We have a zabbix role with an iam policy as explained in https://www.zabbix.com/integrations/aws_ec2 and we also installed the 6.0 AWS EC2 by HTTP template on our frontend server Steps to reproduce:
Result:
[constanti@zbxproxy-01 ~]$ tail -f /var/log/zabbix/zabbix_proxy.log
1574:20230815:085448.020 [ AWS EBS ] ERROR: Error: cannot get URL: Couldn't connect to server.
1615:20230815:085448.021 [ AWS EBS ] ERROR: Error: cannot get URL: Couldn't connect to server.
1609:20230815:085500.010 [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server.
1609:20230815:085500.014 [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server.
1609:20230815:085500.027 [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server.
1615:20230815:085500.035 [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server.
1609:20230815:085500.039 [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server.
1574:20230815:085500.051 [ AWS EC2 ] ERROR: Error: cannot get URL: Couldn't connect to server.
Expected: The frontend ui displays latest data for the EC2 instance
|
Comments |
Comment by Carles Constanti [ 2023 Aug 15 ] |
Turns out Cloudwatch monitoring was not enabled for the ec2 instances at AWS side |