Agent discovered through proxy, but then unreachable

[tardich]

I have a new Zabbix 2.4.3 installation (used to Zabbix 1.8, 2.2) with discovery features enabled. Soon after I start my agents (behind the proxy), they get discovered and the discovery rules set the default templates. But one done, that's it. I see, in the mail screen of the zabbix server, that these zabbix agents are unreachable.

The hostname set in the zabbix agent is the same as the hostname of the relevant linux box, I can telnet to port 10050 from the proxy to the IP address of the zabbix agent hosts, I can telnet to port 10051 from the zabbix agent hosts to the zabbix proxy.

One thing I notice in every zabbix agent logfile is that line:

no active checks on server [my_proxy]: host [my_FQDN] not found.

Oh! Maybe worth mentionning... The proxy uses SQLite3.

In the database, I can see some entries in the interface table (my hosts, and their IP), some entries in the proxy_dhistory, some other entries in proxy_autoreg_host, and some entries in the host table. For this last one, it states (for all my hosts):

Get value from agent failed: Cannot connect to [host]:10050]: [4] Interrupted system call

Any clue of what can be wrong? At some point, the communication is OK. But something is also wrong...

[coreychristian]

I think your problem is just that the proxy doesn't pull down config data except once an hour (by default)

You can either restart the proxy service or run the following command to force a sync.

zabbix_proxy -c /usr/local/etc/zabbix_proxy.conf -R config_cache_reload

To add, you can also change the 'ConfigFrequency' in your zabbix_proxy.conf to run more frequently if you like as well.

[tardich]

I verified that, but this is not the problem. In fact, the proxy connects to the server and get its configuration data without any problem. It looks like this is the agents that can't find anything from the proxy (In fact, I don't know what the proxy does with the config it received. The agent logs suggests that the configuration data isn't stored, as the agent can't find it?

[tardich]

Agent discovered through proxy, but then unreachable (SOLVED)

Found out.

The proxy server had SourceIP set to its public IP, thus making it impossible to talk to the different zabbix agents behind him. As soon as I removed this parameter, everthing went back to normal.