Running Mac Mini 2012 Catalina as dedicated server. Remotes on a Mac Pro running Monterey, iPhone 13 Pro iOS 17.5
After the issue being hotfixed regarding the watched files with build 1445, I'm still having an underlying problem which occured on build 1432 as well.
It seems to be that Roon Server, after the update, is acting like a ghost instance. It says it's running, but when I want to connect, it tells me, I'm already running another instance. The weird thing is this happens while it does recognize my server as being the host.
Last time it was fixed by de-authorizing + authorizing. But this made me lose all my downloads on ARC. If this is the only solution, I'd be happy to know if there is a way to keep my ARC downloads (over 150GB). As this was rather annoying to have to re-do.
Describe your network setup
Fritzbox 10 modem, 4 airplay endpoints which can be found and used
Sorry to hear about your issue with Roon and your Mac Mini!
I see a few different Mac devices within your account information, did you by chance use TimeMachine across multiple Mac devices? Is your Mac Mini a duplicate database from your other Mac device? It could be the case that Roon is getting confused if the two devices are sharing the same Machine ID.
While we continue to improve Arc downloads, I’ve found it useful to add all my downloaded Arc tracks into its own playlist - and if I ever need to remove and reinstall Arc, I can simply tap the download button on the playlist to easily redownload my tracks. It’s not a solution by any means but an easy enough workaround for the time being!
Could you reproduce this and share the specific date and time?
Sorry for the delayed response, as I’ve been away a few days.
The mac isn’t running another copy of my regular working mac. I access all folders through my network, and can log into that device as being a fully solo device.
Adding to that, the issue just appeared again, while I have disabled all automatic updates as that did seem to be a problem.
Later today I can try again from my main computer and send over the logs + attempt timestamps.
Just updating here as I’ve just sent over the logs.
The odd thing is that I didn’t even update anything as automatic updates were turned off after last issue.
Reproduction was from 19-08, timestamp about 1h-30 minutes before upload.
Thanks for getting back to me!
I’ve just rebuilt the database according to your instructions. If the problem occurs again, I’ll keep you posted. For now it seems to work without having to restore the backup.
As I’m going on holiday tomorrow and have automatic backups scheduled every 4 days with a max. of 10. Is it wise to keep this enabled? Or save the one I made this morning, before doing these steps, in a different location?