I have an Unraid-Server running at home and I thought it would be a good idea to let the machine handle Roon as well.
It is an Intel NUC with an Intel® Core™ i7-7567U CPU @ 3.50GHz and I have less than 3.000 albums inc. streaming. Load does not seem to be a problem and Roon initially runs quickly and effortlessly. I can load all my albums and restore my old backups from my ROCK and everything runs very well.
So what’s the problem?
When I restart the Unraid server and I try to start Roon again, it gets stuck in an endless restarting-loop and it just does not come out of it.
Deleting the Roon container and all related add-files and reinstalling everything brings it back to normal, but that is not a real solution …
Does anyone here have an idea, what could be the cause of this behavior?
Although new to Docker (actally Podman), I’d guess that the restart loop is caused by --restart=unless-stopped. Therefore, the question you need to answer, is why is Roon crashing. The logs may provide some insight.
So I will try to find something in the logs - which in my case also means “find the logs first” …
I am really new to the whole topic and I need to learn a lot!
Luckily Roon runs fine unless I restart the server so the problem is something I can take my time with.
Thanks for your input!
There seem to be more things wrong than I thought - the logs show this for the night:
Initializing
Started
Running
00:00:00.000 Info: get lock file path: /tmp/.rnsgem0-
00:00:00.004 Info: GetLockFile, fd: 34
00:00:00.004 Info: GetLockFile, res: 0
00:00:00.004 Trace: Nope, we are the only one running
Initializing
Started
Running
System.Net.Sockets.SocketException (104): Connection reset by peer
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Threading.Tasks.ValueTask`1.ValueTaskSourceAsTask.<>c.<.cctor>b__4_0(Object state)
— End of stack trace from previous location —
at System.Threading.Tasks.TaskToApm.End[TResult](IAsyncResult asyncResult)
at Sooloos.RnetJsonClient.<>c__DisplayClass65_0.<_BeginRead>b__0(IAsyncResult ar)
This happened during a time when nobody was accessing Roon.
Now, in the morning, Roon opens on my clients with
“There was an issue loading your library”