Official Zabbix packages are available for:
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.
# rpm -Uvh https://repo.zabbix.com/zabbix/4.4/rhel/8/x86_64/zabbix-release-4.4-1.el8.noarch.rpm
# rpm -Uvh https://repo.zabbix.com/zabbix/4.4/rhel/7/x86_64/zabbix-release-4.4-1.el7.noarch.rpm
# rpm -Uvh https://repo.zabbix.com/zabbix/4.4/rhel/6/x86_64/zabbix-release-4.4-1.el6.noarch.rpm
# rpm -Uvh https://repo.zabbix.com/zabbix/4.4/rhel/5/x86_64/zabbix-release-4.4-1.el5.noarch.rpm
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:
# yum-config-manager --enable rhel-7-server-optional-rpms
To install Zabbix server on RHEL 7/8 (deprecated on RHEL 6) with MySQL support:
# yum install zabbix-server-mysql
To install Zabbix proxy with MySQL support:
# yum install zabbix-proxy-mysql
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:
# yum install zabbix-web-mysql zabbix-apache-conf
To install Zabbix frontend on RHEL 7 (deprecated on RHEL 6) with MySQL/Apache support:
# yum install zabbix-web-mysql
To install Zabbix frontend on RHEL 7/8 with MySQL/Nginx support:
# yum install epel-release # yum install zabbix-web-mysql zabbix-nginx-conf
Note that Nginx for RHEL is available only in EPEL.
Now import initial schema and data for the server with MySQL:
# zcat /usr/share/doc/zabbix-server-mysql*/create.sql.gz | mysql -uzabbix -p zabbix
You will be prompted to enter your newly created database password.
# zcat /usr/share/doc/zabbix-server-pgsql*/create.sql.gz | sudo -u <username> psql zabbix
With TimescaleDB, in addition to the previous command, also run:
# zcat /usr/share/doc/zabbix-server-pgsql*/timescaledb.sql.gz | sudo -u <username> psql zabbix
For proxy, import initial schema:
# zcat /usr/share/doc/zabbix-proxy-mysql*/schema.sql.gz | mysql -uzabbix -p zabbix
For proxy with PostgreSQL (or SQLite):
# zcat /usr/share/doc/zabbix-proxy-pgsql*/schema.sql.gz | sudo -u <username> psql zabbix # zcat /usr/share/doc/zabbix-proxy-sqlite3*/schema.sql.gz | sqlite3 zabbix.db
Edit zabbix_server.conf (and zabbix_proxy.conf) to use their respective databases. For example:
# vi /etc/zabbix/zabbix_server.conf DBHost=localhost DBName=zabbix DBUser=zabbix DBPassword=<password>
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:
# service zabbix-server httpd php-fpm start
On RHEL 7:
# service zabbix-server httpd start
On RHEL 7/8 with Nginx:
# service zabbix-server nginx php-fpm start
To make it start at system boot on RHEL 8:
# systemctl enable zabbix-server httpd php-fpm
On RHEL 7:
# systemctl enable zabbix-server httpd
On RHEL 7/8 with Nginx:
# systemctl enable zabbix-server nginx php-fpm
RHEL prior to 7:
# chkconfig --level 12345 zabbix-server on
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.
php_value max_execution_time 300 php_value memory_limit 128M php_value post_max_size 16M php_value upload_max_filesize 2M php_value max_input_time 300 php_value max_input_vars 10000 php_value always_populate_raw_post_data -1 # php_value date.timezone Europe/Riga
/etc/nginx/conf.d/zabbix.conf. For Zabbix frontend to work, it's necessary to uncomment and set
# listen 80; # server_name example.com;
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.
php_value[max_execution_time] = 300 php_value[memory_limit] = 128M php_value[post_max_size] = 16M php_value[upload_max_filesize] = 2M php_value[max_input_time] = 300 php_value[max_input_vars] = 10000 ; php_value[date.timezone] = Europe/Riga
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.
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:
# setsebool -P httpd_can_connect_zabbix on 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: # setsebool -P httpd_can_network_connect_db on
RHEL prior to 7:
# setsebool -P httpd_can_network_connect on # setsebool -P zabbix_can_network on
As frontend and SELinux configuration is done, you need to restart Apache web server:
# service httpd restart
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:
$ rpm -ql zabbix-web | grep example.conf
To install the agent, run
# yum install zabbix-agent
To start the agent, run:
# service zabbix-agent start
Substitute 'zabbix-agent' with 'zabbix-agent2' in these commands if using Zabbix agent 2 (only RHEL/CentOS 8).
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:
# yum install zabbix-java-gateway
Proceed to setup for more details on configuring and running Java gateway.
To enable debuginfo repository edit /etc/yum.repos.d/zabbix.repo file.
enabled=1 for zabbix-debuginfo repository.
[zabbix-debuginfo] name=Zabbix Official Repository debuginfo - $basearch baseurl=http://repo.zabbix.com/zabbix/4.4/rhel/7/$basearch/debuginfo/ enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591 gpgcheck=1
This will allow you to install the zabbix-debuginfo package.
# yum install zabbix-debuginfo
This single packages contains debug information for all binary Zabbix componets.