This section provides the steps required for a successful upgrade from Zabbix 4.0.x to Zabbix 4.2.x using official Zabbix packages for Red Hat Enterprise Linux/CentOS.
While upgrading Zabbix agents is not mandatory (but recommended), Zabbix server and proxies must be of the same major version. Therefore, in a server-proxy setup, Zabbix 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 4.2 may take a long time.
The following upgrade notes are available:
|Upgrade from||Read full upgrade notes||Most important changes between versions|
|Older proxies no longer can report data to an upgraded server;
Newer agents no longer will be able to work with an older Zabbix server
|'libpthread' and 'zlib' libraries now mandatory;
Support for plain text protocol dropped and header is mandatory;
Pre-1.4 version Zabbix agents are no longer supported;
The Server parameter in passive proxy configuration now mandatory
|SQLite support as backend database dropped for Zabbix server/frontend;
Perl Compatible Regular Expressions (PCRE) supported instead of POSIX extended;
'libpcre' and 'libevent' libraries mandatory for Zabbix server;
Exit code checks added for user parameters, remote commands and system.run items without the 'nowait' flag as well as Zabbix server executed scripts;
Zabbix Java gateway has to be upgraded to support new functionality
|Database upgrade may be slow, depending on the history table size|
You may also want to check the requirements for 4.2.
tail -f zabbix_server.logor
tail -f zabbix_proxy.login 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.
# systemctl stop zabbix-server
If upgrading the proxy, stop proxy too.
# systemctl stop zabbix-proxy
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.
# 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/doc/zabbix-* /opt/zabbix-backup/
To proceed with the upgrade your current repository package has to be updated.
# rpm -Uvh https://repo.zabbix.com/zabbix/4.2/rhel/7/x86_64/zabbix-release-4.2-1.el7.noarch.rpm
To upgrade Zabbix components you may run something like:
# yum upgrade zabbix-server-mysql zabbix-web-mysql zabbix-agent
If using PostgreSQL, substitute
pgsql in the command. If upgrading the proxy, substitute
proxy in the command.
See the upgrade notes for details on mandatory changes.
Start the updated Zabbix components.
# systemctl start zabbix-server # systemctl start zabbix-proxy # systemctl start zabbix-agent
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 4.2.x (for example, from 4.2.1 to 4.2.3). Upgrading between minor versions is easy.
To execute Zabbix minor version upgrade it is required to run:
$ sudo yum upgrade 'zabbix-*'
To execute Zabbix server minor version upgrade run:
$ sudo yum upgrade 'zabbix-server-*'
To execute Zabbix agent minor version upgrade run:
$ sudo yum upgrade 'zabbix-agent-*'
Note that you may also use 'update' instead of 'upgrade' in these commands. While 'upgrade' will delete obsolete packages, 'update' will preserve them.
The recommended way of adding Jabber notifications support to Zabbix server is rebuilding from source package.
$ sudo yum -y install iksemel-devel gcc $ rpm -ivh http://repo.zabbix.com/zabbix/4.2/rhel/7/SRPMS/zabbix-4.2.1-1.el7.src.rpm $ cd ~/rpmbuild/SPECS $ sudo yum-builddep -y zabbix.spec $ sed -i.bak -r 's/^(build_flags=.*--enable-server)"$/\1 --with-jabber"/;s/^(Release\s*:\s*[^1-9]*[1-9][0-9]*)(.*)/\1.1\2/' zabbix.spec $ rpmbuild -ba zabbix.spec [..] Wrote: /root/rpmbuild/SRPMS/zabbix-4.2.1-1.1.el7.src.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-agent-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-get-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-sender-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-proxy-mysql-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-proxy-pgsql-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-proxy-sqlite3-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-java-gateway-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-server-mysql-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-server-pgsql-4.2.1-1.1.el7.x86_64.rpm Wrote: /root/rpmbuild/RPMS/noarch/zabbix-web-4.2.1-1.1.el7.noarch.rpm Wrote: /root/rpmbuild/RPMS/noarch/zabbix-web-mysql-4.2.1-1.1.el7.noarch.rpm Wrote: /root/rpmbuild/RPMS/noarch/zabbix-web-pgsql-4.2.1-1.1.el7.noarch.rpm Wrote: /root/rpmbuild/RPMS/noarch/zabbix-web-japanese-4.2.1-1.1.el7.noarch.rpm Wrote: /root/rpmbuild/RPMS/x86_64/zabbix-debuginfo-4.2.1-1.1.el7.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.XFsa0b + umask 022 + cd /root/rpmbuild/BUILD + cd zabbix-4.2.1 + rm -rf /root/rpmbuild/BUILDROOT/zabbix-4.2.1-1.1.el7.x86_64 + exit 0