Roon server on Debian stable

Roon Software Discussion Linux
1

On a

Linux fitpc3 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64 GNU/Linux

system, installation terminates without problems but I do get:

nicola@fitpc3:~$ sudo systemctl status roonserver.service
● roonserver.service - RoonServer
   Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-04-20 21:33:03 CEST; 7min ago
  Process: 1707 ExecStart=/opt/RoonServer/start.sh (code=exited, status=203/EXEC)
 Main PID: 1707 (code=exited, status=203/EXEC)

Apr 20 21:33:03 fitpc3 systemd[1]: Started RoonServer.
Apr 20 21:33:03 fitpc3 systemd[1]: roonserver.service: Main process exited, code=exited, status=203/EXEC
Apr 20 21:33:03 fitpc3 systemd[1]: roonserver.service: Unit entered failed state.
Apr 20 21:33:03 fitpc3 systemd[1]: roonserver.service: Failed with result 'exit-code'.
nicola@fitpc3:~$

any idea how to proceed? Thanks, Nicola

2

What does

/var/roon/RoonServer/Logs/RoonServer_log.txt

say?

3 
nicola@fitpc3:~$ ls -l /var/roon/RoonServer/Logs/RoonServer_log.txt
    ls: cannot access '/var/roon/RoonServer/Logs/RoonServer_log.txt': No such file or directory

nicola@fitpc3:~$ sudo updatedb
nicola@fitpc3:~$ sudo locate RoonServer_log.txt
nicola@fitpc3:~$
4

Ah… Debian… maybe that’s why. I have a CentOS here, and the Roon logs are in
/var/roon/RoonServer/Logs/
Does that path exist? Maybe see if Roon lives elsewhere? And locate the logs dir? And see what it writes when it starts up?

And there’s always asking @support what

roonserver.service: Main process exited, code=exited, status=203/EXEC

means.

5

203/EXEC failure

The error message (code=exited, status=203/EXEC) is often seen when the script itself or its interpreter cannot be executed.
It could have these reasons:

  • wrong path to script (e.g. /home/py/ReadPressure2AndPostToMqtt.py)
  • script not executable
  • no shebang (first line)
  • wrong path in shebang (e.g. /bin/python3)
  • internal files in your script might be missing access permissions.
1 Like
6

Thanks CRo and BlackJack! As it turns out, under Debian (4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64 GNU/Linux)

$ sudo ./roonserver-installer-linuxx64.sh

does not set the correct permissions/ownerships. One has to switch user to root and then just do

$ ./roonserver-installer-linuxx64.sh

Now the server starts fine.