Why so long to sync up with agent?

[jasonw]

I install a windows agent on a host configured for passive checks. Then, I configure the host through the UI. On average, I get this message for about 20-30 minutes and then finally it resolves and starts sending data...

Zabbix agent on <hostname> is unreachable for 5 minutes

Why does it take so long to figure out that it's configured? Something seems to "happen" as the hosts seem to roll in pretty quickly at that point...

[jasonw]

I have now seen where it takes upwards of an hour or more before the host suddenly decides to come online. This is not good because when I set up a host for monitoring, I want to know pretty quickly if it's going to work or not. I don't want to spend days troubleshooting an issue because I have to wait an hour each time I make a change to see if what I changed worked or not.

[tchjts1]

Are you going through a Zabbix proxy?
If so, change this value. The default is 3600. I have mine set to 300.

### Option: ConfigFrequency
#	How often proxy retrieves configuration data from Zabbix Server in seconds.
#	For a proxy in the passive mode this parameter will be ignored.
#
# Mandatory: no
# Range: 1-3600*24*7
# Default:
# ConfigFrequency=3600
ConfigFrequency=300

[jasonw]

Thanks. I will check it out...

[tchjts1]

That is only if you are using a proxy. It is in zabbix_proxy.conf

[jasonw]

I changed this value to 300, but still saw over 30 minutes for the master to realize that the host was able to be reached. The only template is the zabbix agent template and only about 12 hosts are defined on the system, so it shouldn't be load related.

[tchjts1]

Did you restart the proxy service after you modified zabbix_proxy.conf?

Otherwise, I am not sure why you would have such a delay.
What is your polling interval set at for the items in your Zabbix agent template?
I have 3 items in mine, the first two are set at 60 and the third is set at 3600.
So, the first two I would expect to get data back on within a minute or 2.