Issue with systemd

[d11ahirst]

Hi,

I am having problems with the scheduling systemd timer,service

This is my profiles.toml

[default]
  initialize = true
  repository = "{{ .Env.RESTIC_REPOSITORY }}"
  password = "{{ .Env.RESTIC_PASSWORD }}"
  option = "s3.connections=3"

  [default.env]
    AWS_ACCESS_KEY_ID = "revoked"
    AWS_SECRET_ACCESS_KEY = "revoked"

  [default.backup]
    exclude = [ ...... ]
    exclude-caches = true
    one-file-system = true
    tag = [ "root" ]
    source = [ "/foldertobackup" ]
    schedule = ["hourly","daily"]
    schedule-permission = "system"
    schedule-priority = "background"
    schedule-lock-wait = "10m"
    schedule-log = "backup.log"

  [default.restore]
     target = "/"

  [default.retention]
    before-backup = false
    after-backup = true
    keep-hourly = 12
    keep-daily = 7
    keep-weekly = 1
    keep-tag = [ "manual", "locked" ]

I get the following output in the log

2023/05/23 09:50:18 INFO  profile 'default': initializing repository (if not existing)
reading repository password from stdin
2023/05/23 09:50:18 INFO  profile 'default': starting 'backup'
Fatal: unable to open config file: stat <no value>/config: no such file or directory
Is there a repository at the following location?
<no value>
2023/05/23 09:50:18 ERROR backup on profile 'default': exit status 1

Any help figuring this out would be appreciated.

[jkellerer]

There is no config option password (existing are password-file or password-command), however as you had set the PW in the env as RESTIC_PASSWORD it is forwarded to restic.

The problem with scheduling however is that it doesn't capture the environment used when scheduling a profile, therefore RESTIC_REPOSITORY is unset and leads to <no value>/config where no value stands for an empty RESTIC_REPOSITORY.

This is an issue that requires fixing (self note: capture all RESTIC_ env variables for scheduling).

The workaround would be to specify the 2 env variables in [default.env] (with actual values) or to set them in a way that they are available in systemd timers (which is probably not what you would want, as it could be read by anyone).

[d11ahirst]

Thanks for the reply,

What you suggested worked fine being able to read the env variables in schedules what be great.

[jkellerer]

Variable capture for schedules is coming in #212

[northben]

I just encountered this issue as well. I'm on version 0.24.0 and I can't find any way to get the scheduled backup job to read environment variables.