Server is normally in append-only mode, when doing restic forget (on non-append-only), I got:
Fatal: unable to create lock in backend: repository is already locked by PID 19815 on backup by username (UID 1000, GID 1000) lock was created at 2020-04-13 23:00:02 (1438h10m34.797376502s ago)
The backup system does hourly backups with cron, some of them may have been interrupted by sleep/shutdowns.
Is there any way to prevent this from happening? Running
restic unlock sounds like avoiding locks (and creating a catastrophic situation), when
forget is running on cron.