I have a restic repo which stores log files of a system.
It is backed up hourly by cronjob and tagged with the date.
Since one day I get the error with every restic operation.
// ErrMaxKeysReached is returned when the maximum number of keys was checked and no key could be found.
ErrMaxKeysReached = errors.Fatal("maximum number of keys reached")
It looks like you have more than 20 keys in your repository. restic gave up after trying the first 20 ones (which probably already took at least 10 seconds). At that number of keys the recommended way is to tell restic which one to use by specifying a --key-hint <key-id> to use.