1 Red Hat Enterprise Linux/CentOS

Packages are available with either MySQL/PostgreSQL database and Apache/Nginx webserver support.

Verify CA encryption mode doesn’t work on RHEL 7 with MySQL due to older MySQL libraries.

Zabbix agent packages and utilities Zabbix get and Zabbix sender are available for , RHEL 6 and as well.

Zabbix official repository provides fping and libssh2 packages as well. These packages are located in the non-supported directory.

See per platform in the download page for:

  • installing server/agent/frontend
  • creating initial database, importing initial data
  • configuring database for Zabbix server
  • configuring PHP for Zabbix frontend
  • starting server/agent processes
  • configuring Zabbix frontend

If you want to run Zabbix agent as root, see Running agent as root.

Zabbix web service process, which is used for , requires Google Chrome browser. The browser is not included into packages and has to be installed manually.

Importing data with Timescale DB

With TimescaleDB, in addition to the import command for PostgreSQL, also run:

TimescaleDB is supported with Zabbix server only.

PHP 7.2

Zabbix frontend requires PHP version 7.2 or newer.

SELinux configuration

RHEL 7 and later:

  2.        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:
  3.        # setsebool -P httpd_can_network_connect_db on

RHEL prior to 7:

  1. # setsebool -P httpd_can_network_connect on
  2.        # setsebool -P zabbix_can_network on

After the frontend and SELinux configuration is done, restart the Apache web server:

  1. # service httpd restart

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).

Creating database

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.

Importing data

Import initial schema:

  1. # cat /usr/share/doc/zabbix-sql-scripts/mysql/proxy.sql | mysql -uzabbix -p zabbix

For proxy with PostgreSQL (or SQLite):

Configure database for Zabbix proxy

Edit zabbix_proxy.conf:

  1. # vi /etc/zabbix/zabbix_proxy.conf
  2.        DBHost=localhost
  3.        DBName=zabbix
  4.        DBUser=zabbix
  5.        DBPassword=<password>

In DBPassword use Zabbix database password for MySQL; PosgreSQL user password for PosgreSQL.

Use 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 for instructions.

Starting Zabbix proxy process

To start a Zabbix proxy process and make it start at system boot:

Frontend configuration

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 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=0 to enabled=1 for zabbix-debuginfo repository.

  1. [zabbix-debuginfo]
  2.        name=Zabbix Official Repository debuginfo - $basearch
  3.        baseurl=http://repo.zabbix.com/zabbix/5.5/rhel/7/$basearch/debuginfo/
  4.        enabled=0
  5.        gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591

This will allow you to install the zabbix-debuginfo package.