In the last few day, my NUC was getting very warm where I posted it here and then had some off-line guidance from @Wade_Oram as my ticket timed out for further replies. I opened the NUC and cleaned it out as Wade advised, and it was less warm for a day or so.
I then began to experience some issues with TV:Remote and posted it here. While that was happening, my server was spinning and continued to do so for the bulk of the day, leading me to conclude that the issue is likely larger than the extension.
Thank you for reaching out. We’ve tried enable diagnostics for your account but it looks like logs are not coming through properly. Can we please ask that you use these instructions to manually access your ROCK logs, upload a set to the below link, and let us know once uploaded so that we can review them? Thanks!
A few new developments. The endless spinning is the Roon server on my Mac (I set it up a while back as a test but rarely use it). My Roon server was intermittently disconnecting, which is likely why you were unable to do the diagnostics. I discovered that as I saw ROCK was not connected to my network due to, in part, an overheating issue. I too was unable to access the logs as per the instructions In one case the NUC was very warm to the touch. Only after I disconnected the NUC from the power supply and let it cool down could I then access ROCK and download the logs for uploading to you.
Hi @David_Weinberg,
Thanks for getting those logs to us. While looking over the NUC logs that you sent the main issue I’m seeing is a lot of NetworkUnreachable traces as well as issues mounting folders from the NAS. I know you said that you noticed the lack of connectivity when the computer is overheating. Is that the only time that happens? Continuous scanning from the network issues could explain the spinning for six hours.
Thanks for the continued support. I *think I isolated the continuous scanning to my Mac as an unintended Roon server (but why is that machine scanning after many hours?? so maybe not). If that is true, then why would the NUC be so warm? Many questions.
Here is the latest from Saturday afternoon. This is with the Roon server on ROCK. Note the "Metadata Improver: Paused” comment:
I have documented my intermittent lack of connectivity here and here where I have developed less than elegant workarounds, but now I’m at a point where my Roon server is, at times, non-functional and hence my original ticket.
That is why I began to explore swapping out the NUC for the Nucleus One as I’ve already replaced my router and most peripherals. The one component I haven’t replaced is the NUC, so…
Update from Sunday late morning- ROCK is only slightly warm, close to what I would consider normal operations, and Roon ARC is working fine. So, some good signs Still, there has been some very inconsistent behavior over the last few weeks.
Reviewing a fresh diagnostic report from your Roon Server, we see some failures in regards to Tags that may be causing your system to continually attempt to process your library:
Info: [Broker:Media] GetOrCreateUserTag: there is an existing tag called
Do you use any third-party metadata editors to create and implement tags? If you create a fresh backup, and remove a handful of tags tied to larger amounts of tracks, how do things perform?
Thanks for determining a path forward. I use the Yate tag editor, and especially so for my box sets to segregate one or more discs in the box set as described here.
However, in that solution, I added the album title to the Roon Album Tag in Yate. Even though I’ve used this methodology for a few years, I have not seen box sets pop up in the Roon tags until a few months ago, and that was about the same time as my Roon server began to get a bit funky.
Following your guidance, I removed the Roon Album Tags from Yate, but still retained the Work and Part Fields:
Thanks for determining a path forward. I have used Yate tag editor, and especially so with my box sets to segregate one or more discs as described here.
However, in that solution, I unnecessarily added the album title to the Roon Album Tag in Yate. Even though I’ve used this methodology for a few years, I have not seen box sets pop up in the Roon tags until a few months ago.
Following your guidance, I removed the content from the Roon Album Tag field in Yate, but still retained the Work and Part Fields:
After a fresh review, it certainly looks more normal considering your library size. Do you find that you’re still running into the same performance issues?
I’m so pleased to report that Roon ROCK and my entire Roon experience is far better, so thank you for your guidance. My NUC is only a slight bit warm and Roon has been playing remarkably well.
The only legacy problem the persists is what I linked to in post #7 on April 5 (and linked here). I would love to have a fresh look at that item, but for now, this issue can be closed out.
My apologies in not re-opening this thread that you linked in your prior TS issue. The reason we haven’t reopened it is because it’s unfortunately still not something we support,that being RoonServer functionality on mobile devices.
I urge you to open a Feature Suggestions if you haven’t yet, as I’m sure it’s something many users would also be interested in!
Certainly let me know if there’s a different issue you’re referring to, and you can always create a new ticket that we’ll link to existing issues. Thanks for your understanding!
This is a longstanding issues. Mitch Duce at Chord once suggested that RoonServer functionality on mobile devices as a solution. Rolling back to the issue at hand- I get intermittent dropouts on my Roon-ready Chord Poly when using Roon ARC, making it less than satisfactory. My workaround- I play music from my SD card and play on Roon ARC (with the volume muted) at the same time so I have a log of what I’ve listened too and I get to enjoy the Roon ARC UI (it is quite nice : )
It would be also be nice if I could use Roon ARC on my Chord Poly. If that is in fact unsupported, then I’ll submit it as a feature suggestion.
Some have commented it could be a local network issue- but I’ve replaced my router a few times and cables, others that it’s the Poly, but that has been inspected and works as per the specs. So I’m at a holding pattern.