How to handle ZABBIX server startup failure

Error recurrence

[[email protected] data]# systemctl status zabbix-server 
● zabbix-server.service - Zabbix Server
   Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since  Four  2022-06-09 16:18:54 CST; 6s ago
  Process: 34789 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
  Process: 34768 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
 Main PID: 34770 (code=exited, status=0/SUCCESS)

6 month  09 16:18:54 ncayu101 kill[34789]: -q, --queue <sig>      use sigqueue(2) rather than kill(2)
6 month  09 16:18:54 ncayu101 kill[34789]: -p, --pid              print pids without signaling them
6 month  09 16:18:54 ncayu101 kill[34789]: -l, --list [=<signal>] list signal names, or convert one to a name
6 month  09 16:18:54 ncayu101 kill[34789]: -L, --table            list signal names and numbers
6 month  09 16:18:54 ncayu101 kill[34789]: -h, --help     display this help and exit
6 month  09 16:18:54 ncayu101 kill[34789]: -V, --version  output version information and exit
6 month  09 16:18:54 ncayu101 kill[34789]: For more details see kill(1).
6 month  09 16:18:54 ncayu101 systemd[1]: zabbix-server.service: control process exited, code=exited status=1
6 month  09 16:18:54 ncayu101 systemd[1]: Unit zabbix-server.service entered failed state.
6 month  09 16:18:54 ncayu101 systemd[1]: zabbix-server.service failed.

As mentioned in the prompt SElinux, The inspection found that it was not closed SELinux

[[email protected] data]# getenforce
Enforcing
[[email protected] data]# sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Max kernel policy version:      31

close SELinux

1. With root Permission remote connection ECS example . Please refer to the overview of connection methods .

2. Run the command getenforce, verification SELinux state .
	 Return status if yes enforcing, indicate SELinux Enabled .

3. Select temporary shutdown or permanent shutdown SELinux.
	 Carry out orders setenforce 0 Temporarily Closed SELinux.
	 Permanent ban SElinux.

[[email protected] data]# getenforce
Enforcing

#  Temporarily Closed  SELinux
[[email protected] data]# setenforce 0
[[email protected] data]# 
[[email protected] data]# 
[[email protected] data]# getenforce
Permissive

• a. Run the following command , edit SELinux Of config file .
  vim /etc/selinux/config
• b. find SELINUX=enforcing, Press i Enter edit mode , Change the parameter to SELINUX=disabled.

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=enforcing
# SELINUXTYPE= can take one of three values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected. 
# mls - Multi Level Security protection.
SELINUXTYPE=targeted

I've revised it

• c. After the modification is completed , Press the keyboard Esc key , Carry out orders :wq, Save and exit the file .

• d. restart ECS example .

shutdown -r now

• e. After restart , Run the command getenforce, verification SELinux Status as disabled, indicate SELinux closed .

start-up zabbix

systemctl start zabbix-server zabbix-agent httpd rh-php72-php-fpm

# Linux View in 
curl http://192.168.70.133/zabbix/setup.php

View it in a browser