Job for zabbix server service failed because the control process exited with error code

I just installed Zabbix 5.0 LTS (The Latest verion of Zabbix) on RHEL-8 OS. On logging in the Zabbix front end, I gett a message saying «Zabbix server is not working». & bar below says:»Zabbix server not working.Information delayed may not be current».Kindly provide help?

Edit:My server port is 10051.

On entering «service zabbix start», I get output:

Redirecting to /bin/systemctl start zabbix.service
Failed to start zabbix.service:Unit zabbix.service not found.

& on entering «systemctl restart zabbix-server zabbix-agent httpd php-fpm», I get:

Job for zabbix-server.service failed because the control process exited with error code.
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

Output of «journalctl -xe»:

RHEL8 platform-python[5746]: SELinux is preventing zabbix_server from using the dac_override capability.
*** Plugin dac_overrride (91.4 confidence) suggests ************************

If you want to help identify if domain needs this access or you have a file with the wrong permissions on your system
Then turn on full auditing to get path information about the offending file and generate the error again.
Do

Turn on full auditing
#auditctl -w /etc/shadow -p w
Try to recreate AVC.Then execute
#ausearch -m avc -ts recent
If you see PATH record check ownership/permissions on file, and fix it,
otherwise report as a bugzilla

*** Plugin catchall (9.59 confidence) suggests *************************

If you believe that zabbix_server should have the dac_override capability by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
#ausearch -c 'zabbix_server' --raw | audit2allow -M my-zabbixserver
#semodule -X 300 -i my-zabbixserver.pp            

RHEL8 dbus-daemon[779]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.40' (uid=0 pid=748 comm="/usr/sbin/sedispatch " label="sytem_u:system_r:auditd_t:s0") (using servicehelper)

On entering «systemctl status zabbix-server.service», I get output:

zabbix-server.service-Zabbix server: Loaded:....
                                     Active:....
                                     Process: 4959 ExecStart=/usr/sbin/zabbix_server -c $CONFILE (code=exited,status=1/FAILURE) 
RHEL8 systemd[1]:zabbix-server.service:Control process exited,code=exited status=1
RHEL8 systemd[1]:zabbix-server.service:Failed with result 'exit-code'.
RHEL8 systemd[1]:Failed to start Zabbix Server. What do I do now?

I just installed Zabbix-5.0 LTS on RHEL-8 OS. After logging in on the Zabbix fronend, I get message that «Zabbix server is not running:the information displayed may not be correct». Kindly help me with server installation.

My Zabbix server port is 10051.

On entering service zabbix start, I get output:

Redirecting to /bin/systemctl start zabbix.service
Failed to start zabbix.service:Unit zabbix.service not found.

and on entering systemctl restart zabbix-server zabbix-agent httpd php-fpm I get:

Job for zabbix-server.service failed because the control process exited with error code.
See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

Output of «journalctl -xe»:

RHEL8 platform-python[5746]: SELinux is preventing zabbix_server from using the dac_override capability.

*** Plugin dac_overrride (91.4 confidence) suggests ************************
If you want to help identify if domain needs this access or you have a file with the wrong permissions on your system
Then turn on full auditing to get path information about the offending file and generate the error again.
Do

Turn on full auditing
#auditctl -w /etc/shadow -p w
Try to recreate AVC.Then execute
#ausearch -m avc -ts recent
If you see PATH record check ownership/permissions on file, and fix it,
otherwise report as a bugzilla

*** Plugin catchall (9.59 confidence) suggests *************************

If you believe that zabbix_server should have the dac_override capability by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
#ausearch -c 'zabbix_server' --raw | audit2allow -M my-zabbixserver
#semodule -X 300 -i my-zabbixserver.pp           

RHEL8 dbus-daemon[779]: [system] Activating service name='org.fedoraproject.Setroubleshootd' requested by ':1.40' (uid=0 pid=748 comm="/usr/sbin/sedispatch " label="sytem_u:system_r:auditd_t:s0") (using servicehelper)

On entering «systemctl status zabbix-server.service», I get output:

zabbix-server.service-Zabbix server: Loaded:....
                                   Active:....
                                   Process: 4959 
ExecStart=/usr/sbin/zabbix_server -c $CONFILE (code=exited,status=1/FAILURE)
RHEL8 systemd[1]:zabbix-server.service:Control process exited,code=exited status=1
RHEL8 systemd[1]:zabbix-server.service:Failed with result 'exit-code'.
RHEL8 systemd[1]:Failed to start Zabbix Server. What do I do now?

Status of Zabbix

Parameter Value Details
Zabbix server is running No localhost:10051

cat /var/log/zabbix/zabbix_server.log
.
.
.
zabbix_server [19361]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19374]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19379]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19384]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19389]: cannot open log: cannot create semaphore set: [28] No space left on device
zabbix_server [19398]: cannot open log: cannot create semaphore set: [28] No space left on device
----------------------------------------------------------------------------------------------------

[[email protected] admin]# systemctl restart zabbix_server
Failed to restart zabbix_server.service: Unit zabbix_server.service failed to load: No such file or directory.
------------------------------------------------------------------------------------------------------
[[email protected] admin]# systemctl restart zabbix-server
Job for zabbix-server.service failed because the control process exited with error code. See "systemctl status zabbix-server.service" and "journalctl -xe" for details.

-------------------------------------------------------------------------------------------------------
[[email protected] admin]# 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: exit-code) since Wed 2018-08-15 00:19:46 EDT; 4s ago
 Process: 20099 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=1/FAILURE)

Aug 15 00:19:46 localhost.localdomain systemd[1]: Failed to start Zabbix Server.
Aug 15 00:19:46 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
Aug 15 00:19:46 localhost.localdomain systemd[1]: zabbix-server.service failed.
[[email protected] admin]#
--------------------------------------------------------------

[[email protected] admin]# cat /etc/selinux/config

# 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=disabled
# SELINUXTYPE= can take one of three two values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted