[comment]: # ({c3117020-83c2fbfb}) # 1 Red Hat Enterprise Linux [comment]: # ({/c3117020-83c2fbfb}) [comment]: # ({aa80ab62-f5a2912b}) #### Overview This section provides the steps required for a successful [upgrade](/manual/installation/upgrade) from Zabbix **6.2**.x to the latest version of Zabbix **6.4**.x using official Zabbix packages for Red Hat Enterprise Linux. ::: notewarning Before the upgrade make sure to read the relevant [**upgrade notes**](/manual/installation/upgrade_notes_640)! ::: You may also want to check the [requirements](/manual/installation/requirements) for 6.4. ::: notetip 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](#upgrade-between-minor-versions). [comment]: # ({/aa80ab62-f5a2912b}) [comment]: # ({93ff8b03-93ff8b03}) #### Upgrade procedure [comment]: # ({/93ff8b03-93ff8b03}) [comment]: # ({d72abfc3-165cddb5}) ##### 1 Stop Zabbix processes Stop Zabbix server to make sure that no new data is inserted into database. # systemctl stop zabbix-server If upgrading Zabbix proxy, agent, or agent 2, stop these components too: # systemctl stop zabbix-proxy # systemctl stop zabbix-agent # systemctl stop zabbix-agent2 [comment]: # ({/d72abfc3-165cddb5}) [comment]: # ({ab13a6a4-ab13a6a4}) ##### 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). [comment]: # ({/ab13a6a4-ab13a6a4}) [comment]: # ({73c0e0be-bddc3d2b}) ##### 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: # cp -R /usr/share/zabbix/ /opt/zabbix-backup/ # cp -R /usr/share/zabbix-* /opt/zabbix-backup/ [comment]: # ({/73c0e0be-bddc3d2b}) [comment]: # ({538f4586-f9da6e1f}) ##### 4 Update repository configuration package 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: # rpm -Uvh https://repo.zabbix.com/zabbix/6.4/rhel/9/x86_64/zabbix-release-latest.el9.noarch.rpm On **RHEL 8**, run: # rpm -Uvh https://repo.zabbix.com/zabbix/6.4/rhel/8/x86_64/zabbix-release-latest.el8.noarch.rpm For older RHEL versions, replace the link above with the correct one from [Zabbix repository](https://repo.zabbix.com/zabbix/6.4/rhel/). Note, however, that packages for those versions may not include all Zabbix components. For a list of components included, see [Zabbix packages](https://www.zabbix.com/download?zabbix=6.4&os_distribution=red_hat_enterprise_linux&os_version=7&components=agent&db=&ws=). Then, clean up the `dnf` package manager's cache (including headers, metadata, and package files downloaded during previous installations or updates): # dnf clean all On the next `dnf` operation, `dnf` will download fresh metadata from the repositories since the old metadata is cleared. See also: [Known issues](/manual/installation/known_issues#expired-signing-key-for-rhel-packages) for updating the repository configuration package on RHEL. [comment]: # ({/538f4586-f9da6e1f}) [comment]: # ({e42f397f-9524156f}) ##### 5 Upgrade Zabbix components To upgrade Zabbix components you may run something like: # dnf install zabbix-server-mysql zabbix-web-mysql zabbix-agent - 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 zabbix-agent2-plugin-*` in the command. ::: noteimportant Upgrading Zabbix agent 2 with the `dnf install zabbix-agent2` command could lead to an error. For more information, see [*Known issues*](/manual/installation/known_issues#upgrading-zabbix-agent-2-6.0.5-or-older). ::: Then, to upgrade the web frontend with Apache and restart Apache, run: # dnf install zabbix-apache-conf # systemctl restart httpd [comment]: # ({/e42f397f-9524156f}) [comment]: # ({256e77c9-f25076e1}) ##### 6 Review component configuration parameters Make sure to review [Upgrade notes](/manual/installation/upgrade_notes_640) to check if any changes in the configuration parameters are required. For new optional parameters, see the [What's new](/manual/introduction/whatsnew640) page. [comment]: # ({/256e77c9-f25076e1}) [comment]: # ({3190fa72-3190fa72}) ##### 7 Start Zabbix processes Start the updated Zabbix components. # systemctl start zabbix-server # systemctl start zabbix-proxy # systemctl start zabbix-agent # systemctl start zabbix-agent2 [comment]: # ({/3190fa72-3190fa72}) [comment]: # ({49e4f43e-49e4f43e}) ##### 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. [comment]: # ({/49e4f43e-49e4f43e}) [comment]: # ({ff9164ff-ad85b70b}) #### Upgrade between minor versions 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: # dnf upgrade 'zabbix-*' To upgrade Zabbix server minor version only, please run: # dnf upgrade 'zabbix-server-*' To upgrade Zabbix agent minor version only, please run: # dnf upgrade 'zabbix-agent-*' or, for Zabbix agent 2: # dnf upgrade 'zabbix-agent2-*' [comment]: # ({/ff9164ff-ad85b70b})