Inside RoonOS the Roon Server software is listed as not running but Roon is running correctly.
I have just updated ROCK on my NUC to 2.71, all went well but if you access the Roon console via Setup, find Roon core and then clicking on the ip address it shows Roon Server NOT RUNNING, however Roon runs just fine, not a problem as such but I though you might want to know?
R
Missed that, thanks.
After an automatic software update, I got the same, Nucleus One. My difference is I am also on EA RoonOS Version 3.0 (build 279). At first, Roon was working fine. But, about 20 minutes later, it wasn’t responding and the remote could not connect. I did a system reboot from this admin page, twice. Still same status and unresponsive Roon from a remote. I then did a hardware reset from the Nucleus One. Same status.
So, then I downloaded the BIN file, loaded it to the Reinstall folder and went through that process. Roon is working fine now and I can play, swap playlists and even endpoints from the remote. But the Admin page still shows Roon Server Software status as Not Running.
I’m just leaving it alone…music is more important than an incorrect status on the Admin page.
I had the same issue, went back to production which has exactly the same issue.
So dev has introduced a new bug which went straight to production release. Great work from the team 
Hi @Olaf_Jungen ,
Yes, I have notified support but having an official tech support request would help to bring this to their attention. See my PM to you.
Hi Carl, I have logged a support request af few minutes ago with them already.
Thank you, I see it …
So is this early access or production? Your support ticket doesn’t say
@Suedkiez Both production and EA have this issue with builds released today. It’s the same on my end with ROCK also on EA.
Hi @Suedkiez
@Olaf_Jungen’s ticket is for production, but it’s both …
Looks like Roon development slipped in additional fixes that were not previously tested on EA as this is only manifesting after today’s releases (prod and EA).
Fortunately from what I can determine it’s not affecting how Roon runs … but it is disconcerting.
Bad idea @Stephen 
I had not been paying attention too much between EA and Production, as I don’t swap back and forth too much, but has the Roon development team always used the next Build number available for the newest Production release? 2.71 (build 1680) Production but Early Access is on 2.71 (build 1679)? Strange to have EA behind Production on Builds?
Reboot your servers twice and see if it helps
Are you saying that doing so works for you and you don’t have it showing as Not Running?
I have soft and hard booted more than twice with no difference.
Rebooting does nothing. I have done a full wipe, installed from USB, updated to latest production, restored backup… exactly the same issue. Really bad practice to implement without testing first!
No, I run Roon Server on DietPi and don’t have an issue.
It’s likely an issue with Roon OS not allowing Roon Server to run. Likely a quick fix.