4. Установка из пакетов

Zabbix SIA поставляет официальные пакеты RPM и DEB для:

Файлы пакетов для репозиториев yum/dnf, apt и zypper для различных дистрибутивов ОС доступны в официальном репозитории Zabbix.

Некоторые дистрибутивы ОС (в частности, дистрибутивы на основе Debian) поставляют свои собственные пакеты Zabbix. Обратите внимание, что эти пакеты не поддерживаются компанией Zabbix. Пакеты Zabbix, поставляемые сторонними лицами, могут быть устаревшими, а также в них могут отсутствовать последние функции и исправления ошибок. Рекомендуется использовать только пакеты из официального репозитория Zabbix. Если ранее вы использовали неофициальные пакеты Zabbix, смотрите заметки касательно обновления пакетов Zabbix из репозиториев ОС.

Package installation notes

The following notes apply to all systems:

If using PostgreSQL, DBHost=localhost (or an IP address) in Zabbix server/proxy configuration makes PostgreSQL use a network socket instead of a local UNIX socket; see SELinux configuration for related setup instructions.
If using TimescaleDB, see additional TimescaleDB setup.
If installing Zabbix Java gateway (for monitoring JMX applications), see additional setup instructions for RHEL-based systems and Debian-based systems.
For running Zabbix agent as root, see Running agent as root.

The following notes apply to RHEL and its derivatives:

If you've enabled the EPEL repository for EL9, which also provides Zabbix packages, it must be excluded from package resolution before installing official Zabbix packages; see Accidental installation of EPEL Zabbix packages.
For installing Zabbix packages on Red Hat UBI environments, see Zabbix packages for RHEL on Red Hat UBI environments.
For using ICMP ping items, packages for fping are also available at the Zabbix Official Repository.
For using ..., packages for iksemel are also available at the Zabbix Official Repository.
For using ..., packages for libssh2 are also available at the Zabbix Official Repository.

SELinux configuration

Zabbix uses socket-based inter-process communication. On systems where Security-Enhanced Linux (SELinux) is enabled, you may need to add SELinux rules to allow Zabbix create/use UNIX domain sockets in the SocketDir directory. Socket files are used by Zabbix server (alerter, preprocessing, IPMI) and Zabbix proxy (IPMI), and they're present while the process is running.

Having SELinux enabled in enforcing mode, execute the following commands to enable communication between Zabbix frontend and server:

For RHEL 7 (and later), AlmaLinux, CentOS Stream, Oracle Linux, Rocky Linux 8 (and later):

setsebool -P httpd_can_connect_zabbix on

If the database is accessed over the network (including localhost for PostgreSQL), also allow Zabbix frontend to connect to the database:

setsebool -P httpd_can_network_connect_db on

For RHEL prior to 7:

setsebool -P httpd_can_network_connect on
       setsebool -P zabbix_can_network on

After applying SELinux settings, restart Apache:

systemctl restart httpd

Optionally, you can install a pre-defined zabbix-selinux-policy package from The Zabbix Official Repository. This package is provided for all supported OS versions to simplify Zabbix deployment and prevent users from turning off SELinux because of the configuration complexity.

For maximum security, it is recommended to set custom SELinux settings.

The zabbix-selinux-policy package contains a basic SELinux policy, allowing Zabbix to create and use sockets and enabling HTTPd connection to PostgreSQL (used by frontend).

The source zabbix_policy.te file contains the following rules:

module zabbix_policy 1.2;
       
       require {
           type zabbix_t;
           type zabbix_port_t;
           type zabbix_var_run_t;
           type postgresql_port_t;
           type httpd_t;
           class tcp_socket name_connect;
           class sock_file { create unlink };
           class unix_stream_socket connectto;
       }
       
       #============= zabbix_t ==============
       allow zabbix_t self:unix_stream_socket connectto;
       allow zabbix_t zabbix_port_t:tcp_socket name_connect;
       allow zabbix_t zabbix_var_run_t:sock_file create;
       allow zabbix_t zabbix_var_run_t:sock_file unlink;
       allow httpd_t zabbix_port_t:tcp_socket name_connect;
       
       #============= httpd_t ==============
       allow httpd_t postgresql_port_t:tcp_socket name_connect;

Debuginfo packages

Debuginfo packages contain debugging symbols for Zabbix binaries. They are not required for normal installation or operation but are useful for advanced troubleshooting.

To enable the zabbix-debuginfo repository:

On RHEL 6 or 7, edit /etc/yum.repos.d/zabbix.repo and set enabled=1 for the zabbix-debuginfo section:

[zabbix-debuginfo]
       name=Zabbix Official Repository debuginfo - $basearch
       baseurl=http://repo.zabbix.com/zabbix/7.0/stable/rhel/7/$basearch/debuginfo/
       enabled=1
       gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX-A14FE591
       gpgcheck=1

On SUSE, edit /etc/zypp/repos.d/zabbix.repo and set enabled=1 for the zabbix-debuginfo section:

[zabbix-debuginfo]
       name=Zabbix Official Repository debuginfo
       type=rpm-md
       baseurl=https://repo.zabbix.com/zabbix/7.0/stable/sles/15/x86_64/debuginfo/
       gpgcheck=1
       gpgkey=https://repo.zabbix.com/zabbix/7.0/stable/sles/15/x86_64/debuginfo/repodata/repomd.xml.key
       enabled=0
       update=1

Once enabled, install the packages:

On RHEL, install a single package with debug information for all Zabbix components:

dnf install zabbix-debuginfo

On SUSE, install component-specific debuginfo packages:

zypper install zabbix-<component>-debuginfo

Documentation

4. Установка из пакетов

Package installation notes

SELinux configuration

Debuginfo packages