Esta é uma tradução da página de documentação original em inglês. Ajude-nos a torná-la melhor.

3 SUSE Linux Enterprise Server


Official Zabbix packages are available for:

SUSE Linux Enterprise Server 15 Download
SUSE Linux Enterprise Server 12 Download

Verify CA encryption mode doesn't work on SLES 12 (all minor OS versions) with MySQL due to older MySQL libraries.

Adding Zabbix repository

Install the repository configuration package. This package contains yum (software package manager) configuration files.

SLES 15:

# rpm -Uvh --nosignature
       # zypper --gpg-auto-import-keys refresh 'Zabbix Official Repository' 

SLES 12:

# rpm -Uvh --nosignature
       # zypper --gpg-auto-import-keys refresh 'Zabbix Official Repository' 

Server/frontend/agent installation

To be able to install Zabbix frontend Web and Scripting Module must be activated. It contains the necessary PHP dependencies.

SLES 15:

# SUSEConnect -p sle-module-web-scripting/15/x86_64

SLES 12:

# SUSEConnect -p sle-module-web-scripting/12/x86_64

To install Zabbix server/frontend/agent with MySQL support:

# zypper install zabbix-server-mysql zabbix-web-mysql zabbix-apache-conf zabbix-agent

Substitute 'apache' in the command with 'nginx' if using the package for Nginx web server. See also: Nginx setup for Zabbix on SLES 12/15.

Substitute 'zabbix-agent' with 'zabbix-agent2' in these commands if using Zabbix agent 2 (only SLES 15 SP1+).

To install Zabbix proxy with MySQL support:

# zypper install zabbix-proxy-mysql

Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL.

Creating database

For Zabbix server and proxy daemons a database is required. It is not needed to run Zabbix agent.

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!

Create the database using the provided instructions for MySQL or PostgreSQL.

Importing data

Now import initial schema and data for the server with MySQL:

# zcat /usr/share/doc/packages/zabbix-server-mysql*/create.sql.gz | mysql -uzabbix -p zabbix

You will be prompted to enter your newly created database password.

With PostgreSQL:

# zcat /usr/share/doc/packages/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/packages/zabbix-server-pgsql*/timescaledb.sql.gz | sudo -u <username> psql zabbix

TimescaleDB is supported with Zabbix server only.

For proxy, import initial schema:

# zcat /usr/share/doc/packages/zabbix-proxy-mysql*/schema.sql.gz | mysql -uzabbix -p zabbix

For proxy with PostgreSQL:

# zcat /usr/share/doc/packages/zabbix-proxy-pgsql*/schema.sql.gz | sudo -u <username> psql zabbix

Configure database for Zabbix server/proxy

Edit /etc/zabbix/zabbix_server.conf (and zabbix_proxy.conf) to use their respective databases. For example:

# vi /etc/zabbix/zabbix_server.conf

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.

Zabbix frontend configuration

Depending on the web server used (Apache/Nginx) edit the corresponding configuration file for Zabbix frontend:

  • For Apache the configuration file is located in /etc/apache2/conf.d/zabbix.conf. Some PHP settings are already configured. But it's necessary to uncomment the "date.timezone" setting and set the right timezone 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
  • The zabbix-nginx-conf package installs a separate Nginx server for Zabbix frontend. Its configuration file is located in /etc/nginx/conf.d/zabbix.conf. For Zabbix frontend to work, it's necessary to uncomment and set listen and/or server_name directives.
# listen 80;
       # server_name;
  • Zabbix uses its own dedicated php-fpm connection pool with Nginx:

Its configuration file is located in /etc/php7/fpm/php-fpm.d/zabbix.conf. Some PHP settings are already configured. But it's necessary to 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[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.

Starting Zabbix server/agent process

Start Zabbix server and agent processes and make it start at system boot.

With Apache web server:

# systemctl restart zabbix-server zabbix-agent apache2 php-fpm
       # systemctl enable zabbix-server zabbix-agent apache2 php-fpm

Substitute 'apache2' with 'nginx' for Nginx web server.

Installing debuginfo packages

To enable debuginfo repository edit /etc/zypp/repos.d/zabbix.repo file. Change enabled=0 to enabled=1 for zabbix-debuginfo repository.

       name=Zabbix Official Repository debuginfo

This will allow you to install zabbix-<component>-debuginfo packages.