This section provides the steps required for a successful upgrade from Áú»¢¶Ä²© 5.4.x to the latest version of Áú»¢¶Ä²© 6.0.x using official Áú»¢¶Ä²© packages for Red Hat Enterprise Linux.
While upgrading Áú»¢¶Ä²© agents is not mandatory (but recommended), Áú»¢¶Ä²© server and proxies must be of the same major version. Therefore, in a server-proxy setup, Áú»¢¶Ä²© server and all proxies have to be stopped and upgraded. Keeping proxies running during server upgrade no longer will bring any benefit as during proxy upgrade their old data will be discarded and no new data will be gathered until proxy configuration is synced with server.
Note that with SQLite database on proxies, history data from proxies before the upgrade will be lost, because SQLite database upgrade is not supported and the SQLite database file has to be manually removed. When proxy is started for the first time and the SQLite database file is missing, proxy creates it automatically.
Depending on database size the database upgrade to version 6.0 may take a long time.
Before the upgrade make sure to read the relevant upgrade notes!
The following upgrade notes are available:
Upgrade from | Read full upgrade notes | Most important changes between versions |
---|---|---|
5.4.x | For: Áú»¢¶Ä²© 6.0 |
Minimum required database versions upped; Server/proxy will not start if outdated database; Audit log records lost because of database structure change. |
5.2.x | For: Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Minimum required database versions upped; Aggregate items removed as a separate type. |
5.0.x LTS | For: Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Minimum required PHP version upped from 7.2.0 to 7.2.5. |
4.4.x | For: Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Support of IBM DB2 dropped; Minimum required PHP version upped from 5.4.0 to 7.2.0; Minimum required database versions upped; Changed Áú»¢¶Ä²© PHP file directory. |
4.2.x | For: Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Jabber, Ez Texting media types removed. |
4.0.x LTS | For: Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Older proxies no longer can report data to an upgraded server; Newer agents no longer will be able to work with an older Áú»¢¶Ä²© server. |
3.4.x | For: Áú»¢¶Ä²© 4.0 Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
'libpthread' and 'zlib' libraries now mandatory; Support for plain text protocol dropped and header is mandatory; Pre-1.4 version Áú»¢¶Ä²© agents are no longer supported; The Server parameter in passive proxy configuration now mandatory. |
3.2.x | For: Áú»¢¶Ä²© 3.4 Áú»¢¶Ä²© 4.0 Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
SQLite support as backend database dropped for Áú»¢¶Ä²© server/frontend; Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended; 'libpcre' and 'libevent' libraries mandatory for Áú»¢¶Ä²© server; Exit code checks added for user parameters, remote commands and system.run[] items without the 'nowait' flag as well as Áú»¢¶Ä²© server executed scripts; Áú»¢¶Ä²© Java gateway has to be upgraded to support new functionality. |
3.0.x LTS | For: Áú»¢¶Ä²© 3.2 Áú»¢¶Ä²© 3.4 Áú»¢¶Ä²© 4.0 Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Database upgrade may be slow, depending on the history table size. |
2.4.x | For: Áú»¢¶Ä²© 3.0 Áú»¢¶Ä²© 3.2 Áú»¢¶Ä²© 3.4 Áú»¢¶Ä²© 4.0 Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Minimum required PHP version upped from 5.3.0 to 5.4.0 LogFile agent parameter must be specified |
2.2.x LTS | For: Áú»¢¶Ä²© 2.4 Áú»¢¶Ä²© 3.0 Áú»¢¶Ä²© 3.2 Áú»¢¶Ä²© 3.4 Áú»¢¶Ä²© 4.0 Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Node-based distributed monitoring removed |
2.0.x | For: Áú»¢¶Ä²© 2.2 Áú»¢¶Ä²© 2.4 Áú»¢¶Ä²© 3.0 Áú»¢¶Ä²© 3.2 Áú»¢¶Ä²© 3.4 Áú»¢¶Ä²© 4.0 Áú»¢¶Ä²© 4.2 Áú»¢¶Ä²© 4.4 Áú»¢¶Ä²© 5.0 Áú»¢¶Ä²© 5.2 Áú»¢¶Ä²© 5.4 Áú»¢¶Ä²© 6.0 |
Minimum required PHP version upped from 5.1.6 to 5.3.0; Case-sensitive MySQL database required for proper server work; character set utf8 and utf8_bin collation is required for Áú»¢¶Ä²© server to work properly with MySQL database. See database creation scripts. 'mysqli' PHP extension required instead of 'mysql' |
You may also want to check the requirements for 6.0.
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 Áú»¢¶Ä²© 6.0.x minor versions (for example, from 6.0.1 to 6.0.3), see Upgrade between minor versions.
Stop Áú»¢¶Ä²© server to make sure that no new data is inserted into database.
If upgrading Áú»¢¶Ä²© proxy, agent, or agent 2, stop these components too:
It is no longer possible to start the upgraded server and have older and unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Áú»¢¶Ä²©, now is officially disabled, as the server will ignore data from unupgraded proxies.
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 Áú»¢¶Ä²© 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 Áú»¢¶Ä²© 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 . Note, however, that packages for those versions may not include all Áú»¢¶Ä²© components. For a list of components included, see Áú»¢¶Ä²© 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 Áú»¢¶Ä²© 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 Áú»¢¶Ä²© agent 2 with the dnf install zabbix-agent2
command could lead to an error. For more information, see Known issues.
Then, to upgrade the web frontend with Apache and restart Apache, run:
Make sure to review Upgrade notes to check if any changes in the configuration parameters are required.
Start the updated Áú»¢¶Ä²© 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 Áú»¢¶Ä²© web interface to work properly.
It is possible to upgrade between Áú»¢¶Ä²© 6.0.x minor versions (for example, from 6.0.1 to 6.0.3).
To upgrade Áú»¢¶Ä²© minor version, please run:
To upgrade Áú»¢¶Ä²© server minor version only, please run:
To upgrade Áú»¢¶Ä²© agent minor version only, please run:
or, for Áú»¢¶Ä²© agent 2: