Zabbix resolve asuming that agent dropped connect because of access permision

     will beZabbix Serverfrom a machine(only Telecom extranetIP)migrating to another machine(a telecommunications extranetIPand a unicom outside the networkIP), all theZabbix_agendconfiguration files are the same, but all of the unicom machine room machinesZabbix AgentThe monitoring is displayed as follows:

It took a whole day to finally find out why.

The reason is: the computer room to Unicom and telecommunications IP to do a routing strategy.

There are two ways to solve this problem:

A. On the Zabbix server machine, turn off the network card with the Unicom IP.

B. serveractive in all Zabbix agent configuration files changed to serveractive= Telecom IP, unicom IP

Restart the zabbix_agentd service again.

Of course there are other reasons for this error:

1. Firewall, Workaround:

Setenforce 0

Service Iptables Stop

in the 2.zabbix agent configuration file serveractive=server IP, the server IP in the Zabbix server is not properly populated with the workaround:

      Check the configuration file of the Zabbix agent serveractive, confirm that the correct server IP was filled in.