So we can better assist you, please describe your network configuration/topology, including any networking hardware currently in use, so we can have a clear understanding of how your devices are communicating.
When this behavior occurs are you able to access the Web UI?
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Time experienced: 01-April-2019, Time: 8.08 (CET)
It was running the night before. I have no information of when it stoped during the night.
It has never stopped, when in use.
kr
Now that I have the timestamps, diagnostics have been enabled on your account. The next time your Core is active a diagnostics report will automatically be generated and uploaded directly to our servers
Once that’s been received, I’ll be sure to update this thread and pass the diagnostics over to the team for further analysis.
Hi @dylan
Time: 7.40 CET 04-APR-2019, restart Roonserver.
However, this does not getting the Roon up and running.
Still returns “choose your Roon Core”
Roon Core seems not to be running. No update on the time running.
After a couple of minutes server states “not running”.
So server will only getting back in operation by reboot.
@dylan: Strange that issue now again occuried after four days: thursday morning (reported) and now monday morning. Next time maybe friday?
Could it be filled memory, or full log? Or a nice hidden setting in the NUC?
I just spoke with the team about this and they’ve requested that the next time this occurs, please let me know here without rebooting the machine. As the device is in this state we will enable some further diagnostics that should give us greater insight into this.
Thanks for letting us know! Diagnostics was enabled and our team took a look at the diagnostics report. They’re seeing some signs of networking issues in the report and were hoping that you could give something a try. Please reboot your router (but not the Core machine) and let us know when you’ve done so. I’ll enable diagnostics once more so the team can have another look at the report after this is done.