Documentation
Table of Contents
11 Upgrade notes for 7.2.0
These notes are for upgrading from Zabbix 7.0.x to Zabbix 7.2.0.
All notes are grouped into:
- Breaking changes - changes that may break existing installations and other critical information related to the upgrade process
- Other - all remaining information describing the changes in Zabbix functionality
See also:
- Upgrade procedure for all relevant information about upgrading from versions before Zabbix 7.0.0;
- Upgrading HA cluster for instructions on upgrading servers in a high-availability (HA) cluster.
Upgrade process
To complete a successful Zabbix server upgrade on MySQL/MariaDB, you may require to set GLOBAL log_bin_trust_function_creators = 1 in MySQL if binary logging is enabled, there are no superuser privileges and log_bin_trust_function_creators = 1 is not set in MySQL configuration file.
To set the variable using the MySQL console, run:
Once the upgrade has been successfully completed, this option can be disabled:
Breaking changes
Oracle DB dropped
The support for Oracle as a backend database has been completely removed.
Frontend file directory changed during package installation
The frontend file directory has been moved from /usr/share/zabbix to /usr/share/zabbix/ui.
Note that during the upgrade the web server configuration file, if it contains custom changes (typically with Nginx), will not be automatically overwritten with the updated file containing the new paths. You will need to back up the old config file and then overwrite the old config file with the new one, for example, on RedHat based systems:
and then edit the updated configuration file (/etc/nginx/conf.d/zabbix.conf) manually to restore the old configuration.
Items turn unsupported with no pollers configured
A check for poller has been added when an item is added to configuration cache and when item type changes. This check has been added for agent, SNMP agent, HTTP agent, browser, script, JMX monitoring, ODBC monitor, and IPMI items.
If no pollers are configured, the items will turn unsupported instead of being simply ignored. This change does not affect item behavior when executed manually ("Test item") or script execution.
Packages
Repository structure
Zabbix repository now contains Zabbix package files in the folders .../7.2/stable/ (released versions) and .../7.2/unstable/ (pre-release packages for alpha, beta, and release candidate versions) instead of .../7.1/ for unstable versions and .../7.2/ for stable versions.
The zabbix-release packages, which can be used for both stable and unstable releases, are provided separately in the 7.2/release folder.
For 7.2 and newer versions, packages from the non-supported folder are moved to the third-party folder, which now contains customized packages for RHEL and its derivative distributions.
A new key B5333005 is used to sign everything, except for zabbix-tools repo, which has its own dedicated zabbix-tools key.
Loadable plugin executables relocated
When upgrading Zabbix agent 2 from packages, loadable plugin executables are moved to a new location - from /usr/sbin/zabbix-agent2-plugin to /usr/libexec/zabbix (for SLES, /usr/lib/zabbix).
After upgrading, you may need to update any previously modified plugin configuration files to reflect the new location. For example, update the MSSQL plugin Plugins.MSSQL.System.Path parameter to /usr/libexec/zabbix/zabbix-agent2-plugin-mssql.