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

systemctl status zabbix-agent.service
? zabbix-agent.service - Zabbix Agent
   Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: resources) since Tue 2016-11-08 20:16:06 CET; 6s ago
  Process: 52646 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
  Process: 52654 ExecStart=/usr/sbin/zabbix_agentd -c $CONFFILE (code=exited, status=0/SUCCESS)
 Main PID: 52644 (code=exited, status=1/FAILURE)
Nov 08 20:16:06 hostname systemd[1]: Failed to start Zabbix Agent.
Nov 08 20:16:06 hostname systemd[1]: Unit zabbix-agent.service entered failed state.
Nov 08 20:16:06 hostname systemd[1]: zabbix-agent.service failed.

Nov  8 20:06:11 hostname systemd: zabbix-agent.service holdoff time over, scheduling restart.
Nov  8 20:06:11 hostname systemd: Starting Zabbix Agent...
Nov  8 20:06:11 hostname systemd: zabbix-agent.service: Supervising process 52333 which is not our child. We'll most likely not notice when it exits.
Nov  8 20:06:11 hostname systemd: Started Zabbix Agent.
Nov  8 20:06:11 hostname systemd: zabbix-agent.service: main process exited, code=exited, status=1/FAILURE
Nov  8 20:06:11 hostname kill: Usage:
Nov  8 20:06:11 hostname kill: kill [options] <pid|name> [...]
Nov  8 20:06:11 hostname systemd: zabbix-agent.service: control process exited, code=exited status=1
Nov  8 20:06:11 hostname kill: Options:
Nov  8 20:06:11 hostname kill: -a, --all              do not restrict the name-to-pid conversion to processes
Nov  8 20:06:11 hostname kill: with the same uid as the present process
Nov  8 20:06:11 hostname kill: -s, --signal <sig>     send specified signal
Nov  8 20:06:11 hostname kill: -q, --queue <sig>      use sigqueue(2) rather than kill(2)
Nov  8 20:06:11 hostname kill: -p, --pid              print pids without signaling them
Nov  8 20:06:11 hostname kill: -l, --list [=<signal>] list signal names, or convert one to a name
Nov  8 20:06:11 hostname kill: -L, --table            list signal names and numbers
Nov  8 20:06:11 hostname kill: -h, --help     display this help and exit
Nov  8 20:06:11 hostname kill: -V, --version  output version information and exit
Nov  8 20:06:11 hostname kill: For more details see kill(1).
Nov  8 20:06:11 hostname systemd: Unit zabbix-agent.service entered failed state.
Nov  8 20:06:11 hostname systemd: zabbix-agent.service failed.

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?