I have been kicked off Roon about five times in the past 24 hours. By “kicked out” I mean Roon stops playing, I have to turn off and my my server (a Innuous zenith se) and then put my username and password back in. It eventually works after rebooting but it’s frustrating. The only change I added is an Innuos Phoenix reclocker a few days ago. I just updated the firmware on the server. I reinstalled the Roon app on my PC and iPhone last week. It is not a network issue as internet and streaming services all work fine on the same PC. It’s a shame because my system sounds better than ever.
Anyway here’s my setup.
Ethernet to Innuos Zenith Se - Innuos Phoenix reclocker - chord m scaler - chord Dave (dac) - ATC speakers.
I am not averse to reinstalling Roon from scratch if needed - I have very few CDs ripped to my server and run mostly Tidal or Qobuz.
Yes and still with the same issue. I notice that it tends to lock up and reboot whenever I ask it to do something new. So if I play three or four songs a from one album it is fine, but if I then open up a new album in Tidal or Qobuz or look up a new artist, it then freezes. When it freezes (like when I press play on a song) the blue line on the bottom goes back and forth very quickly like its in a game of Pong.
At this point I need to know whether this is a hardware or software issue- is it the server or the software. Because I bought my server from Europe I want to do everything possible to make sure it’s a software issue first.
As far as exact times go, I can tell you I listened to an album for about 10 minutes last night at 8:00 pm before it stopped working. I rebooted the core ( Innuos zenith Se) and shortly thereafter it started working again before stopping about 10 minutes later. It then kicked me off altogether.
Behavior happens when I check either a new album or an album already stored in my library.
Unfortunately I can’t move my router because it is at the other end of the house and it is tethered to the cable modem and satellite. Again I don’t think it is related to a network issue - I can stream x box games onto the PC (which uses a lot more bandwidth than even high res audio) and it works fine.
I’ve enabled diagnostics mode on your Core and what this action does is automatically upload a log set to our servers for analysis.
I’m looking over the log report and I’m seeing a LevelDb.Exception: IO error: No space left on device error message. I believe you ran out of space on your Core’s /var/roon/RoonServer/ location, and it might have left your database in a weird state as Roon kept trying to write files to the database and was failing.
I would clean up some items from the Core - if you’re using the Core to store media, you should move the files over to another media location such as a NAS/external HDD and then setup a fresh database on the Innuous.
I am not certain how Innuous exposes their RoonServer web interface, but it would be a good idea to delete the current database and start with a new one. For specific instructions on this, you may want to reach out to Innuous directly, as I don’t see the Innuous site provide much instructions on this.
This is a question best proposed to Innuous support, as we don’t have any visibility into how Innuous hosts the database or instructions on their website on how to properly reset the Roon database. I would reach out to Innuous support and provide them this log snippet so they can investigate this issue further:
05/14 21:25:20 Critical: scx: LevelDb.Exception: IO error: /var/roon/RoonServer/Database/Core/5678722f137f4549a7d378af08946cac/broker_2.db/161039.ldb: No space left on device
at LevelDb.Database._CheckError (System.IntPtr err) [0x00037] in <373b5d36b2dd4f9c87e614fda690fbce>:0
at LevelDb.Database..ctor (System.String path) [0x00075] in <373b5d36b2dd4f9c87e614fda690fbce>:0
at Sooloos.Broker.Database..ctor (System.String dbdir) [0x0005b] in <beeb2a36840a4c619fcf8dbf08fbe6ee>:0
at Sooloos.Broker.State.NotifyIsLoggedIn (System.String userid) [0x0005d] in <beeb2a36840a4c619fcf8dbf08fbe6ee>:0
at Sooloos.Broker.Accounts._DataUpdated () [0x001d8] in <beeb2a36840a4c619fcf8dbf08fbe6ee>:0
at Sooloos.Broker.Accounts+<>c__DisplayClass66_1+<<_FinishLogin>b__1>d.MoveNext () [0x00253] in <beeb2a36840a4c619fcf8dbf08fbe6ee>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <370a0c27f4b74d1a81431037df6d75bf>:0
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_0 (System.Object state) [0x00000] in <370a0c27f4b74d1a81431037df6d75bf>:0
at Sooloos.SynchronizationContextThread._Dispatch (Sooloos.SynchronizationContextThread+SendOrPostWrapper& ret) [0x00012] in <4a12564dca88461fb02804cdf98a5a9c>:0
05/14 21:25:21 Info: [stats] 1915mb Virtual, 142mb Physical, 27mb Managed, 0 Handles, 28 Threads