Hi Keith. How are you running n8n? Depending on where your data directory is hosted, if the db file can’t be locked exclusively for n8n, you can have problems like this, like in a 2 node setup if they are sharing the same data directory, or if its a docker volume without the right permissions configured.
Ahh, I see. I googled that error and I see other people have had similar issues in the past, even after restarting workspace. It is attributed to n8n being down, or overloaded.
I didn’t see any follow ups to those threads, so my guess is it is something temporary. Perhaps there’s a backup process running that locks the database, preventing access. Maybe it will be resolved by now, or soon. Good luck!
Hey man, looks like it resolved on its own, we did restart a couple of times, dont know if that triggered the fix, but looking good for now. Thanks for the help though!!