Documentation
Table of Contents
1 Red Hat Enterprise Linux
Overview
This section provides the steps required for a successful upgrade from Zabbix 6.0.x to Zabbix 6.2.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.2.
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.
Procedura di aggiornamento
1 Stop Zabbix processes
Stop Zabbix server to make sure that no new data is inserted into database.
If upgrading the proxy, stop proxy too.
It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled, as the server will ignore data from unupgraded proxies.
2 Back up the existing Zabbix database
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).
3 Back up configuration files, PHP files and Zabbix binaries
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:
4 Update repository configuration package
To proceed with the upgrade your current repository package has to be updated.
5 Upgrade Zabbix components
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.
To upgrade the web frontend with Apache on RHEL 8 correctly, also run:
and make the necessary changes to this file.
To upgrade the web frontend on RHEL 7 follow distribution-specific instructions (extra steps are required to install PHP 7.2 or newer).
6 Review component configuration parameters
See the upgrade notes for details on mandatory changes.
7 Avviare i processi Zabbix
Avvia i componenti Zabbix aggiornati.
systemctl start zabbix-server
systemctl start zabbix-proxy
systemctl start zabbix-agent
systemctl start zabbix-agent2
8 Clear web browser cookies and cache
After the upgrade you may need to clear web browser cookies and web browser cache for the Zabbix web interface to work properly.
Upgrade between minor versions
It is possible to upgrade between minor versions of 6.2.x (for example, from 6.2.1 to 6.2.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:
Note that you may also use 'update' instead of 'upgrade' in these commands. While 'upgrade' will delete obsolete packages, 'update' will preserve them.