5004:20171102:203320.072 cannot connect to alert manager service: Cannot connect to service "alerter": [2] No such file or directory.
  5005:20171102:203320.076 cannot connect to alert manager service: Cannot connect to service "alerter": [2] No such file or directory.
  5006:20171102:203320.076 cannot connect to alert manager service: Cannot connect to service "alerter": [2] No such file or directory.
  4999:20171102:203320.077 One child process died (PID:5004,exitcode/signal:1). Exiting ...
  7327:20171102:203320.111 server #1277 started [poller #981]
  4999:20171102:203322.677 syncing history data...
  4999:20171102:203322.677 syncing history data done
  4999:20171102:203322.678 syncing trend data...
  4999:20171102:203322.678 syncing trend data done
  4999:20171102:203322.678 Zabbix Server stopped. Zabbix 3.4.3 (revision 73588)

root@zabbix:~# tail -f /var/log/zabbix/zabbix_agentd.log
 22352:20171102:202244.122 **************************
 22352:20171102:202244.122 using configuration file: /etc/zabbix/zabbix_agentd.conf
 22352:20171102:202244.122 agent #0 started [main process]
 22353:20171102:202244.123 agent #1 started [collector]
 22354:20171102:202244.123 agent #2 started [listener #1]
 22355:20171102:202244.127 agent #3 started [listener #2]
 22357:20171102:202244.127 agent #5 started [active checks #1]
 22356:20171102:202244.128 agent #4 started [listener #3]
 22357:20171102:202244.130 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [111] Connection refused)
 22357:20171102:203401.383 the system time has been pushed back, adjusting active check schedule