Service fails with status=203/EXEC
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 test is run as the user relution in the installation directory, as the start script aborts when run as root:
cd /opt/relution
sudo -u relution JAVA_HOME=/usr bin/relution-foreground.sh
The exit code 203/EXEC means that systemd cannot execute the start script directly. A possible cause is an incorrect SELinux context, for example if the Relution directory was extracted outside of /opt and then moved. Missing execute permissions for the scripts in the bin directory are also possible.
Fix the cause
The SELinux context and the execute permissions can be corrected with the following commands:
sudo restorecon -Rv /opt/relution
sudo chmod 755 /opt/relution/bin/*.sh
The service is then started again with sudo systemctl restart relution.
Adjust the relution service file
Alternatively, the script can be started via Bash. For this purpose, a small adjustment is made in the relution.service unit file: In the line ExecStart of the file /etc/systemd/system/relution.service, /bin/bash is prepended.
ExecStart=/bin/bash /opt/relution/bin/relution-foreground.sh
Afterwards, systemd is reloaded and the service is restarted:
sudo systemctl daemon-reload
sudo systemctl restart relution
Other startup errors
If the start script itself aborts, the service does not end with 203/EXEC but with exit status 1. The cause is then shown in the journal, which can be displayed with journalctl -u relution, e.g. This script must not be run as root. when started as root, or a message about the Java version (Relution requires Java Version …).