Restic unlock on wasabi giving fatal error

Getting Help
1

Hi I have a couple of repositories on wasabi. One of them keeps reporting a VERY STALE lock.

Here’s the lock message :

unable to create lock in backend: repository is already locked by PID 13736 on 127.0.0.1purvez-Aspire-5750 by root (UID 0, GID 0)
lock was created at 2023-03-02 20:10:05 (26634h32m44.02637519s ago)
storage ID d47ebaf9
the unlock command can be used to remove stale locks

I use the following backup command in a larger shell file :

${rhome}restic backup -v -v --tag pdacer --exclude-file=${rbkup}rfilesexclude --files-from ${rbkup}rfilesfrom --repository-file $rrepo --password-file ${rbkup}rchuparustom >>./logs/bkup_$today.log 2>>./logs/bkuperr_$today.log

The above command works fine. So I thought I’d cd into $rhome and then run the following command to clear the lock:

./restic unlock --repository-file ./rrepofile --password-file ./rchuparustom

However after ‘thinking’ about it for a while it comes back with :

Fatal: unable to open config file: Stat: Access Denied.
Is there a repository at the following location?
s3:s3.eu-central-1.wasabisys.com/pdacer

my rrepofile contains the following one liner:

s3:s3.eu-central-1.wasabisys.com/pdacer

What am I doing wrong please?

2

Apologies, my mistake. My backup shell file had a number of other parameters like Access Keys which had already been ‘exported’ and therefore the above backup command worked. I created a similar file with the unlock command and that says ‘successfully removed locks’.

Haven’t tried it yet but hopefully this should have worked.

Sorry again.

3

Hey at least you came back and explained the problem. Nothing more annoying than a “Oh I fixed it” reply on a forum post with no clue what the fix was!

4

Hehehe Yes I know what you mean. Totally useless for even the next person trying to find an answer. Thanks for the support.