Service does not start - Linux
On this page
Introduction
On Linux the Relution service cannot be started and via systemctl status relution
these errors are output
Apr 12 12:02:52 Relution systemd[1]: Started Relution Server.
Apr 12 12:02:52 Relution systemd[1]: relution.service: Main process exited, code=exited, status=203/EXEC
Apr 12 12:02:52 Relution systemd[1]: relution.service: Failed with result 'exit-code'.
Apr 12 12:02:52 Relution systemd[1]: relution.service: Service RestartSec=100ms expired, scheduling restart.
Apr 12 12:02:52 Relution systemd[1]: relution.service: Scheduled restart job, restart counter is at 1.
Apr 12 12:02:52 Relution systemd[1]: Stopped Relution Server
Relution can also be started normally via relution-foreground.sh
and works as usual.
The problem may be due to the fact that the bash
is not the default shell of the operating system.
Adjust the relution service file
For this purpose a small adjustment can be made in the Relution Services
file and the service should start again afterwards.
In the line ExecStart
of the file /etc/system/system/relution.service
/bin/bash
must be added. After that you can try to start the service again.