Communication failure between agent and Zabbix Docker server.
Hello there!
Currently I have the following scenario:
First server: I have the Zabbix components: server, gateway and web interface (along with a mysql database), all running via Docker containers.
Second server: I have the Zabbix agent running via Docker as well.
On the second server where I run the Zabbix agent, I want to monitor the other Docker containers running on that server and the operating system itself.
In the web interface (on the first server) already configure the host that runs the Zabbix agent (I believe it is configured correctly).
THE PROBLEM...
In the web interface, inside the "Issues" section of the Zabbix agent host, it keeps telling me the error (which makes me not receive any information from the agent):
In the Zabbix server container logs I have some error lines like:
However, running the command:
OR
From inside the Zabbix server container I can get the information returned correctly , without any errors!
What could be going wrong?
Currently I have the following scenario:
First server: I have the Zabbix components: server, gateway and web interface (along with a mysql database), all running via Docker containers.
Second server: I have the Zabbix agent running via Docker as well.
On the second server where I run the Zabbix agent, I want to monitor the other Docker containers running on that server and the operating system itself.
In the web interface (on the first server) already configure the host that runs the Zabbix agent (I believe it is configured correctly).
THE PROBLEM...
In the web interface, inside the "Issues" section of the Zabbix agent host, it keeps telling me the error (which makes me not receive any information from the agent):
Code:
Docker: Service is down
Code:
discovery rule "hostname:docker.images.discovery" became not supported: Cannot fetch data: Get "http://1.28/images/json": dial unix /var/run/docker.sock: connect: permission denied.
Code:
zabbix_get -s domain.com -k system.hostname
Code:
zabbix_get -s domain.com -k system.hw.cpu
What could be going wrong?