The information about the Roon Extension Manager is split between different threads because they discuss different parts of the project. Although it is useful to keep topics separated it also makes information a bit scattered.
To keep information up to date I always try to update the first post with current information, but on this forum this is a bit difficult because after a few months I can no longer edit the first post
To solve the above problems I now created a project entry point in the form of a project Wiki:
I made a start by adding some basic information and will add more detail to it as the project progresses. The different pages contain links to the applicable topics on this forum, in case things need discussion.
In case something specific needs more attention, please let me know.
Failed to start roon-extension-manager.service: Unit roon-extension-manager.service failed to load: Invalid argument. See system logs and âsystemctl status roon-extension-manager.serviceâ for details.
I check the service status and I get this
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:7] Assignment outside of section. Ignoring.
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:8] Assignment outside of section. Ignoring.
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:9] Assignment outside of section. Ignoring.
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:10] Assignment outside of section. Ignoring.
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:11] Assignment outside of section. Ignoring.
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:12] Assignment outside of section. Ignoring.
Sep 04 21:11:19 vortexbox systemd[1]: [/etc/systemd/system/roon-extension-manager.service:13] Assignment outside of section. Ignoring.
Warning: roon-extension-manager.service changed on disk. Run âsystemctl daemon-reloadâ to reload units.
I have seen this issue before when the systemd service file used DOS carriage returns. You may want to run dos2unix on the systemd service file before doing the systemd daemon-reloadâŚ
Command would be:
dos2unix /etc/systemd/system/roon-extension-manager.service
What encoding does the editor use, is it set to UTF-8?
Your case looks similar to this one.
I previously installed the service on my NUC, running Arch Linux. I now also installed it on my PC that runs Fedora 24. I had to add the PATH variable to the service file in order to get it working, it should be placed in the [Service] section:
I just cut and pasted those and it changed the case when doing this. I edited in Nano if I remember from when I did my own service t needed that entry to so Iâll add it in and see if it sorts it.
Maybe the copying from the webpage causes the issue. Please download the zip file and extract the service file from the linux\ directory. Then make the required modifications on this file.
Still struggling. Sorry Im not that experienced with linux. When you say the last part of the environment section needs to point to the node.js installation directory this is where I am lost. What node.js are you referring to?
Type âwhich nodeâ without the quotes. That will give you the full path to the Node JS executable.
To get the currently configured full path for a user, type âecho $PATHâ. The path listed in Janâs example file on the âEnvironmentâ line is a pretty standard one and should work.
And you really, REALLY should not be running node as root. It runs perfectly fine and is much safer as a standard, non-privileged user.
My extension requires version 6.x or higher because of some of the array types that are used. It may be confusing if the installation steps show v5.10.1 when there may be problems with some of the extensions with that versionâŚ
Sorted at last. For the record mike i have to run it as root as vortexbox runs as root from the outset. I never botheres to create another user as its too much hassle.
