This configuration (hardware and software) ran for many years without any issues. Other VMs on the systems show now problems.
Since a while (it could be about since updating to Roon 2) every few days I have Roon crashing randomly while playing music. It recovers itself without intervention within 2–3 minutes.
System log alway shows the same pattern (crash was at 09:42):
Jan 22 08:52:28 roon start.sh[1605390]: !!! XmlFetchError
Jan 22 08:52:28 roon start.sh[1605390]: XmlCheckRefreshCompleted - FAIL - 4c494e4e-0026-0f21-8174-01273949013f
Jan 22 09:42:56 roon start.sh[1526325]: 04 days, 01:08:12.369 Debug: RoonServer, after RoonAppliance exit, exitcode: 137
Jan 22 09:42:56 roon start.sh[1526325]: Error
Jan 22 09:42:56 roon start.sh[1526325]: Initializing
Jan 22 09:42:56 roon start.sh[1526325]: Not responding
Jan 22 09:42:56 roon start.sh[1526325]: 04 days, 01:08:15.450 Debug: RoonServer, before attempting to start RoonAppliance binary at path: /opt/RoonServer/Server/../Appliance/RoonAppliance
Jan 22 09:42:56 roon start.sh[1526325]: 04 days, 01:08:15.461 Debug: RoonServer, after starting RoonAppliance
Jan 22 09:42:56 roon start.sh[1526325]: Started
Jan 22 09:42:59 roon start.sh[1683318]: aac_fixed decoder found, checking libavcodec version...
Jan 22 09:42:59 roon start.sh[1683318]: has mp3float: 1, aac_fixed: 1
Jan 22 09:42:59 roon start.sh[1526325]: Running
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Jan 22 09:44:48 roon start.sh[1683318]: (trak) unknown chunk id: load
Sinces this was running rock-stable and self-updating over years before (kudos to your SW-engineers!), any help is appreciated.
Running Roon in a bHyve VM is not an officially supported environment. It is considered Tinkering. Roon does not stop users from using their software in unsupported environments which is great for the tinkerers among us; however, when you do so, you are also taking on the ongoing support for that environment.
I am moving this post to the Tinkering section so other users who may also be using your environment can help you with diagnosing and resolving your issue.
If this does not work for you, then I would recommend running Roon in an officially supported environment for the stability and support you are looking for.
eah, I was wondering if I should go up with this, too, but wanted to wait for a diagnosis before wasting RAM on things that may not need it…
I felt this was ok with the system requirements, since I don’t use any DSP and have one client only.
I would have expected some qualified feedback or error message on going out of memory though from a commercial software, instead of just dying quietly .
oh, that’s a little bit surprising for me .
I can remember there were constraints on operating systems and RAM/CPU for supported environments (which I followed both), but I can’t remember limitations on running in a virtual machine. Would you mind giving me a pointer where I can find them?
How would running inside a virtual environment vs. on physical iron make any difference to a proper software not directly accessing specific hardware devices?
But this is a regular Out-of-the-Box Ubuntu Base system, without any modifications.
I installed a regular Ubuntu from scratch, then installed Roon with the official Ubuntu package. Nothing else…
As a professional software engineer: I can’t see how this could make any difference to Roon? (We’re not talking about timing issues or the like…)
As a buyer: There was no limitation to physical hardware communicated. Your website said, it’s running on Ubuntu, without any limitations. When buying a proper, commercial software in 2023, not being supported in a VM is a heavy limitation of the usability one would expect to be communicated honestly.
Aside from “official” constraints, I’m honestly disappointed as a customer, how easily this is pushed away without any interest in a solution, despite the fact there is no evidence for any relevance of the hardware for that problem.
Yesterday, I already turned it up to 6G instead of the 4G before, if that doesn’t work, I’ll try the 8G.
So far, no crashes (but so far, no statistic significance )
.
.
)