zabbix无法启动

在配置zabbix邮件报警时遇到，配置完脚本后zabbix网站无法打开

服务正常启动无报错，但查看端口发现10051端口并未启动

查看日志：

cat /usr/local/zabbix/zabbix_server.log

发现报错：

  9548:20231215:165528.456 syncing trend data...
  9548:20231215:165528.457 syncing trend data done
  9548:20231215:165528.457 Zabbix Server stopped. Zabbix 5.0.40 (revision 8856587278e).
  9573:20231215:165538.572 Starting Zabbix Server. Zabbix 5.0.40 (revision 8856587278e).
  9573:20231215:165538.572 ****** Enabled features ******
  9573:20231215:165538.572 SNMP monitoring:           YES
  9573:20231215:165538.572 IPMI monitoring:           YES
  9573:20231215:165538.572 Web monitoring:            YES
  9573:20231215:165538.572 VMware monitoring:         YES
  9573:20231215:165538.572 SMTP authentication:       YES
  9573:20231215:165538.572 ODBC:                      YES
  9573:20231215:165538.572 SSH support:               YES
  9573:20231215:165538.572 IPv6 support:              YES
  9573:20231215:165538.572 TLS support:               YES
  9573:20231215:165538.572 ******************************
  9573:20231215:165538.572 using configuration file: /etc/zabbix/zabbix_server.conf
  9573:20231215:165538.577 current database version (mandatory/optional): 05000000/05000007
  9573:20231215:165538.577 required mandatory version: 05000000
  9573:20231215:165538.594 server #0 started [main process]
  9581:20231215:165538.594 server #1 started [configuration syncer #1]
  9584:20231215:165538.698 server #2 started [alert manager #1]
  9584:20231215:165538.698 cannot initialize alert manager: Cannot bind socket to "/var/run/zabbix/zabbix_server_alerter.sock": [13] Permission denied.
  9573:20231215:165538.701 One child process died (PID:9584,exitcode/signal:1). Exiting ...
  9587:20231215:165538.701 server #5 started [alerter #3]
  9573:20231215:165538.704 syncing trend data...
  9573:20231215:165538.705 syncing trend data done
  9573:20231215:165538.706 Zabbix Server stopped. Zabbix 5.0.40 (revision 8856587278e).

显示配置文件正确，但无法将套接字绑定到“/var/run/zabbix/zabbix_server_alerter.sock”

查看文件存在

后发现没有关闭防火墙和selinux,执行命令：

setenforce 0 && systemctl stop firewalld

再次启动服务，查看端口，服务启动成功。

问题解决，间隔一个晚上忘记关闭防火墙了。