mmclain-42

I do see this: zerobyte | info > Restic unlock succeeded for repository: s3:[removed].backblazeb2.com/[name] zerobyte | GET /api/v1/repositories/[name] 200 1ms zerobyte | GET /api/v1/repositories/[name] 200 0ms zerobyte | error >...

I just updated to v0.18.4 and get the same issue: zerobyte | GET /api/v1/repositories/[name] 200 1ms zerobyte | Restic unlock succeeded for repository: s3:s3.[host].backblazeb2.com/[name] zerobyte | error > Restic check...

@nicotsx no issues running it manually: using temporary cache in /tmp/restic-check-cache-1212121051 create exclusive lock for repository repository 0bff0405 opened (version 2, compression level auto) created new cache in /tmp/restic-check-cache-1212121051 load...

Same result using temporary cache in /var/lib/zerobyte/restic/cache/restic-check-cache-3237324344 create exclusive lock for repository repository 0bff0405 opened (version 2, compression level auto) created new cache in /var/lib/zerobyte/restic/cache/restic-check-cache-3237324344 load indexes [0:01] 100.00% 3...