Zabbix server is not running: the information displayed may not be current

[modamer5]

Dears ALL,

I have successfully installed the Zabbix server, And I added some Switch to make sure everything was fine, After two days, I started adding all switches, including about 70 devices Through the Discovery Service, After that the alert message started to appear on the screen " Zabbix server is not running: the information displayed may not be current" and from System information Dashboard page, I see: Zabbix server is running Value NO.

please i need some Help ...


[[root@localhost ~]# 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 Mon 2021-05-03 12:33:00 EDT; 6s ago
Process: 34972 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)
Process: 34968 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
Main PID: 34970 (code=exited, status=0/SUCCESS)

May 03 12:33:00 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:33:00 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
May 03 12:33:00 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:33:00 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.




[root@localhost ~]# sudo tail /var/log/zabbix/zabbix_server.log
34789:20210503:122824.948 5: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](zbx_thread_start+0x37) [0x55e417cd104d]
34789:20210503:122824.948 4: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](MAIN_ZABBIX_ENTRY+0xaae) [0x55e417b2c122]
34789:20210503:122824.948 3: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](daemon_start+0x2ff) [0x55e417cc18c1]
34789:20210503:122824.948 2: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](main+0x2f5) [0x55e417b2b629]
34789:20210503:122824.948 1: /lib64/libc.so.6(__libc_start_main+0xf3) [0x7fb82cb447b3]
34789:20210503:122824.948 0: /usr/sbin/zabbix_server: configuration syncer [syncing configuration](_start+0x2e) [0x55e417b2a65e]
34788:20210503:122824.952 One child process died (PID:34789,exitcode/signal:1). Exiting ...
34788:20210503:122824.952 syncing trend data...
34788:20210503:122824.953 syncing trend data done
34788:20210503:122824.953 Zabbix Server stopped. Zabbix 5.2.6 (revision 798506596c).

[root@localhost ~]# journalctl -xe
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:28:02 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:28:02 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:28:02 localhost.localdomain kill[34776]: kill: not enough arguments
May 03 12:28:02 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:28:02 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:28:13 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:28:13 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 780.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:28:13 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:28:13 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 780.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:28:13 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:28:13 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:28:13 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:28:13 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:28:14 localhost.localdomain kill[34783]: kill: not enough arguments
May 03 12:28:14 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:28:14 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:28:24 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:28:24 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 781.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:28:24 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:28:24 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:28:24 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:28:24 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:28:24 localhost.localdomain kill[34790]: kill: not enough arguments
May 03 12:28:24 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:28:24 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:28:32 localhost.localdomain sudo[34793]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/bin/tail /var/log/zabbix/zabbix_server.log
May 03 12:28:32 localhost.localdomain sudo[34793]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice
May 03 12:28:32 localhost.localdomain sudo[34793]: pam_unix(sudo:session): session opened for user root by root(uid=0)
May 03 12:28:32 localhost.localdomain sudo[34793]: pam_unix(sudo:session): session closed for user root
May 03 12:28:35 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:28:35 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 782.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:28:35 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:28:35 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:28:35 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:28:35 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:28:35 localhost.localdomain kill[34800]: kill: not enough arguments
May 03 12:28:35 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:28:35 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:28:46 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:28:46 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 783.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:28:46 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:28:46 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:28:46 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:28:46 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:28:46 localhost.localdomain kill[34807]: kill: not enough arguments
May 03 12:28:46 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:28:46 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:28:57 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:28:57 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 784.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:28:57 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:28:57 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:28:57 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:28:57 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:28:57 localhost.localdomain kill[34814]: kill: not enough arguments
May 03 12:28:57 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:28:57 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:29:08 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:29:08 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 785.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:29:08 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:29:08 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:29:08 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:29:08 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:29:09 localhost.localdomain kill[34821]: kill: not enough arguments
May 03 12:29:09 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:29:09 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:29:19 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:29:19 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 786.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:29:19 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:29:19 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:29:19 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:29:19 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:29:20 localhost.localdomain kill[34828]: kill: not enough arguments
May 03 12:29:20 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:29:20 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:29:30 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:29:30 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 787.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:29:30 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:29:30 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:29:30 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:29:30 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:29:31 localhost.localdomain kill[34835]: kill: not enough arguments
May 03 12:29:31 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:29:31 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:29:41 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:29:41 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 788.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:29:41 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:29:41 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:29:41 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:29:41 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:29:42 localhost.localdomain kill[34842]: kill: not enough arguments
May 03 12:29:42 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:29:42 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:29:52 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:29:52 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 789.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:29:52 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:29:52 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:29:52 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:29:52 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:29:53 localhost.localdomain kill[34849]: kill: not enough arguments
May 03 12:29:53 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:29:53 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.
May 03 12:30:03 localhost.localdomain systemd[1]: zabbix-server.service: Service RestartSec=10s expired, scheduling restart.
May 03 12:30:03 localhost.localdomain systemd[1]: zabbix-server.service: Scheduled restart job, restart counter is at 790.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Automatic restarting of the unit zabbix-server.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
May 03 12:30:03 localhost.localdomain systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
May 03 12:30:03 localhost.localdomain systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
May 03 12:30:03 localhost.localdomain systemd[1]: zabbix-server.service: Can't open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory
May 03 12:30:03 localhost.localdomain systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is done.
May 03 12:30:04 localhost.localdomain kill[34856]: kill: not enough arguments
May 03 12:30:04 localhost.localdomain systemd[1]: zabbix-server.service: Control process exited, code=exited status=1
May 03 12:30:04 localhost.localdomain systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit zabbix-server.service has entered the 'failed' state with result 'exit-code'.