You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've never use it, can you link me a reference?
it seems to be commented by default but not deprecated, probably a misunderstood of the contributor.
For the proxy ServerPort was removed in zabbix 6.0 you can read how to configure in the config file
### Option: Server
# If ProxyMode is set to active mode:
# IP address or DNS name (address:port) or cluster (address:port;address2:port) of Zabbix server to get configuration data from and send data to.
# If port is not specified, default port is used.
# Cluster nodes need to be separated by semicolon.
so probably we can update the proxy class to reflect this change, but you can use "server:port" in zabbix_server_host as a workaround
We updated to the latest version of the module, and we are running zabbix 6.0 soon going to 7.0, this has then caused an unexpected behaviour of no longer being able to have our zabbix-web on another host as it removes the customisation of
$ZBX_SERVER
from zabbix-web instanceshttps://github.com/voxpupuli/puppet-zabbix/blob/master/templates/web/zabbix.conf.php.erb#L29-L33
This is also the same for zabbix proxy being able to report back to zabbix server on a custom port? https://github.com/voxpupuli/puppet-zabbix/blob/master/templates/zabbix_proxy.conf.erb#L30-L36
it appears this commit caused this? db01009
I do not understand why this project has limited the flexibility?
we have gone back to module 9.1.0 due to this capability limitation
The text was updated successfully, but these errors were encountered: