Mac Server or Roon app running core on a dedicated mac mini constantly crashing

Support
1

Roon Core Machine

Mac Mini M1 dedicated to the server task. Fresh build. No anti-malware or firewall.
macOS Ventura 13.3.1
8_GB RAM, 256_GB SSD
Streaming ONLY - no local library

Networking Gear & Setup Details

CenturyLink Gig Fiber to house
Asus RT-AX86S router
Mac Mini running Roon server connected via Ethernet directly to switch on router
No VPN

Connected Audio Devices

Primary endpoints:
iFi Zen Stream connected by ethernet (no wireless) to switch on router - same switch as Core Mac Mini
Chord Poly on wireless

Less frequent:
WiiM Mini via Airplay
Sonos system via Airplay

Number of Tracks in Library

Zero
streaming only - Qobuz

Description of Issue

Had the Roon Core running on Roon app on mini for almost a year and was stable. Recently it began crashing frequently. Found anecdotal reports that running Server on the mini might be better. Removed app, replaced with Server. Seemed a little better - no complete stops, BUT server now seems to stop and restart itself a couple times an hour. The controller - the Roon app on my work mac - would stop playing, and give the “looking for core” error. It would reconnect after 30 seconds or so. So I moved my playback control to an iPad - but same thing. The core is unstable.

I need to renew my subscription in a couple days. A few months ago I was considering a lifetime subscription, but at this point I’m thinking of not renewing AT ALL. Or at least going monthly for a minimal commitment because this thing is no longer working as advertised. And I’m not going to buy MORE equipment to run it. A dedicated Mac mini - clean install, no other function, should be fine.

And looking through the forums, I’m not the only one experiencing this kind of instability.

2

Hey @Eric_Olson1,

Thanks for taking the time to write in, and my apologies for the delay! Following up on this issue, do you receive a crash report from Apple when Roon crashes? If so, could you share a screenshot of it here? Or, copy and paste the crash report here - either will work.

With that, let’s see if a fresh database changes the behavior. Steps to follow below:

  • Create a Backup of your current database
  • Exit out of Roon
  • Navigate to your Roon Database Location
  • Find the folder that says “Roonserver”
  • Rename the “Roon” folder to “Roonserver_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the backup

Thanks!

5

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.