Replies: 1 comment
-
|
I thought i had fixed this but it looks like i hadnt. The repo is showing as locked again and the Doctor just runs without doing much. I have tried to go back to a previous version as i belive it stopped working following an update. I did find that i had to enter the secret as a variable in my Docker setup, i hadnt done this before and it was just in the software. Luckily i had saved it so think i have saved and entered the right string. Would it be possible to get some support on this? It is very likely a me issue and not an issue of software. Many thanks |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I have my S3 repo setup and its been working. An unexpected restart i belive has caused this error. Please could you support with the "unlock" command that i would need? not able to see how to list them in command line
{"message_type":"exit_error","code":11,"message":"unable to create lock in backend: repository is already locked by PID 273 on c9c29738a781 by root (UID 0, GID 0)\nlock was created at 2026-01-26 01:55:30 (227h26m26.547465447s ago)\nstorage ID 138d05b9\nthe
unlockcommand can be used to remove stale locks"}Many thanks
Beta Was this translation helpful? Give feedback.
All reactions