Zabbix Documentation 4.2

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


Sidebar

manual:installation:upgrade:packages:rhel_centos

1 Red Hat Enterprise Linux/CentOS

Overview

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.

Please note, that support for Jabber notifications was removed from official Zabbix server packages starting from version 4.2.0-1 due to the lack of support for and vulnerable libiksemel library. If you still need it, see this section for instructions.

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.

Before the upgrade make sure to read the relevant upgrade notes!

The following upgrade notes are available:

Upgrade fromRead full upgrade notesMost important changes between versions
4.0.x LTS For:
Zabbix 4.2
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
3.4.x For:
Zabbix 4.0
Zabbix 4.2
'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
3.2.x For:
Zabbix 3.4
Zabbix 4.0
Zabbix 4.2
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
3.0.x LTS For:
Zabbix 3.2
Zabbix 3.4
Zabbix 4.0
Zabbix 4.2
Database upgrade may be slow, depending on the history table size

You may also want to check the requirements for 4.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.

Upgrade procedure

1 Stop Zabbix processes

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
It is no longer possible to start the upgraded server and have older, yet unupgraded proxies report data to a newer server. This approach, which was never recommended nor supported by Zabbix, now is officially disabled when upgrading to 4.2 (or later) from any version before 4.2, as the server will ignore data from unupgraded proxies.
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/

PHP files and Zabbix binaries:

# cp -R /usr/share/zabbix/ /opt/zabbix-backup/
# cp -R /usr/share/doc/zabbix-* /opt/zabbix-backup/
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/4.2/rhel/7/x86_64/zabbix-release-4.2-1.el7.noarch.rpm
5 Upgrade Zabbix components

To upgrade Zabbix components you may run something like:

# yum upgrade 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.

6 Review component configuration parameters

See the upgrade notes for details on mandatory changes.

7 Start Zabbix processes

Start the updated Zabbix components.

# systemctl start zabbix-server
# systemctl start zabbix-proxy
# systemctl start zabbix-agent
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 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.

Adding Jabber notifications support to Zabbix server package

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