Official Zabbix 5.0 LTS packages for Red Hat Enterprise Linux, CentOS, and Oracle Linux are available on Zabbix website.
Packages are available with either MySQL/PostgreSQL database and Apache/Nginx web server support.
Zabbix Official Repository provides fping, iksemel and libssh2 packages as well. These packages are located in the non-supported directory.
Verify CA encryption mode doesn't work on RHEL 7 with MySQL due to older MySQL libraries.
See installation instructions per platform in the download page for:
If you want to run Zabbix agent as root, see Running agent as root.
With TimescaleDB, in addition to the import command for PostgreSQL, also run:
TimescaleDB is supported with Zabbix server only.
Zabbix frontend requires additional packages not available in basic installation. You need to enable repository of optional rpms in the system you will run Zabbix frontend on:
Note that Nginx for RHEL is available in Red Hat Software Collections and in EPEL. If Red Hat Software Collections are used, simply install zabbix-nginx-conf-scl package.
Zabbix frontend requires PHP version 7.2 or newer starting with Zabbix 5.0.
Note that RHEL/CentOS 7 only provide PHP 5.4. See instructions for installing Zabbix frontend on Red Hat Enterprise Linux/CentOS 7.
Having SELinux status enabled in enforcing mode, you need to execute the following commands to enable communication between Zabbix frontend and server:
RHEL 7 and later:
If the database is accessible over network (including 'localhost' in case of PostgreSQL), you need to allow Zabbix frontend to connect to the database too:
RHEL prior to 7:
After the frontend and SELinux configuration is done, restart the Apache web server:
Once the required repository is added, you can install Zabbix proxy by running:
Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL, or with 'sqlite3' to use SQLite3 (proxy only).
Create a separate database for Zabbix proxy.
Zabbix server and Zabbix proxy cannot use the same database. If they are installed on the same host, the proxy database must have a different name.
Import initial schema:
For proxy with PostgreSQL (or SQLite):
In DBName for Zabbix proxy use a separate database from Zabbix server.
In DBPassword use Zabbix database password for MySQL; PostgreSQL user password for PostgreSQL.
DBHost= with PostgreSQL. You might want to keep the default setting
DBHost=localhost (or an IP address), but this would make PostgreSQL use a network socket for connecting to Zabbix. See SELinux configuration for instructions.
To start a Zabbix proxy process and make it start at system boot:
A Zabbix proxy does not have a frontend; it communicates with Zabbix server only.
It is required to install Java gateway only if you want to monitor JMX applications. Java gateway is lightweight and does not require a database.
Once the required repository is added, you can install Zabbix Java gateway by running:
Proceed to setup for more details on configuring and running Java gateway.
Debuginfo packages are currently available for RHEL/CentOS versions 7, 6 and 5.
To enable debuginfo repository edit /etc/yum.repos.d/zabbix.repo file. Change
enabled=1 for zabbix-debuginfo repository.
This will allow you to install the zabbix-debuginfo package.
This single package contains debug information for all binary Zabbix components.