Official Zabbix 6.5 PRE-RELEASE packages for SUSE Linux Enterprise Server are available on Zabbix website. Packages for Zabbix 7.0 will be available upon its release.
Please note that on SLES 12 the following features are not available:
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 PHP 7, Apache and MySQL support, run:
Substitute component names in this command as needed:
zabbix-apache-conf. See also: Nginx setup for Zabbix on SLES 12/15.
zabbix-apache-conffor Apache; use
zabbix-agent2instead of or in addition to
To install Zabbix proxy with MySQL support:
For PostgreSQL, use
zabbix-proxy-pgsql instead of
For SQLite3, use
zabbix-proxy-sqlite3 instead of
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.
To create a database, follow the instructions for MySQL or PostgreSQL. An SQLite3 database (supported for Zabbix proxy only) will be created automatically and does not require additional installation steps.
Separate databases are required for Zabbix server and Zabbix proxy; they cannot share the same database. If a server and a proxy 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. While some PHP settings may already be configured, it's essential that you uncomment the
date.timezone setting and specify the appropriate timezone setting that suits your requirements.
/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 (the path may vary slightly depending on the service pack).
Now you are ready to proceed with frontend installation steps that 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:
For Nginx, substitute
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.