forgetoption Could not parse config file!

[mluettermann]

Describe the bug
i am not able to create an backup with an simple autorestic.yml

my autorestic.yaml file
`version: 2

locations:
my-locations:
from: /data
to: hdd

backends:
hdd:
type: local
path: /backup`

Expected behavior
responce from the autoresctic check

'autorestic check
Using config: /root/.autorestic.yaml
Using lock: /root/.autorestic.lock.yml
Saved a backup copy of your file next to the original.
Initializing backend "hdd"...
Everything is fine.'

error output while autorestic backup -a

'autorestic backup -a
Using config: /root/.autorestic.yaml
1 error(s) decoding:

• 'locations[my-locations]' has invalid keys: forgetoption
  Could not parse config file!
  Using lock: /root/.autorestic.lock.yml'

why i get this responce ? has invalid keys: forgetoption Could not parse config file!

Environment

• OS: Ubuntu
• Version: 22.04
• autorestic version 1.7.7
• restic 0.15.2 compiled with go1.20.3 on linux/amd64

[dolgarev]

I have the same issue with Debian 12. Any news here?

[ts-mk]

The same happens to locations -> name -> copy which becomes copyoption.

[wutr]

#194

Manually remove the offending yaml key (forgetoption and maybe a few more) as a workaround.

[zkhan93]

#194

Manually remove the offending yaml key (forgetoption and maybe a few more) as a workaround.

I tried this, but the invalid keys re-appear.

UPDATE: I was missing env variables, after providing proper env it worked.

[mrkeypad]

UPDATE: I was missing env variables, after providing proper env it worked.

cant you please explain how did you do that? what is the correct env config? cant find anythig in docs :(

[zkhan93]

UPDATE: I was missing env variables, after providing proper env it worked.

cant you please explain how did you do that? what is the correct env config? cant find anythig in docs :(

correct config should look like this, once the config is correct, manually removing the offending keys in temporary yaml will work.

.autorestic.yaml

locations:
  ...

backends:
  bb-data
    type: b2
    path: '...'

.autorestic.env

AUTORESTIC_BB-DATA_RESTIC_PASSWORD=...
AUTORESTIC_BB-DATA_B2_ACCOUNT_ID=...
AUTORESTIC_BB-DATA_B2_ACCOUNT_KEY=...

when I was getting this error, .autorestic.env was not providing correct keys for bb-data backend.
reference doc

[cloudrck]

I'm seeing the same issue on Arch Linux and FreeBSD 14.

Using SFTP as only backend.

autorestic version 1.7.9

[nununo]

I too was having this issue. Thank you @zkhan93 for giving me the clue. Indeed, when I added the missing repository key everything started working fine.

Still, this issue should be corrected and a more adequate error raised.

[Kenya-West]

I have the same problem with restic REST backend:

First, it gets the error that is not detailed:

autorestic check -c /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.yaml -v

Using config:    /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.yaml
Using env:       /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.env
Using lock:      /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.lock.yml
Saved a backup copy of your file next to the original.
> Executing: /usr/local/bin/restic check
Initializing backend "somedest"...
> Executing: /usr/local/bin/restic init
Error: exit status 1

After that, I run this command again, and this time it explains the error:

autorestic check -c /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.yaml -v

Using config:    /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.yaml
Using env:       /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.env
1 error(s) decoding:

* 'locations[home_user]' has invalid keys: forgetoption
Could not parse config file!
Using lock:      /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.lock.yml

I remove forgetoption from generated config:

backends:
  ...
locations:
  home_user:
    from:
    - /home/kenyawest
    type: ""
    to:
    - somedest
    ...
    options:
      forget:
        forgetoption:
        - prune
        keep-last:
        - 10
-    forgetoption: ""
-    copyoption: {}

and then it returns back to error with exit code 1 (look for first code block), I do not event imagine how to solve it.

UPD:

Seems like it lost key or has wrong password if use custom command:

 $kenyawest: ~ ❯ sudo autorestic exec -c /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.yaml -av -- check
Using config:    /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.yaml
Using env:       /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.env
Using lock:      /home/kenyawest/backup-restic-node/autorestic/config/.autorestic.lock.yml


    Executing on "somedest"

> Executing: /usr/local/bin/restic check
using temporary cache in /tmp/restic-check-cache-375859033
create exclusive lock for repository
Fatal: wrong password or no key found

exit status 12

Error: 1 errors were found

But the key is present, and password is correct (I checked this in REST server by comparing password and bcrypt hash)

backends:
  somedest:
    type: rest
    path: http://sub.example.tld:22002/
    key: vErYmUcHlOnGkEyDoUbLeTrIpLeHaShEd
    requirekey: false
    env: {}
    rest:
      user: user
      password: password
    options: {}
locations:
  ...

I am very much lost right now...

UPD2: I managed to resolve that use case. Simply save the key somewhere, do not try to reconstruct it.