Setup: Mac Pro (early 2008) running Roon Server (headless) v 1.4 . Build 298, 64bit.
All music is stored on local drives, but not the startup drive. Local collection is small (< 100 albums), but Tidal makes it over 1000.
Machine I’m controlling the above from is a Macbook Pro, and the autoupdate on that to 1.4 Build 300 worked fine.
Behavior: Watching via the “About” screen, Core says Checking for Update… Then Downloading Update 1.4 Build 300 (for about ~10 secs)… Then Installing update, but immediately errors out with “There was an error checking for an update.”
Steps I’ve taken:
Noticed this a few days ago, so I decided to let it go to see if it fixed itself. No luck.
Rebooted machine today. Same thing.
Overall, I’ve watched it check and error out about a dozen times.
I can post the logs when it finishes the download and starts the update, but don’t know if that’s cool to do…
Explanation for others who may have this issue in the future:
Awhile back, I switched the user account this machine auto-logs into. I wanted a “clean” user account.
So, only the original user that I had run/installed Roon with had Read/Write permissions on all the RoonServer package files. This meant the new user couldn’t update those files.
I had to go into the Package Contents of RoonServer and add the current user with Read/Write permissions, then “Apply to enclosed items.”
The logs are what tipped me off. Notice the two different users - roon and jtnt - and then “Permission denied.”