Official Zabbix 7.0 packages for SUSE Linux Enterprise Server are available on Zabbix website.
Zabbix agent packages and utilities Zabbix get and Zabbix sender are available in Zabbix Official Repository for SLES 15 (SP4 and newer) and SLES 12 (SP4 and newer).
Please note that SLES 12 can be used only for Zabbix proxy and the following features are not available:
Install the repository configuration package. This package contains yum (software package manager) configuration files.
SLES 15:
rpm -Uvh --nosignature https://repo.zabbix.com/zabbix/7.0/sles/15/x86_64/zabbix-release-latest.sles15.noarch.rpm
zypper --gpg-auto-import-keys refresh 'Zabbix Official Repository'
SLES 12 (proxy only):
rpm -Uvh --nosignature https://repo.zabbix.com/zabbix/7.0/sles/12/x86_64/zabbix-release-latest.sles12.noarch.rpm
zypper --gpg-auto-import-keys refresh 'Zabbix Official Repository'
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 8, Apache and MySQL support, run:
Substitute component names in this command as needed:
zabbix-nginx-conf-php8
instead of zabbix-apache-conf-php8
. See also: Nginx setup for Zabbix on SLES 15.zabbix-server-pgsql
instead of zabbix-server-mysql
; use zabbix-web-pgsql
instead of zabbix-web-mysql
.zabbix-agent2
instead of or in addition to zabbix-agent
.To install Zabbix proxy with MySQL support:
For PostgreSQL, use zabbix-proxy-pgsql
instead of zabbix-proxy-mysql
.
For SQLite3, use zabbix-proxy-sqlite3
instead of zabbix-proxy-mysql
.
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.
Zabbix server and proxy daemons require a database. Zabbix agent does not need a database.
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 PostgreSQL:
With TimescaleDB, in addition to the previous command, also run:
zcat /usr/share/packages/zabbix-sql-scripts/postgresql/timescaledb/schema.sql.gz | sudo -u <username> psql zabbix
TimescaleDB is supported with Zabbix server only.
For proxy, import initial schema:
For proxy with PostgreSQL:
Edit Zabbix server configuration file (/etc/zabbix/zabbix_server.conf
) and, if required, Zabbix proxy configuration file (/etc/zabbix/zabbix_proxy.conf
) for their respective databases. For example:
In DBPassword use Zabbix database password for MySQL; PostgreSQL user password for PostgreSQL.
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.
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/apache2/conf.d/zabbix.conf
. 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
and/or server_name
directives.Its configuration file is located in /etc/php8/fpm/php-fpm.d/zabbix.conf
(the path may vary slightly depending on the service pack).
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 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:
systemctl restart zabbix-server zabbix-agent apache2 php-fpm
systemctl enable zabbix-server zabbix-agent apache2 php-fpm
For Nginx, substitute apache2
with nginx
.
To enable debuginfo repository edit /etc/zypp/repos.d/zabbix.repo file. Change enabled=0
to enabled=1
for zabbix-debuginfo repository.
[zabbix-debuginfo]
name=Zabbix Official Repository debuginfo
type=rpm-md
baseurl=http://repo.zabbix.com/zabbix/7.0/sles/15/x86_64/debuginfo/
gpgcheck=1
gpgkey=http://repo.zabbix.com/zabbix/7.0/sles/15/x86_64/debuginfo/repodata/repomd.xml.key
enabled=0
update=1
This will allow you to install zabbix-<component>-debuginfo packages.