I'm able to start the service without errors but when I check status I see the below. I struggled with the ExecStart section of the script where the error is happening.
Error
jamulus.service-Jamulus-ServerLoaded:loaded(/etc/systemd/system/jamulus.service;disabled;vendorpreset:enabled)Active:activating(auto-restart)(Result:exit-code)sinceSat2020-04-0415:02:04UTC;7sagoProcess:1733ExecStart=/usr/local/bin/Jamulus-s-n#### Modify this for your circumstances #### (code=exited, status=203/EXEC)MainPID:1733(code=exited,status=203/EXEC)
Startup file - ExecStart section (nothing else touched in the script)
ExecStart=/usr/local/bin/Jamulus-s-n\
#### Modify this for your circumstances ####-o"yourServerName=YourMomsServer;yourCity=LaGrange;[country ID]=USA"
Any assitance appreciated!
Last edit: Snackmaster 2020-04-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I created an XML and it ended with the same 203/exec error.
Interstingly the Linux server tutorial had the Unit file ExecStart line completely updated after I posted. I tried the new code - same result. I'm good at 203/Exec errors :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
May be systemd didn't recognise your changes. Therefore please try the following:
"sudo systemctl disable jamulus.service"
then
"sudo systemctl stop jamulus.service"
then
"sudo systemctl daemon-reload"
then
"sudo systemctl enable jamulus.service"
then
"sudo systemctl start jamulus.service"
finally
Please post the output of
"sudo systemctl status jamulus.service"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've tried starting over from scratch twice (fresh donwload, install and config) , I've tried the setup pages updated config (Exec start line) and I've tried your XML config method - the run below I'm trying the install with a lower case J(amulus) in case that was an issue (all prior tests were upper case but I never see that in Unix). I often reboot to ensure a clean start when changing Jamulus settings (I normally do not set the Symlink per the setup guide so I have a clean start, I did for the steps above).
All tests land me squarely on "code=exited, status=203/EXEC". That error seems to cover a lot of ground, mostly permissions that I see. My perm's are 755.
Results from the above steps to fully turn off and enable Jamulus:
root@LaGrange1:~# sudo systemctl status jamulus.service
● jamulus.service - Jamulus-Server
Loaded: loaded (/etc/systemd/system/jamulus.service; enabled; vendor preset: enab
Active: activating (auto-restart) (Result: exit-code) since Sat 2020-04-25 12:26:
Process: 9992 ExecStart=/usr/local/bin/jamulus -s -i /usr/local/bin/jamulus/jamsrv
Main PID: 9992 (code=exited, status=203/EXEC)
Apr 25 12:26:26 EAM1 systemd[1]: jamulus.service: Main process exited, code=exited,
Apr 25 12:26:26 EAM1 systemd[1]: jamulus.service: Unit entered failed state.
Apr 25 12:26:26 EAM1 systemd[1]: jamulus.service: Failed with result 'exit-code'.
Thank you for the assistence!
Last edit: Snackmaster 2020-04-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, first of all thanks for the software, which is very nice and useful in these times. While in general I was able to experiment with different instances of servers without issues, the same as above to me happens when I try to set recording through the -R option (even chmod 777 on the recording directory). I also tried the above mentioned systemctl sequence without success. However, it runs well when I start the server directly with exactly the same options.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When following the guide here - https://github.com/corrados/jamulus/wiki/Server---Linux
For a Digital Ocean Ubuntu 16.04 VM - working to setup a private server.
Permissions appear okay?
/usr/local/bin/Jamulus = 755
/etc/systemd/system/jamulus.service = 644
I'm able to start the service without errors but when I check status I see the below. I struggled with the ExecStart section of the script where the error is happening.
Error
Startup file - ExecStart section (nothing else touched in the script)
Any assitance appreciated!
Last edit: Snackmaster 2020-04-04
Hi snackmaster,
ran into same problem. Try to create a XML-File like this:
<server>
<centralservaddr>jamulus.fischvolk.de</centralservaddr>
<defcentservaddr>1</defcentservaddr>
<servlistenabled>1</servlistenabled>
<name>YourServerName</name>
<city>YourCity</city>
<country>YourCountryID</country>
<autostartmin>1</autostartmin>
</server>
save it in same directory where Jamulus resides an name it like : jamsrvconf.xml
Now edit your jamulus.service file an replace your "ExecStart"-Statement like this:
ExecStart=/YourPathToJamulusSources/Jamulus -s -i /YourPathToJamulusXML-File/jamsrvconf.xml
Hope this will do it for you too.
Thanks jogi-baho,
I created an XML and it ended with the same 203/exec error.
Interstingly the Linux server tutorial had the Unit file ExecStart line completely updated after I posted. I tried the new code - same result. I'm good at 203/Exec errors :-)
May be systemd didn't recognise your changes. Therefore please try the following:
"sudo systemctl disable jamulus.service"
then
"sudo systemctl stop jamulus.service"
then
"sudo systemctl daemon-reload"
then
"sudo systemctl enable jamulus.service"
then
"sudo systemctl start jamulus.service"
finally
Please post the output of
"sudo systemctl status jamulus.service"
I've tried starting over from scratch twice (fresh donwload, install and config) , I've tried the setup pages updated config (Exec start line) and I've tried your XML config method - the run below I'm trying the install with a lower case J(amulus) in case that was an issue (all prior tests were upper case but I never see that in Unix). I often reboot to ensure a clean start when changing Jamulus settings (I normally do not set the Symlink per the setup guide so I have a clean start, I did for the steps above).
All tests land me squarely on "code=exited, status=203/EXEC". That error seems to cover a lot of ground, mostly permissions that I see. My perm's are 755.
Results from the above steps to fully turn off and enable Jamulus:
root@LaGrange1:~# sudo systemctl status jamulus.service
● jamulus.service - Jamulus-Server
Loaded: loaded (/etc/systemd/system/jamulus.service; enabled; vendor preset: enab
Active: activating (auto-restart) (Result: exit-code) since Sat 2020-04-25 12:26:
Process: 9992 ExecStart=/usr/local/bin/jamulus -s -i /usr/local/bin/jamulus/jamsrv
Main PID: 9992 (code=exited, status=203/EXEC)
Apr 25 12:26:26 EAM1 systemd[1]: jamulus.service: Main process exited, code=exited,
Apr 25 12:26:26 EAM1 systemd[1]: jamulus.service: Unit entered failed state.
Apr 25 12:26:26 EAM1 systemd[1]: jamulus.service: Failed with result 'exit-code'.
Thank you for the assistence!
Last edit: Snackmaster 2020-04-25
Hi, first of all thanks for the software, which is very nice and useful in these times. While in general I was able to experiment with different instances of servers without issues, the same as above to me happens when I try to set recording through the -R option (even chmod 777 on the recording directory). I also tried the above mentioned systemctl sequence without success. However, it runs well when I start the server directly with exactly the same options.