Any insight on how to fix this problem

[hbarker]

XeomaCoreService.service - XeomaCore
Loaded: loaded (/etc/systemd/system/XeomaCoreService.service; enabled)
Active: failed (Result: start-limit) since Thu 2017-02-02 08:27:36 MST; 2min 59s ago
Process: 1159 ExecStart=/root/bin/Xeoma/xeoma -service -startdelay 10 (code=exited, status=203/EXEC)
Main PID: 1159 (code=exited, status=203/EXEC)

Feb 02 08:27:36 BBXeoma systemd[1]: Unit XeomaCoreService.service entered failed state.
Feb 02 08:27:36 BBXeoma systemd[1]: XeomaCoreService.service holdoff time over, scheduling restart.
Feb 02 08:27:36 BBXeoma systemd[1]: Stopping XeomaCore...
Feb 02 08:27:36 BBXeoma systemd[1]: Starting XeomaCore...
Feb 02 08:27:36 BBXeoma systemd[1]: XeomaCoreService.service start request repeated too quickly, refusing to start.
Feb 02 08:27:36 BBXeoma systemd[1]: Failed to start XeomaCore.
Feb 02 08:27:36 BBXeoma systemd[1]: Unit XeomaCoreService.service entered failed state.

I have rebooted i've upgraded xeoma to the latest version. Not sure why it wont start. This is running on Linux Rasbian Jessie 4.4.34-v7+

[LuciusGrey]

XeomaCoreService.service - XeomaCore

I have rebooted i've upgraded xeoma to the . Not sure why it wont start. This is running on Linux Rasbian Jessie 4.4.34-v7+

Are you still getting this error hbarker?

[Admin_K]

XeomaCoreService.service - XeomaCore
Loaded: loaded (/etc/systemd/system/XeomaCoreService.service; enabled)
Active: failed (Result: start-limit) since Thu 2017-02-02 08:27:36 MST; 2min 59s ago
Process: 1159 ExecStart=/root/bin/Xeoma/xeoma -service -startdelay 10 (code=exited, status=203/EXEC)
Main PID: 1159 (code=exited, status=203/EXEC)

Feb 02 08:27:36 BBXeoma systemd[1]: Unit XeomaCoreService.service entered failed state.
Feb 02 08:27:36 BBXeoma systemd[1]: XeomaCoreService.service holdoff time over, scheduling restart.
Feb 02 08:27:36 BBXeoma systemd[1]: Stopping XeomaCore...
Feb 02 08:27:36 BBXeoma systemd[1]: Starting XeomaCore...
Feb 02 08:27:36 BBXeoma systemd[1]: XeomaCoreService.service start request repeated too quickly, refusing to start.
Feb 02 08:27:36 BBXeoma systemd[1]: Failed to start XeomaCore.
Feb 02 08:27:36 BBXeoma systemd[1]: Unit XeomaCoreService.service entered failed state.

I have rebooted i've upgraded xeoma to the latest version. Not sure why it wont start. This is running on Linux Rasbian Jessie 4.4.34-v7+

Hello!

What version of Xeoma do you use now? 16.12.26?

Please check each folder (etc/init.d, etc/init, /etc/systemd/system/ ), do you see autostart script in 1 or 2 folders?

What happens when you try using -core command? What way did you update Xeoma? Manually changed .app file or used Xeoma Client?