· Hello, I'm using Roon Version 2.70 on Mac OS 15.7.8. When starting Roon, I occassionally, but not always get an error message, Fatal error could not create lock file. When I click the OK button, Roon will then start no problem. The only time this becomes an issue is when my Mac restarts after a power outage. I then can't use Arc until I get home and I'm able to clear the error message. I followed the advice in this post: https://community.roonlabs.com/t/fatal-error-could-not-create-required-lock-file-macos-13-4-1-investigating/248128 But it didn't make in difference. For now it seems like a low priority error as it's only occassional, but i thought you'd like the know about it. Thanks! Andy
Thanks for the report. Please let us know the exact local date and time when you notice the “Fatal error could not create lock file” message, and we’ll enable diagnostics on your account to check if the logs contain clues.
I don’t remember the exact date and time. I created the topic maybe 5 or 10 minutes after it occured if that’s any help. Which would have been about July 30th 7:45PM EST.
Thanks for the extra detail, and sorry this has dragged on. We pulled diagnostics from your account and went through the full log set (Roon, RoonServer, and RAATServer) end to end. We want to be upfront: we can’t find the fatal lock file dialog itself anywhere in there, and the evening around 7:45 PM looks completely clean and normal, a routine quit and relaunch, no errors.
What did stand out was a burst of startup activity earlier that same day, around 5:40 AM: RAATServer failed to connect once and restarted a couple of times in quick succession. That looks a lot more like “the Mac just came back up and everything is racing to start” than the calm evening window does.
Could you please confirm the time again, as precisely as you can? If it’s possible the error actually happened that morning rather than in the evening, that would help us line it up with what we’re seeing. Also, the next time this happens, please let us know the exact time as soon as you can, we’ll pull fresh diagnostics right after, and having both the old and new pull to compare against each other should help us actually catch the event this time.
One more thing that would help: if you check ~/Library/Logs/DiagnosticReports on the Mac around whichever timestamp turns out to be right, and there’s a crash report dated then, please send that over too, that’s not something our diagnostics pull captures.
Actually, yes, 5:40 AM would have been the time, I had just updated the Mac and then left for the day. I did not check back with the unit until after i returned from work later that day. The error would have occured at 5:40 AM, but I didn’t notice it until 7:45 PM.