Recent content by zeus86

meanwhile the second instance finally also went through. as it can be seen from the screenshot, this instance had failure for longer in the past in total. once in a while a run finished fine (after putting in to a timeslot where nothing else was happening and rate-limiting api-requests), but...

One of my instances already finished. it actually took 3 attempts, because of failed to delete some objects (without further details) in step 2. However, I think the api-command to actually delete the object went through just fine anyways, because on subsequent tries the GC ran longer until it...

I'll test that, because my jobs are meanwhile failing since almost 2 weeks consecutively. GC is already currently running. I'll report back for my 2 instances, if this solved the problem. If this is confirmed to work, this might be worth reporting back to hetzner because they keep how2s for...

after some runs did complete meanwhile, today i had another error. as requested, here the full log (with redacted hostnames).

short update: i manually remove those backups from s3 where the verification fails (were some of the oldest anyways), and additionally temporarily adjusted the retention time, so that another 2 of the oldest backups (each) were removed. however, the GC error still occurs for me. on another...

currently i am running 4.2.0 still. full trail: proxmox-backup 4.2.0 running kernel: 7.0.0-3-pve proxmox-backup-server 4.2.5-1 running version: 4.2.0 proxmox-kernel-helper 9.2.0 proxmox-kernel-7.0...

did anyone found a real root cause for this? i currently have the exact same problem also on a hetzner s3 bucket, and i suspect some backups that did failed verification are the curlpit. for some reason, 3 older backups actually failed verification. all from the same day but from different...

I literally just signed up this forum to tell you, that this bug is still a thing with LXC-Containers on Proxmox 6.3-3, and your solution still works fine. Thank you very, very much for this. I cannot believe, why a bug like this is not fixed after 10(!!) Years, when the Solution has already...