Index/19b6de8c23 does not exist after forget --prune

Getting Help
1

Hi,

SOLVED:

typo in chown -R www-data:www-data

after forget and/or prune or rebuild-index…

index/19b6de8c23 does not exist after forget --prune
steps to reproduce:

restic backup 2-3 times to have more then one backup for one day so we have something to forget.

restic forget --keep-daily 31 --keep-weekly 10 --keep-monthly 12 --keep-yearly 10 --prune

2 seconds after forget:
restic check => no errors

wait one minutes, check again =>
Load(<index/19b6de8c23>, 0, 0) returned error, retrying after 1.080381816s: <index/19b6de8c23> does not exist
(several identical lines)

restic rebuild-index
2 seconds after forget:
restic check => no errors

wait one minutes, check again => new/other index missing
Load(<index/b16897ca35>, 0, 0) returned error, retrying after 552.330144ms: <index/b16897ca35> does not exist
(several identical lines)

Our “special” setup:
debian 10 buster 64 bit (server and client) on proxmox 6 kvm virtualisation

server:
rest-server 0.10.0-dev compiled with go1.11.6 on linux/amd64
–append-only --private-repos --tls

so forget --prune can’t be done on the client
but on the server directly on the repo file-system (nfs-mounted from our qnap-nas)

on client and server:
restic 0.12.0 compiled with go1.15.8 on linux/amd64

2

SOLVED:

typo in chown -R www-data:www-data

after forget and/or prune or rebuild-index…

rest-server runs as www-data and we don’t want to have a possible shell for user www-data.
So we have to run forget and/or prune or rebuild-index as root
So the new index is owned by root and we should not have a typo in chown -R www-data:www-data :slight_smile:

1 Like
3

Thanks for the feedback! Glad you could figure it out!