Official Zabbix 6.3 PRE-RELEASE packages for SUSE Linux Enterprise Server are available on Zabbix website. Packages for Zabbix 6.4 will be available upon its release.
Verify CA encryption mode doesn't work on SLES 12 (all minor OS versions) with MySQL due to older MySQL libraries.
Install the repository configuration package. This package contains yum (software package manager) configuration files.
Please note, that Zabbix web service process, which is used for scheduled report generation, requires Google Chrome browser. The browser is not included into packages and has to be installed manually.
To install Zabbix server/frontend/agent with MySQL support:
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:
Substitute 'mysql' in the commands with 'pgsql' to use PostgreSQL.
The package 'zabbix-sql-scripts' contains database schemas for all supported database management systems for both Zabbix server and Zabbix proxy and will be used for data import.
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:
Edit /etc/zabbix/zabbix_server.conf (and zabbix_proxy.conf) to use their respective databases. For example:
In DBPassword use Zabbix database password for MySQL; PostgreSQL user password for PostgreSQL.
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.
Depending on the web server used (Apache/Nginx) edit the corresponding configuration file for Zabbix frontend:
/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.
/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/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.
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.
Start Zabbix server and agent processes and make it start at system boot.
With Apache web server:
Substitute 'apache2' with 'nginx' for Nginx web server.
To enable debuginfo repository edit /etc/zypp/repos.d/zabbix.repo file. Change
enabled=1 for zabbix-debuginfo repository.
This will allow you to install zabbix-<component>-debuginfo packages.