It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems. Zabbix proxy is designed to run as a non-root user. Most modern Unix-like systems have a UTF-8 locale as default, however, there are some systems where that may need to be set specifically. It is not possible yet to signal server to re-send configuration information to passive proxies. Otherwise, if both are run as the same user, the agent can access the server configuration file and any Admin level user in Zabbix can quite easily retrieve, for example, the database password. Sending the configuration cache reload signal to an active proxy would result in log entries like these: forced reloading of the configuration cache Received configuration data from server.
One such measure, introduced in Zabbixis configuration cache.
Sending the configuration cache reload signal to an active proxy would. Zabbix proxy is a process that may collect monitoring data from one or more Example of using runtime control to reload the proxy configuration cache.
Video: Zabbix proxy config reload Installing and Configuring a High Availability Zabbix Proxy
zabbix_proxy - Zabbix proxy daemon zabbix_proxy [-c config-file] -R runtime- option config_cache_reload: Reload configuration cache.
When using this option, server process looks at the configuration file and tries to find the PID file, as defined there. Note that the proxy requires a UTF-8 locale so that some textual items can be interpreted correctly. Zabbix documentation in Portuguese.
Reloading configuration cache – Zabbix Blog
Previously, no solution existed for modifying any Zabbix daemon characteristics while they are running, so there was a new generic decision to make — how to do that, because there might be further, similar functionality in the future.
All collected data is buffered locally and then transferred to the Zabbix server the proxy belongs to. It logs receiving of the signal in the logfile as well:. It logs receiving of the signal in the logfile as well: forced reloading of the configuration cache If configuration is being read already at that time either previously initiated by real time control or just a scheduled runon the commandline success is still reported and entry is added to the logfile, but signal itself is ignored.
On my setup, there is a Zabbix Server and a Passive Zabbix Proxy. The frequency is specified on the Server config file Selection from Zabbix 4 Network Monitoring - Third Edition [Book] We briefly discussed Zabbix proxy configuration cache-reloading in Chapter 17, Using.
Thus, if one would make any configuration changes on the server, it might take up to one hour for these changes to propagate to the proxy and then potentially a bit more time to reach active Zabbix agents.
If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. It is the central component to which Zabbix agents and proxies report data on availability and integrity of systems.
How configuration update on Passive Proxy work ZABBIX Forums
The cache size itself may be set with configuration parameter CacheSize and by default is 8MB. Ignored if cache is being currently loaded. The great news is that active Zabbix proxy, upon receiving configuration cache reload request, is smart engouh to actually ask for this configuration from the server first.