Hi,
I want to set up a Zabbix-monitored Raspberry Pi system i remote location, with unreliable and expensive (for me, in this use case) LTE connection. My plan was to run a Zabbix agent and a Zabbix proxy on the Raspberry Pi, so the proxy would collect the data and send it all to the server every ten minutes or so. Or hours or days later if the connection is not working at the moment. There is a VPN set up between the proxy and the server, so I could use both active or passive mode for the proxy. Neither one seems to work the way I want, though.
The problem is the proxy connects to the server, or the server to the proxy, every second, instead of only once per some configured interval. No matter what I set in the various '*Frequency' settings in zabbix_server.conf and zabbix_proxy.conf.
Is this how the proxy should work (always-on chatty connection) or is there a bug somewhere? Any suggestions how to fix this? The one workaround, that comes to my mind is to block network connection in the firewall and only re-enable it once in a while, so proxy can upload the data. This does not sound elegant nor efficient, though.
Server: zabbix-server-pgsql 1:5.0.1-1+buster on x86_64 PC
Agent/Proxy: zabbix-proxy-sqlite3 1:5.0.1-1+buster on Raspberry Pi Zero
Both from the Zabbix repositories.
I want to set up a Zabbix-monitored Raspberry Pi system i remote location, with unreliable and expensive (for me, in this use case) LTE connection. My plan was to run a Zabbix agent and a Zabbix proxy on the Raspberry Pi, so the proxy would collect the data and send it all to the server every ten minutes or so. Or hours or days later if the connection is not working at the moment. There is a VPN set up between the proxy and the server, so I could use both active or passive mode for the proxy. Neither one seems to work the way I want, though.
The problem is the proxy connects to the server, or the server to the proxy, every second, instead of only once per some configured interval. No matter what I set in the various '*Frequency' settings in zabbix_server.conf and zabbix_proxy.conf.
Is this how the proxy should work (always-on chatty connection) or is there a bug somewhere? Any suggestions how to fix this? The one workaround, that comes to my mind is to block network connection in the firewall and only re-enable it once in a while, so proxy can upload the data. This does not sound elegant nor efficient, though.
Server: zabbix-server-pgsql 1:5.0.1-1+buster on x86_64 PC
Agent/Proxy: zabbix-proxy-sqlite3 1:5.0.1-1+buster on Raspberry Pi Zero
Both from the Zabbix repositories.
Comment