Search results

Could this become some advanced option in GUI when restoring CTs? It is annoying having to find out what is the right command full command to run and default debian lxc images have postfix installed with creates 'random' file nodes in /var/spool with make restores fail.

If I set my backup to "PBS change detection mode: Metadata" each backup produces "TASK ERROR: connection error: not connected on Metadata". Sample log below: ``` 2025-11-24T08:35:02+00:00: starting new backup reader datastore 'backup': "/mnt/backup" 2025-11-24T08:35:02+00:00: protocol upgrade...

Here is my full log. In terms what I found on hetzner s3 This is some chunk that was marked corrupted too and it is on my hetzner storage.

I am on 4.0.15, as far I see they isn't a new update in repos.

Just got a bunch off: ``` 2025-10-02T07:16:30+00:00: chunk 609608675341b0b043b3accb719ab25d5d7a5c7979b72748dc82a7c5f25e7d2d was marked as corrupt 2025-10-02T07:22:13+00:00: <?xml version="1.0" encoding="UTF-8"?> <Error> <Code>GatewayTimeout</Code> <Message>The server did not respond in...

2025-08-14T06:13:04+00:00: verify backblaze:ct/103/2025-04-20T08:28:37Z 2025-08-14T06:13:04+00:00: check pct.conf.blob 2025-08-14T06:13:04+00:00: check root.ppxar.didx 2025-08-14T06:16:48+00:00: "can't verify chunk, load failed - client error (SendRequest)" 2025-08-14T06:16:50+00:00...

Yes, looks like an error returned from backblaze. But in that case stopping the task and starting again shouldn't clear that?

No I am pretty sure I am not hitting any tier limits, as I do pay for it and after restarting the job it now is at ~18h and still running fine. I found that in journal: Aug 06 18:15:38 pbs proxmox-backup-proxy[213]: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>...

After sometime running well a sync job to a s3 backblaze datastore it started to error out and doesn't seam to recover. Does it have already some re-connection/retry logic? My upload speed is fairly slow so such a job takes a lot of time. This one was running already for 3 hours and then stopped...

Exactly what I am thinking too! Sure, add it here https://bugzilla.proxmox.com/show_bug.cgi?id=6633 Thanks!

Thanks! Yeah, now it works. BTW. I suspect that is currently out of your scope but did you consider adding encrypted datastores? Especially for S3 that would be really helpful to have some way to encrypt a whole store with a user provided password. Doing encrypted backups by itself is not that...

Any one could provide how should the S3 Endpoint config look like for backblaze? I tried putting s3 endpoint as: s3.us-west-000.backblazeb2.com and backblazeb2.com and setting the region to us-west-000 Also tested s3.{{region}}.backblazeb2.com and all ends up with "405 Method Not Allowed" I...

Hi! I am trying to setup multiple IP address on a bridge and routing ports from them to specific internal IPs. That setup works fine with my MAIN public ip address, but not at all with EXTRA and I am out of ideas why. Here is my network setup file: auto lo iface lo inet loopback iface...

Thanks! That works for us, appreciate the quick answer.

Hi! I do currently have two servers in my network, one running Proxmox Backup Server 1.1-1 and one Proxmox VE 6.0 with works fine. Because the VE 6.0 is on a remote server updating/installing 8.0 will be slight problematic so I avoid that for now (please don't judge ). Now I am adding a new...

Hi! I just found an issue with tmpfs in my LXC containers. Example, I have a container with have assigned 4GB RAM but tmpfs shows 32GB with is half of the host memory: df -h Filesystem Size Used Avail Use% Mounted on udev 32G 0 32G 0% /dev/tty tmpfs...

Hmm... That worked: 1. In /etc/fstab on the host system /etc/pve/nodes/ocs /certs fuse.bindfs perms=0000:u+rD,uid-offset=100000,gid-offset=100000 0 0 And then just: pct set 103 -mp0 /certs,mp=/certs And it works :D, looks like a hack but I am happy with that solution :). BTW I am not sure how...

I tried already: lxc.mount.entry: /etc/pve/nodes/ocs certs fuse.bindfs perms=0000:u+rD,uid-offset=100000,gid-offset=100000 0 0 But that just fails when the CT is started: () __safe_mount_beneath_at: 1106 Function not implemented - Failed to open 51(dev) safe_mount: 1204 Invalid argument -...

I found that post about using bindfs for sharing files into CT https://forum.proxmox.com/threads/lxc-user-mappings.75450/ It seams like much easier thing that using mp0 and setting up uid/gid map (I couldn't get it done). So I add into fstab on the host system: /etc/pve/nodes/ocs...

nice, thanks. I will test that. Looks like it will help a lot.