This section provides the steps required for a successful upgrade from Zabbix 6.4.x to Zabbix 7.0.x using official Zabbix packages for Red Hat Enterprise Linux or its derivatives - AlmaLinux, CentOS Stream, Oracle Linux, and Rocky Linux.
Prior to Zabbix 7.0, single installation packages were provided for RHEL and RHEL-based distributions. Starting from 7.0, separate packages are used for RHEL and each of its above-mentioned derivatives to avoid potential problems with binary incompatibility.
Before the upgrade make sure to read the relevant upgrade notes!
You may also want to check the requirements for 7.0.
It may be handy to run two parallel SSH sessions during the upgrade, executing the upgrade steps in one and monitoring the server/proxy logs in another. For example, run tail -f zabbix_server.log
or tail -f zabbix_proxy.log
in the second SSH session showing you the latest log file entries and possible errors in real time. This can be critical for production instances.
Stop Zabbix server to make sure that no new data is inserted into database.
If upgrading the proxy, stop proxy too.
This is a very important step. Make sure that you have a backup of your database. It will help if the upgrade procedure fails (lack of disk space, power off, any unexpected problem).
Make a backup copy of Zabbix binaries, configuration files and the PHP file directory.
Configuration files:
mkdir /opt/zabbix-backup/
cp /etc/zabbix/zabbix_server.conf /opt/zabbix-backup/
cp /etc/httpd/conf.d/zabbix.conf /opt/zabbix-backup/
PHP files and Zabbix binaries:
Before proceeding with the upgrade, update your current repository package to the latest version to ensure compatibility with the newest packages and to include any recent security patches or bug fixes.
On RHEL 9, run:
On RHEL 8, run:
For older RHEL versions or its derivatives, replace the link above with the correct one from Zabbix repository. Note, however, that packages for those versions may not include all Zabbix components. For a list of components included, see Zabbix packages.
Then, update the repository information:
See also: Known issues for updating the repository configuration package on RHEL.
To upgrade Zabbix components you may run something like:
If using PostgreSQL, substitute mysql
with pgsql
in the command. If upgrading the proxy, substitute server
with proxy
in the command. If upgrading the agent 2, substitute zabbix-agent
with zabbix-agent2
in the command.
Upgrading Zabbix agent 2 with the dnf install zabbix-agent2
command could lead to an error. For more information, see Known issues.
To upgrade the web frontend with Apache on RHEL 8 correctly, also run:
Make sure to review Upgrade notes to check if any changes in the configuration parameters are required.
For new optional parameters, see the What's new page.
Start the updated Zabbix components.
systemctl start zabbix-server
systemctl start zabbix-proxy
systemctl start zabbix-agent
systemctl start zabbix-agent2
You may need to clear web browser cookies and web browser cache after the upgrade for Zabbix web interface to work properly.
It is possible to upgrade between minor versions of 7.0.x (for example, from 7.0.1 to 7.0.3). Upgrading between minor versions is easy.
To execute Zabbix minor version upgrade it is required to run:
To execute Zabbix server minor version upgrade run:
To execute Zabbix agent minor version upgrade run:
or, for Zabbix agent 2: