[root@ZBXNWKMNTR ~]# service zabbix-server status
Redirecting to /bin/systemctl status zabbix-server.service
● zabbix-server.service - Zabbix Server
Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: resources) since Thu 2018-02-08 12:20:29 EST; 7s ago
Process: 28885 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
Process: 28938 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 28883 (code=exited, status=1/FAILURE)
CGroup: /system.slice/zabbix-server.service

Feb 08 12:20:29 systemd[1]: PID file /run/zabbix/zabbix_s....
Feb 08 12:20:29 systemd[1]: Failed to start Zabbix Server.
Feb 08 12:20:29 systemd[1]: Unit zabbix-server.service en....
Feb 08 12:20:29 systemd[1]: zabbix-server.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers

Unfortunately there isn’t a ton of information to work from here. Zabbix server by default logs to a file called zabbix_server.log. This file is likely in either /var/log or /tmp and should record some additional details of the failure that can be used to track down the source of this issue.

Disable Selinux

Thanks

Submit an Answer