I am running restic 0.18 against a s3 backend. Since yesterday I can add / access the repo. The error is
Load(<lock/add9ae0157>, 0, 0) failed: The specified key does not exist
Is there any way I can fix the repo?
Regards
Hagen
This seems to be a lock file, should not be an issue. If you are not actively using it with multiple clients, this has to be a leftover.
Out of curiosity, is the s3 backend supplied by self-hosted Minio? Asking because I recently saw similar leftovers on it.
Anyway you should be able to remove the mentioned file manually on s3 side.
no, its a hosted offering from contabo
how can I find which file to remove?
you might need to set up a client tool like mc (if contabo gives any kind of user interface to reach you can also use it). The file is mentioned in the error: lock/add9ae0157 so check locks folder in the remote repo.
But, I was thinking where I was remembering a similar issue and found it: S3 and the name 'locks' so I suggest checking that out since it might be relevant.
1 Like
Use some S3 client to get a list of files in the locks folder. There should be some file with a name starting with add9ae0157. Try to download that file or just try to delete it manually. The expected result is that this also results in a The specified key does not exist error. If yes, please contact the hoster and ask them to fix the S3 bucket.
Is Contabo based on Ceph storage? If yes, it could be because of this bug:
We also suffer from this, overwrite/delete manually the lock is what we do as a workaround.
Hi, based on the other thread I canceled the service and contabo and moved on