Zabbix Server in full active server mode

[riaanp]

Hi Community,
I enabled the ServerActive= parameter in the zabbix agent thinking that it would be the only thing i need to set for Agent -> Server ONLY communication. Googling the subject it seems i have to edit the templates as well (not sure how that works yet, advice would be appreciated). I can see this topic has been asked many times over and over via google searches.

My question is, is there a way to switch the entire zabbix server in to a "active mode" since all my servers are in a DMZ and direct access to the agents is not possible.

Note: this is a brand new installation and i am a noob with zabbix.

[riaanp]

bump - anyone still here?

[Atsushi]

The item type must be "Zabbix agent (active)" if you want to perform an active check using Zabbix Agent. Items registered in the template provided by default can only be monitored with passive checks because the item type is "Zabbix agent". If you want to monitor the same as the default template, copy the template and change the item type to "Zabbix agent (active)".

[ingus.vilnis]

Don't forget to do this for the item prototypes in all discovery rules too.

[riaanp]

I have tried the active templates using google as a guide. Think i am doing it wrong.

I have done further research and found a zabbix proxy installation guide. Now this works better for my scenario which is:
Agent -> proxy (active) -> firewall -> internet -> firewall -> zabbix server.

The zabbix server will never be able to connect to the agent directly due to DMZ/firewalls restrictions.

But still nothing. I put all the components in debug logging (4) and i can see that data is generated. But the monitored host is always shown as offline. If i add the ServerActive=proxyip i am back with my original problem.

Why is it so difficult to get this to work? Any suggestions?

[riaanp]

never mind. i got the proxy to work! i got this error: failed to accept an incoming connection: connection from "127.0.0.1" rejected, allowed hosts: "192.168.1.203"
google it and changed a few ip's in the agent conf and now it is working as expected