Official Zabbix packages are available for:
|RHEL 8, CentOS 8 and Oracle Linux 8||Download|
|RHEL 7, CentOS 7 and Oracle Linux 7||Download|
In this documentation we will refer to all 3 using the term
Install the repository configuration package. This package contains yum (software package manager) configuration files.
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:
To install Zabbix server on RHEL 7/8 (deprecated on RHEL 6) with MySQL support:
To install Zabbix proxy with MySQL support:
Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL, or with 'sqlite3' to use SQLite3 (proxy only).
To install Zabbix frontend on RHEL 8 with MySQL/Apache support:
To install Zabbix frontend on RHEL 7 (deprecated on RHEL 6) with MySQL/Apache support:
To install Zabbix frontend on RHEL 7/8 with MySQL/Nginx support:
Note that Nginx for RHEL is available only in EPEL.
Separate databases are needed for Zabbix server and Zabbix proxy; they cannot use the same database. Therefore, if they are installed on the same host, their databases must be created with different names!
Now import initial schema and data for the server with MySQL:
You will be prompted to enter your newly created database password.
With TimescaleDB, in addition to the previous command, also run:
TimescaleDB is supported with Zabbix server only.
For proxy, import initial schema:
For proxy with PostgreSQL (or SQLite):
Edit zabbix_server.conf (and zabbix_proxy.conf) to use their respective databases. For example:
In DBPassword use Zabbix database password for MySQL; PosgreSQL user password for PosgreSQL.
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 below for instructions.
To start Zabbix server process on RHEL8:
On RHEL 7:
On RHEL 7/8 with Nginx:
To make it start at system boot on RHEL 8:
On RHEL 7:
On RHEL 7/8 with Nginx:
RHEL prior to 7:
Substitute 'zabbix-server' with 'zabbix-proxy' if you are installing Zabbix proxy.
Depending on the web server used (Apache/Nginx) edit the corresponding configuration file for Zabbix frontend:
/etc/httpd/conf.d/zabbix.conf. Some PHP settings are already configured. Note that in RHEL 7 (but not in RHEL 8) it's necessary to uncomment and set the right date.timezone setting for you.
/etc/nginx/conf.d/zabbix.conf. For Zabbix frontend to work, it's necessary to uncomment and set
Its configuration file is located in
/etc/php-fpm.d/zabbix.conf. Some PHP settings are already configured. But it's necessary to set the right date.timezone setting for you in this file.
Now you are ready to proceed with frontend installation steps which will allow you to access your newly installed Zabbix.
Note that a Zabbix proxy does not have a frontend; it communicates with Zabbix server only.
Zabbix official repository provides fping, iksemel, libssh2 packages as well. These packages are located in the non-supported directory.
If you use RHEL 6 please read the section about using Zabbix frontend on RHEL 6 on how to configure the frontend.
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:
RHEL prior to 7:
As frontend and SELinux configuration is done, you need to restart Apache web server:
Zabbix frontend on RHEL 6 is not supported because of PHP version. Since Zabbix 3.0 the requirements are to have PHP 5.4.0 or later while RHEL 6 latest version is 5.3.3 .
In most cases Zabbix server and frontend are installed on the same machine. When upgrading 2.2 to 3.0 Zabbix server will perform database upgrade and frontend will stop working. There is no way to roll back the database changes so users will be forced to upgrade PHP using 3rd party packages. This is why Zabbix server is also deprecated on RHEL 6.
If you still want to use Zabbix frontend on RHEL 6 and upgraded your PHP using 3rd party packages you would need to enable
zabbix-deprecated repository first:
You will have to do some more manual configuration. This is because we cannot identify the Apache version required for your PHP which makes it impossible for us to provide proper Apache configuration for Zabbix frontend. We have included 2 Apache configuration files to our zabbix-web package, one for Apache 2.2 and another for 2.4, which you would need to integrate with the Apache configuration yourself:
To get the full path to the files execute:
To install the agent, run
To start the agent, run:
Substitute 'zabbix-agent' with 'zabbix-agent2' in these commands if using Zabbix agent 2 (only RHEL/CentOS 8).
If you want to run Zabbix agent as root, see here https://www.zabbix.com/documentation/4.4/manual/appendix/install/run_agent_as_root.
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.
::: noteclassic 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 packages contains debug information for all binary Zabbix componets.