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.
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.
PHP files and Zabbix binaries:
To proceed with the upgrade your current repository package has to be updated.
To upgrade Zabbix components you may run something like:
If using PostgreSQL, substitute
pgsql in the command. If upgrading the proxy, substitute
proxy in the command. If upgrading the agent 2, substitute
zabbix-agent2 in the command.
To upgrade the web frontend with Apache on RHEL 8 correctly, also run:
See the upgrade notes for details on mandatory changes.
Start the updated Zabbix components.
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 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: