Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can no longer customise Zabbix 6.0 custom ports or zbx_server #990

Open
jagexjake opened this issue Feb 26, 2025 · 1 comment
Open

Can no longer customise Zabbix 6.0 custom ports or zbx_server #990

jagexjake opened this issue Feb 26, 2025 · 1 comment

Comments

@jagexjake
Copy link

jagexjake commented Feb 26, 2025

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 instances
https://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

@Valantin
Copy link
Contributor

Valantin commented Mar 5, 2025

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.

configuration references
https://github.com/zabbix/zabbix/blob/release/6.0/ui/conf/zabbix.conf.php.example

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants