3CX V15 on Linux Services not starting

[iqit]

When I reboot the VM the services does not start automatically.

Then when run /usr/sbin/3CXStartServices the following comes up:

root@3cx:~# /usr/sbin/3CXStartServices
Job for 3CXEventNotificationManager.service failed. See 'systemctl status 3CXEventNotificationManager.service' and 'journalctl -xn' for details.
Job for 3CXCfgServ01.service failed. See 'systemctl status 3CXCfgServ01.service' and 'journalctl -xn' for details.
A dependency job for 3CXPhoneSystem01.service failed. See 'journalctl -xn' for details.
A dependency job for 3CXIVR01.service failed. See 'journalctl -xn' for details.
A dependency job for 3CXPhoneSystemMC01.service failed. See 'journalctl -xn' for details.
Job for 3CXTunnel01.service failed. See 'systemctl status 3CXTunnel01.service' and 'journalctl -xn' for details.
Job for 3CXMediaServer.service failed. See 'systemctl status 3CXMediaServer.service' and 'journalctl -xn' for details.
A dependency job for 3CXQueueManager01.service failed. See 'journalctl -xn' for details.
A dependency job for 3CXSystemService01.service failed. See 'journalctl -xn' for details.
root@3cx:~#

Then when I run systemctl status 3CXEventNotificationManager.service

root@3cx:~# systemctl status 3CXEventNotificationManager.service
● 3CXEventNotificationManager.service - 3CX Event Notification Manager
Loaded: loaded (/lib/systemd/system/3CXEventNotificationManager.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-01-07 14:56:13 SAST; 1min 9s ago
Process: 624 ExecStopPost=/bin/rm -f /var/run/phonesystem/3CXEventNotificationManager.pid (code=exited, status=217/USER)
Process: 622 ExecStart=/usr/lib/3cxpbx/CloudServicesWatcher -p /var/run/phonesystem/3CXEventNotificationManager.pid -c /var/lib/3cxpbx/Bin/CloudServicesWatcher.exe.config (code=exited, status=217/USER)
Main PID: 622 (code=exited, status=217/USER)

Jan 07 14:56:13 3cx systemd[622]: Failed at step USER spawning /usr/lib/3cxpbx/CloudServicesWatcher: No such process
Jan 07 14:56:13 3cx systemd[1]: 3CXEventNotificationManager.service: main process exited, code=exited, status=217/USER
Jan 07 14:56:13 3cx systemd[624]: Failed at step USER spawning /bin/rm: No such process
Jan 07 14:56:13 3cx systemd[1]: 3CXEventNotificationManager.service: control process exited, code=exited status=217
Jan 07 14:56:13 3cx systemd[1]: Failed to start 3CX Event Notification Manager.
Jan 07 14:56:13 3cx systemd[1]: Unit 3CXEventNotificationManager.service entered failed state.
root@3cx:~#

and journalctl -xn

root@3cx:~# journalctl -xn
-- Logs begin at Sat 2017-01-07 14:54:05 SAST, end at Sat 2017-01-07 14:58:05 SAST. --
Jan 07 14:56:37 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:32:83:d8:65:45:2f:86:dd SRC=fe80:0000:0000:0000:3083:d8ff:fe65:452f DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=169 TC=0 HO
Jan 07 14:56:47 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:d4:ca:6d:2a:34:c5:86:dd SRC=fe80:0000:0000:0000:d6ca:6dff:fe2a:34c5 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=163 TC=0 HO
Jan 07 14:57:05 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:4c:5e:0c:54:aa:93:86:dd SRC=fe80:0000:0000:0000:4e5e:0cff:fe54:aa93 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=164 TC=0 HO
Jan 07 14:57:12 3cx xe-daemon[521]: Running CollectOS ...
Jan 07 14:57:12 3cx xe-daemon[521]: Running CollectMisc ...
Jan 07 14:57:12 3cx xe-daemon[521]: Running CollectNetworkAddr ...
Jan 07 14:57:12 3cx xe-daemon[521]: Running CollectDisk ...
Jan 07 14:57:37 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:32:83:d8:65:45:2f:86:dd SRC=fe80:0000:0000:0000:3083:d8ff:fe65:452f DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=169 TC=0 HO
Jan 07 14:57:47 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:d4:ca:6d:2a:34:c5:86:dd SRC=fe80:0000:0000:0000:d6ca:6dff:fe2a:34c5 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=163 TC=0 HO
Jan 07 14:58:05 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:4c:5e:0c:54:aa:93:86:dd SRC=fe80:0000:0000:0000:4e5e:0cff:fe54:aa93 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=164 TC=0 HO
lines 1-11/11 (END)

Do you know where I can start looking?

 

[iqit]

More info:
root@3cx:~# journalctl -xn
-- Logs begin at Sat 2017-01-07 14:54:05 SAST, end at Sat 2017-01-07 15:06:05 SAST. --
Jan 07 15:05:59 3cx systemd[1]: Dependency failed for 3CX PhoneSystem 01 System Server.
-- Subject: Unit 3CXSystemService01.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit 3CXSystemService01.service has failed.
--
-- The result is dependency.
Jan 07 15:05:59 3cx systemd[1]: Dependency failed for 3CX PhoneSystem 01 Management Console.
-- Subject: Unit 3CXPhoneSystemMC01.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit 3CXPhoneSystemMC01.service has failed.
--
-- The result is dependency.
Jan 07 15:05:59 3cx systemd[1]: Unit 3CXCfgServ01.service entered failed state.
Jan 07 15:05:59 3cx systemd[1]: 3CXMediaServer.service: control process exited, code=exited status=217
Jan 07 15:05:59 3cx systemd[1]: Failed to start 3CX PhoneSystem Media Server.
-- Subject: Unit 3CXMediaServer.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit 3CXMediaServer.service has failed.
--
-- The result is failed.
Jan 07 15:05:59 3cx systemd[1]: Unit 3CXMediaServer.service entered failed state.
Jan 07 15:06:05 3cx kernel: iptables[DOS]: IN=eth0 OUT= MAC=33:33:00:00:00:01:4c:5e:0c:54:aa:93:86:dd SRC=fe80:0000:0000:0000:4e5e:0cff:fe54:aa93 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=164 TC=0 HO
lines 1-29/29 (END)