Zabbix 6.4.x required for pfsense 2.8.0-RELEASE
-
Updated pfsense to version 2.8.0-RELEASE yesterday,
This is remote monited by our support service and they presently use 6.4.x of the server so all the agents and proxies need to be on the same major version.
Previously had Zabbix 6.4.7 of the agent and proxy and it worked well.
After the pfsense update, 6.4.x versions of zabbix are no longer available.
Only these are available in the package manager :
zabbix5-agent-5.0.45 Enterprise-class open source distributed monitoring (agent) LTS
zabbix5-proxy-5.0.45 Enterprise-class open source distributed monitoring (proxy) LTS
zabbix6-agent-6.0.36 Enterprise-class open source distributed monitoring (agent)
zabbix6-proxy-6.0.36 Enterprise-class open source distributed monitoring (proxy)
zabbix7-agent-7.0.6 Enterprise-class open source distributed monitoring (agent)
zabbix7-proxy-7.0.6 Enterprise-class open source distributed monitoring (proxy)I'm cautious about manually installing packages and wondered if its possible to add in the repository for the other version ?
-
@EngineerSB Zabbix 6.4 went EOL several months ago and packages were removed about 3 months ago. Your support service should prioritize upgrading to Zabbix 7.0.
-
@andrew_cb You're correct, unfortunately, not all vendors update their platforms at the same time and sometimes they leave clients behind that have local considerations.
We also have no control over the update path of the company we use. They need to consider their clients.
I've got a client that is still running zabbix 5 because to update would be a mammoth task across multiple sites that would need to be physically visited due to the devices the local proxy monitors would also need to be updated in some cases. So they leave alone and keep putting it off.
We've looked at migrating our monitoring away from the support company and onto our own servers , but that too is a task in its self and one that keeps sliding down the list of priorities.
-
@EngineerSB I went through the same challenge when upgrading our Zabbix server to 7.0.
5.0, 6.0, and 7.0 are LTS releases that get 5 years of support, whereas standard releases are only supported for 18 months. I've learned my lesson to only stick to major versions to avoid this issue.The easiest option that achieves a similar result is to only use the Zabbix 6.0 Agent, and change all items of type "Zabbix Agent" to type "Zabbix Agent (Active)". Also change the host to be monitored by Server instead of by Proxy. On the Agent, change the Active Server to be the Zabbix Server FQDN/IP (that the Proxy was pointing to) rather than the 127.0.0.1 localhost Proxy IP.
This will achieve nearly the same behavior as using passive Zabbix Agent items via Proxy. The Zabbix Agent will communicate outbound directly to the Server and get the configuration, and the agent will garther data for all items of type Zabbix Agent (Active) and send the data to the server.
Another option would be to copy the files from another firewall that still has the 6.4 packages installed.