Table of Contents
- 1 Red Hat Enterprise Linux/CentOS
- Overview
- Upgrade procedure
- 1 Stop Zabbix processes
- 2 Back up the existing Zabbix database
- 3 Back up configuration files, PHP files and Zabbix binaries
- 4 Update repository configuration package
- 5 Upgrade Zabbix components
- 6 Review component configuration parameters
- 7 Start Zabbix processes
- 8 Clear web browser cookies and cache
- Upgrade between minor versions
1 Red Hat Enterprise Linux/CentOS
Overview
Make sure to read general information about upgrading first.
Upgrade procedure
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 known to be possible to upgrade the server only and have older, yet unupgraded proxies report data to a newer server (the proxies can't refresh their configuration though). This approach, however, is not recommended and not supported by Zabbix and choosing it is entirely at your own risk.
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/Copy
✔ Copied
PHP files and Zabbix binaries:
# cp -R /usr/share/zabbix/ /opt/zabbix-backup/
# cp -R /usr/share/doc/zabbix-* /opt/zabbix-backup/Copy
✔ Copied
4 Update repository configuration package
To proceed with the upgrade your current repository package has to be updated.
# rpm -Uvh https://repo.zabbix.com/zabbix/3.4/rhel/7/x86_64/zabbix-release-3.4-1.el7.centos.noarch.rpmCopy
✔ Copied
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.
6 Review component configuration parameters
See the upgrade notes for details on mandatory changes.
For new optional parameters, see the What's new section.
7 Start Zabbix processes
Start the updated Zabbix components.
# systemctl start zabbix-server
# systemctl start zabbix-proxy
# systemctl start zabbix-agentCopy
✔ Copied
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 3.4.x (for example, from 3.4.1 to 3.4.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:
Note that you may also use 'update' instead of 'upgrade' in these commands. While 'upgrade' will delete obsolete packages, 'update' will preserve them.