Dear Team,
I’m trying to use k8up, which is using Restic under the hood and am facing some problem when running the restic command:
2024-09-22T07:53:57Z INFO k8up.restic.restic.backup.command restic command {"path": "/usr/local/bin/restic", "args": ["backup", "--option", "", "--host", "core-vault", "--json", "/data/data-vault-0"]}
2024-09-22T07:53:57Z INFO k8up.restic.restic.backup.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666}
2024-09-22T07:53:58Z ERROR k8up.restic.restic.backup.progress /data/data-vault-0/auth during scan {"error": "error occurred during backup"}
github.com/k8up-io/k8up/v2/restic/logging.(*BackupOutputParser).out
/home/runner/work/k8up/k8up/restic/logging/logging.go:156
github.com/k8up-io/k8up/v2/restic/logging.writer.Write
/home/runner/work/k8up/k8up/restic/logging/logging.go:103
io.copyBuffer
/opt/hostedtoolcache/go/1.21.12/x64/src/io/io.go:432
io.Copy
/opt/hostedtoolcache/go/1.21.12/x64/src/io/io.go:389
os/exec.(*Cmd).writerDescriptor.func1
/opt/hostedtoolcache/go/1.21.12/x64/src/os/exec/exec.go:560
os/exec.(*Cmd).Start.func2
/opt/hostedtoolcache/go/1.21.12/x64/src/os/exec/exec.go:717
2024-09-22T07:53:58Z ERROR k8up.restic.restic.backup.progress /data/data-vault-0/core during scan {"error": "error occurred during backup"}
github.com/k8up-io/k8up/v2/restic/logging.(*BackupOutputParser).out
/home/runner/work/k8up/k8up/restic/logging/logging.go:156
github.com/k8up-io/k8up/v2/restic/logging.writer.Write
/home/runner/work/k8up/k8up/restic/logging/logging.go:103
io.copyBuffer
/opt/hostedtoolcache/go/1.21.12/x64/src/io/io.go:432
io.Copy
/opt/hostedtoolcache/go/1.21.12/x64/src/io/io.go:389
os/exec.(*Cmd).writerDescriptor.func1
/opt/hostedtoolcache/go/1.21.12/x64/src/os/exec/exec.go:560
os/exec.(*Cmd).Start.func2
/opt/hostedtoolcache/go/1.21.12/x64/src/os/exec/exec.go:717
2024-09-22T07:53:58Z ERROR k8up.restic.restic.backup.progress /data/data-vault-0/logical during scan {"error": "error occurred during backup"}
github.com/k8up-io/k8up/v2/restic/logging.(*BackupOutputParser).out
/home/runner/work/k8up/k8up/restic/logging/logging.go:156
github.com/k8up-io/k8up/v2/restic/logging.writer.Write
/home/runner/work/k8up/k8up/restic/logging/logging.go:103
io.copyBuffer
/opt/hostedtoolcache/go/1.21.12/x64/src/io/io.go:432
io.Copy
/opt/hostedtoolcache/go/1.21.12/x64/src/io/io.go:389
os/exec.(*Cmd).writerDescriptor.func1
/opt/hostedtoolcache/go/1.21.12/x64/src/os/exec/exec.go:560
os/exec.(*Cmd).Start.func2
/opt/hostedtoolcache/go/1.21.12/x64/src/os/exec/exec.go:717
So you can see the restic command being executed in the first line: /usr/local/bin/restic backup --option --host core-vault --json /data/data-vault-0. It does find the folders on the mounted volume, but is throwing the error message {"error": "error occurred during backup"} during every single one of them.
The restic repo is created correctly, including a snapshot, it just contains no data at all.
Environment variables:
RESTIC_REPOSITORY=azure:core-vault:/
RESTIC_PASSWORD=secret
AZURE_ACCOUNT_KEY=secret
AZURE_ACCOUNT_NAME=secret
Any ideas how to get more information about the failure? It seems to be restic JSON output (called with the --json flag, it’s not really helpful though. The remaining log lines are probably less interesting, as they only contain the repo init which was successful:
2024-09-22T07:53:51Z INFO k8up.restic initializing
2024-09-22T07:53:51Z INFO k8up.restic setting up a signal handler
2024-09-22T07:53:51Z INFO k8up.restic.restic using the following restic options {"options": [""]}
2024-09-22T07:53:51Z INFO k8up.restic.restic.RepoInit.command restic command {"path": "/usr/local/bin/restic", "args": ["init", "--option", ""]}
2024-09-22T07:53:51Z INFO k8up.restic.restic.RepoInit.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666}
2024-09-22T07:53:55Z INFO k8up.restic.restic.RepoInit.restic.stdout created restic repository e9b9a6898b at azure:core-vault:/
2024-09-22T07:53:55Z INFO k8up.restic.restic.RepoInit.restic.stdout
2024-09-22T07:53:55Z INFO k8up.restic.restic.RepoInit.restic.stdout Please note that knowledge of your password is required to access
2024-09-22T07:53:55Z INFO k8up.restic.restic.RepoInit.restic.stdout the repository. Losing your password means that your data is
2024-09-22T07:53:55Z INFO k8up.restic.restic.RepoInit.restic.stdout irrecoverably lost.
2024-09-22T07:53:55Z INFO k8up.restic.restic.unlock unlocking repository {"all": false}
2024-09-22T07:53:55Z INFO k8up.restic.restic.unlock.command restic command {"path": "/usr/local/bin/restic", "args": ["unlock", "--option", ""]}
2024-09-22T07:53:55Z INFO k8up.restic.restic.unlock.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666}
2024-09-22T07:53:56Z INFO k8up.restic.restic.snapshots getting list of snapshots
2024-09-22T07:53:56Z INFO k8up.restic.restic.snapshots.command restic command {"path": "/usr/local/bin/restic", "args": ["snapshots", "--option", "", "--json"]}
2024-09-22T07:53:56Z INFO k8up.restic.restic.snapshots.command Defining RESTIC_PROGRESS_FPS {"frequency": 0.016666666666666666}
2024-09-22T07:53:57Z INFO k8up.restic.k8sClient listing all pods {"annotation": "k8up.io/backupcommand", "namespace": "core-vault"}
2024-09-22T07:53:57Z INFO k8up.restic backups of annotated jobs have finished successfully
2024-09-22T07:53:57Z INFO k8up.restic.restic.backup starting backup
2024-09-22T07:53:57Z INFO k8up.restic.restic.backup starting backup for folder {"foldername": "data-vault-0"}
Any help would be much appreciated.