NUC 10
Intel(R) Core™ i7-10710U CPU @ 1.10GHz
32GB RAM
1TB 2.5" SSD for storage
512MB M.2 nVME for OS
Debian 11
Networking Gear & Setup Details
Ubiquiti swtiches and AP’s
Connected Audio Devices
N/A
Number of Tracks in Library
Very small
Description of Issue
Today, the Roon Core just became inaccessible and this is the first time (in a year or so) that this happened. The NUC is accessible through the network (it’s also a Plex server). When I do a systemctl status roonserver.service, I get this:
root@nuc:~# systemctl status roonserver.service
● roonserver.service - RoonServer
Loaded: loaded (/etc/systemd/system/roonserver.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2022-03-31 18:03:23 PST; 32min ago
Main PID: 6319 (start.sh)
Tasks: 64 (limit: 38122)
Memory: 10.0G
CPU: 1h 42min 31.387s
CGroup: /system.slice/roonserver.service
├─ 6319 /bin/bash /opt/RoonServer/start.sh
├─ 6323 /opt/RoonServer/RoonDotnet/RoonServer RoonServer.dll
├─11935 /opt/RoonServer/RoonDotnet/RoonAppliance RoonAppliance.dll -watchdogport=36295
└─11936 /opt/RoonServer/Server/processreaper 11935
Mar 31 18:35:26 nuc start.sh[6323]: Started
Mar 31 18:35:28 nuc start.sh[6323]: Not responding
Mar 31 18:35:44 nuc start.sh[6323]: 00:32:20.483 Debug: PathForResource, filename: ../.update
Mar 31 18:35:44 nuc start.sh[6323]: 00:32:20.483 Debug: PathForResource, candidate: /opt/RoonServer/Server/../.update
Mar 31 18:35:44 nuc start.sh[6323]: Error
Mar 31 18:35:46 nuc start.sh[6323]: 00:32:22.483 Debug: PathForResource, filename: ../Appliance/RoonAppliance
Mar 31 18:35:46 nuc start.sh[6323]: 00:32:22.483 Debug: PathForResource, candidate: /opt/RoonServer/Server/../Appliance/RoonAppliance
Mar 31 18:35:46 nuc start.sh[6323]: Initializing
Mar 31 18:35:46 nuc start.sh[6323]: Started
Mar 31 18:35:48 nuc start.sh[6323]: Not responding
So it looks like the service itself has a problem. My father is the actual user (through an iPad to control the Core), and I’m just the IT guy. He said an update happened yesterday and the server continued to work until earlier this morning. When he tried again tonight, it is no longer accessible.
I’m running Roon Server on Debian, albeit under BHYVE 1.0.
Normally after a successful update I need to manually restart the service with the following command,
sudo systemctl restart roonserver.service
For me this normally works.
Occasionally I have had to rerun the installer script then restart the service and just restore my database from the previous nights backup. (This I have only had to do once though)
Thanks for the reply. I already tried restarting the service and it just gives me the same error. At this point, do I need to just rerun the installer script? If I do that, will it necessary be a fresh install and you just restore the database from the backups you have? Also, don’t I need to uninstall first?
the installer script removes the necessary Roon files. It does not touch the actual local audio files but obviously you should manage any necessary backups for those separately. Then it is simply a matter of selecting the backup folder to restore from under settings.
Haven’t used roon on linux for a while but think it should be the RoonServer.txt file in the log folder, think it is in /var/roon/RoonServer or /opt/RoonServer/
Each time you restart the service it will archive the current log file and create a new one but tail -f should be ok with the rotating log as long as you use the non archive name.
Are you using this Debian install just for the Roon Server or is it part of wider services?
In my use case I have a Debian install running under BHYVE that is simply for Roon Server so ultimately its quite simple to just start over as all files and backups are on other devices etc.
My normal routine for applying any Roon updates to the core is as follows,
sudo apt update
sudo apt list --upgradable
Then I take a quick look at what’s being upgraded.
sudo apt upgrade
Once complete I then run the Roon updater from client.
If I run any issues that don’t seem to be resolved by a (which can happen)
The server has NUC and Plex on it and a couple of docker containers. I can take it down if necessary. I’m all for reinstalling and restoring from backups. I’ve done in, I think, once in the past but I’m not sure if I ran the uninstall script before the install script. I know you said the install script removes the necessary Roon files but does that mean it does exactly what the uninstall script does?
I did an apt update && apt upgrade, rebooted the NUC, reinstalled using the x64 install script and same thing (not responding). I tried using the uninstall script, rebooted, and reinstalled using the same script, and still the same thing. So there’s something going on that’s making the service not respond.
I already tried restarting the service earlier and it did nothing. I also don’t think rebooting any network device (ubiquiti switches, AP’s, and pfsense) would do anything. I can access the NUC just fine and I can access my Plex server that’s on the same device.
Ok, so it works now. What I needed to do was to delete /var/roon after running the uninstall script and before reinstalling. This was done because the database is in /var/roon and the uninstall script doesn’t touch that. After all these, I just restored from my last backup. Could the root cause probably be a corrupted database or something?
It’s far from unknown, there are also some cache and temp files in there that I sometimes delete if I feel Roon is sluggish and needs some shock treatment.
Would you run:
ls -l /opt/RoonServer/Server/…/.update
and give the output?
The path is odd.
Both errors introduce …/ into the path. I do not know why it would be explicitly called with:
/opt/RoonServer/Server/…/.update
vs
/opt/RoonServer/.update as is written above.