I have an earlyaccess core running on my QNAP TS-873. Recently, I’ve been noticing sudden stopping of my music and all my devices on my system disconnecting. No errors, I just get this for a few mins:
The behavior is similar to this:
I haven’t made any changes to my system and the only other change to my network recently was adding a new unmanaged switch. However, this switch is not connected to my QNAP so I don’t see why this would be causing the issues.
I’ve noticed that the CPU activity on my QNAP is unusually high when these errors occur but then it goes back to normal eventually. I’m not sure why the activity is high because I’m not really running anything else on the NAS. Typically when Roon is running smoothly I see about 20-30% CPU usage. I have basically stopped all non-essential processes on the NAS.
If I stop Roon on the NAS and restart, it usually fixes the problem, but it takes several minutes each time and is time-consuming, when I want things to “just work”…
I should note that everything is wired. No wifi, and this affects all remote devices. I’m not sure what else to do at this point. For now, I will remove that new switch to see if that makes any difference…
Hi, @J_B, sorry for the late reply. Thank you for the description of your issue. Am I getting it right that you are not seeing neither network zones located on other machines nor local zones connected directly to your QNAP (if there are such)?
Also could you, please, confirm that the last time saw the issue happening was on May 13th at around 9am? I am asking because I’d like to request a diagnostics report and explore if there are any reports related with this timestamp.
I don’t have any local zones directly connected to the QNAP. But regardless, all zones disappear.
The last time I saw it happening was yesterday.
Lately, I’ve mainly been listening to a box set with over 200 CDs. I never really experienced problems until I started listening to that. Could that be a potential cause?
Thank you for the reply! Quick question, am I getting it right that the reboot is the only way to get out of this state for you or zones might come back on their own after some time?
They come back after a time most of the time, but the problem keeps happening. If I reboot, then there is a longer time period before it starts happening again.
So another update. I stopped listening to my Mozart complete works album (200 CDs, 241 hours) for awhile and the Core has been much more stable. Still sluggish and occasionally disconnects but when I tried to listen to Mozart again the same behavior occurred immediately and very frequently.
So I suspect this has something to do with the number of tracks? Or maybe something else related to the size of the album? Any thoughts?
Hi! Sorry for the delayed response here. When you say that you are listening to this large boxset, could you, please, elaborate how exactly does your listening procedure look like? Are you adding all the tracks in the Queue or are you doing something else?
Hi, no, I’m not adding all tracks to the queue as that isn’t a reliable way of play through all the tracks (hence my feature request here and to a lesser extent here). Also, the queue doesn’t show play counts so I have no way of pick-up where I left off.
I screen captured a typical procedure on what I more or less normally do to get going. The main thing is to get to the album itself so I can see the play counts. Because I restarted the Core just before doing the recording there are minimal delays (although still some) in actually playing the tracks. If you want, when the disconnection happens, I can make another recording.
Note that the music had suddenly stopped before I started taking the screen capture even though it still said it was playing. As you can see at the end of the video, I try to play again but it just loops that disconnection and “No audio devices found”. A restart of the Core fixes it.
Could part of the issue be that I have nearly 100,000 tracks in my library? I’m wondering if I should migrate to a ROCK, but I’d like to know before I invest the money and time to do so…
It just happened (this time listening to an album on Tidal), and I restarted the server. I’ve downloaded the logs and uploaded them per your instructions. I separated the Roon Server logs into two files because, for some reason, the zip file was over 100MB. But when I separated the logs the total came to only 14 MB, weird. Anyway, you should have them now, let me know if you need anything else. Thank you.
So, I just got back from two weeks of vacation. I updated Roon to its latest update and I still have the same issues. I will restart the Core server and it will likely fix it for awhile…
Alright, further update, I just migrated from my QNAP NAS to an Nuc i7 ROCK server (in the supported list). From the get-go I’ve had the same issues. So maybe the issue is just navigating huge multi-disc albums…?
Just found this thread, and this has happened to me maybe 2 or 3 times the past few months?
My Sonos devices remain in Roon, but all of my “local” devices won’t connect. This happened to me when listening on my phone last night (8/8) at around 11:30pm Pacific time. I was listening, and I was messing with EQ settings if it matters. Suddenly my phone’s audio didn’t show up in Roon anymore and I left it for the night.
Then woke up today, logged into my PC, and my PC didn’t appear as an audio device either. I had to restart the Roon Server (runniing on Synology), and now everything has come back.
So interesting development today. I was trying to listen an opera and it was stopping during every song and doing the same things as described in this thread (disconnecting etc.). I tried everything, rebooting my ROCK, rebooting my Endpoint (ropieee), closing and opening the Windows Remote but nothing was working.
Then I noticed a disk space warning which is sadly a common issue on this machine so I deleted a few files but not very many (<1GB) and I decided to reboot because some other programs were acting up too. When I booted up I had 14 gb free which was surprising that I got a low space warning because I only deleted a few hundred megs before rebooting.
Then I fired up the Roon Remote… … and it has been working flawlessly since!
So I know there is some cache that the Remote uses but maybe it was filling the harddrive with nearly 13 gb of data? Is that why I’ve been having these problems? Is it a caching issue on the Remote machine?
Unfortunately I didn’t check my harddisk space before rebooting to see a before/after picture of the drive space, but things are working much smoother now. So maybe it is the Remote that’s messing things up?? If not cache, something else?