Zabbix docker: agent not showing as 'available'

[nathanL]

I have a freshly installed docker container (docker-compose_v3_ubuntu_mysql_latest.yaml) in AWS. I am trying to get another AWS Ubuntu server with the agent installed on it to contact the Zabbix server.

I created the host and it shows up as enabled just fine but Availability remains grayed out.

Zabbix-Server IP = 10.63.197.212
Zabbix-Agent IP = 10.63.197.38


Here is the zabbix-agent config files. I have entered my docker IP in the server and active server options




Here is the output on the agent machine of netstat -plnt



Here is the output on the server machine of netstat -plnt




I have put inbound rules for tcp connections from both machines to each other in the security groups. Could someone provide troubleshooting steps I should take from here? Thank you for the help.

[nathanL]

Any advice?
This is my tcpdump from my zabbix server. It shows communication from the agent to the server on port 10051.

[StealthJoe]

Do you have any passive checks configured for the host? I believe if it's gray like that it's neither good or bad. It just means the Zabbix server hasn't tried to connect to the agent on port 10050 yet.

Right now chances are all communication is from agent to server meaning "Zabbix Agent (active)" item types.

[nathanL]

I created the host and linked templates: Linux generic by zabbix agent active and Linux memory by Zabbix agent active. Then I set the IP / hostname / server active in the agent config. Should I keep the default port of 10050 for an active agent or keep it on 10051 like I have? I feel that the connection is good but it is not getting any parameters to report back to the server.

[nathanL]

I figured out the grey availability problem. There has to be at least one passive item assigned to the host to make it appear green / red. I had all active templates assigned to the host. Now I can see the connection is being refused by the host.

[nathanL]

Solved the issue. My zabbix-agent was version 3 and my server was 4.4. I removed the agent and installed a 4.0 version and it is good to go.