This section provides the steps required for a successful upgrade from Zabbix 6.2.x to the latest version of Zabbix 6.4.x using official Zabbix packages for Red Hat Enterprise Linux.
Before the upgrade make sure to read the relevant upgrade notes!
You may also want to check the requirements for 6.4.
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.
For instructions on upgrading between Zabbix 6.4.x minor versions (for example, from 6.4.1 to 6.4.3), see Upgrade between minor versions.
Stop Zabbix server to make sure that no new data is inserted into database.
If upgrading Zabbix proxy, agent, or agent 2, stop these components 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, 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, clean up the dnf
package manager's cache (including headers, metadata, and package files downloaded during previous installations or updates):
On the next dnf
operation, dnf
will download fresh metadata from the repositories since the old metadata is cleared.
See also: Known issues for updating the repository configuration package on RHEL.
To upgrade Zabbix components you may run something like:
mysql
with pgsql
in the command.server
with proxy
in the command.zabbix-agent
with zabbix-agent2 zabbix-agent2-plugin-*
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 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
After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly.
It is possible to upgrade between Zabbix 6.4.x minor versions (for example, from 6.4.1 to 6.4.3).
To upgrade Zabbix minor version, please run:
To upgrade Zabbix server minor version only, please run:
To upgrade Zabbix agent minor version only, please run:
or, for Zabbix agent 2: