Search results

I spent some hours debugging this issue, was getting crazy, and I solved it on my 3 nodes cluster this way: https://forum.proxmox.com/threads/cant-connect-to-destination-address-using-public-key-task-error-migration-aborted.42390/post-619486 Hope it doesn't trigger again.

Thanks for your post. It worked except for a GUI problem (connection error when managing other nodes), so I had to add a service restart. In case someone else has the same issue, I ran these commands on all my 3 nodes: cd /root/.ssh mv id_rsa id_rsa.old mv id_rsa.pub id_rsa.pub.old mv config...

No need to replace it, it's an env variable that contains the interface for the scripts in /etc/network/if-*.d Every time an interface comes up or goes down, scripts in those dirs are executed and that variable is set with the inteface name. So now I'm using this, and it works perfectly: auto...

You were right, it was the segment offload bug of the e1000 drivers. I used Thomas recommendation to disable it completely: https://forum.proxmox.com/threads/e1000e-reset-adapter-unexpectedly.87769/post-384609 auto lo iface lo inet loopback auto eno1 iface eno1 inet static address...

But I don't have any reset events for the NIC in dmesg log. Anyway, the offload issue seems plausible, it would explain the apparent randomness of the issue. There's also this post of Thomas to disable all offload...

Thomas, how is the $IFACE variable expanded? There's a post-up script that processes that line and has it defined? Thanks.

That's one of the old workarounds, it's not what I wanted to achieve. You need to check why on the other 2 dockers it worked with full ZFS and on this one it didn't.

You removed the whole folder with subfolders?? I think you screwed up docker installation. :) You had to only remove the driver from the json file, not the entire folder. I don't know how docker is starting without that folder.

looks like you have a driver configured, remove it. clean all the customizations you've done, docker installation has to be as clean as possible. If you can't do it, reinstall docker.

don't specify the driver (remove the daemon.json setting) and remove fuse=1. If you use the latest kernels docker should finally choose the overlay2 driver instead of the obsolete and inefficient vfs driver. I use privileged containers, you seem to use both privileged and unprivileged, you need...

I simply unrolled what I did following this guide: https://c-goes.github.io/posts/proxmox-lxc-docker-fuse-overlayfs/

Before 6.1, with the zfs LXC, the default storage driver would be the terrible vfs. So the only way was changing docker's config to use fuse-overlayfs. I installed 6.1, uninstalled fuse-overlayfs in the LXC, rebooted the pve node and then to my surprise in the LXC docker container I see this: ❯...

I upgraded my 2 PVE nodes to 6.1.10 and I noticed my docker v23 LXC with ZFS finally works with the overlay2 storage driver. No more fuse-overlayfs. Really nice. I wonder if someone could point me to what has changed at kernel level to finally allow support for this. Thanks in advance.

I had Docker v23 with 5.x Kernel, and it never worked, it always reverted to vfs so I used fuse-overlayfs. I upgraded PVE nodes kernel to 6.1.10 (it's opt-in for now), removed fuse-overlayfs, and after rebooting the nodes, the docker LXC container on ZFS finally showed the proper support for...

you think it might be something on the PVE side?

@Matthias. would be interesting to know which update addressed the issue. Where can I see a detail of the updates of proxmox backup client (maybe also the server)? I can't see a dropdown near the title nor the first post. Where is it? Maybe in the threads view?

@Matthias. just to let you know that I tried again today, all PVE nodes updated and PBS too, and it finally all backups completed without errors. :) Didn't change anything at hw level, I don't know which of the updates of last month did the trick, but it worked. Here's the current versions of...

This Intel NUC was previously a PVE node, but I converted it to PBS. Never had any hw issue. I switched cables, changed switch (I have 2 switches). No tx/rx errors on the switch ports. Tried a CAT6 (high quality) cable. That's why I'm frustrated...don't know what else I can try. The only...

Hi Matthias. I regenerated the keys as instructed. Removed datastore and backup job, recreated datastore and job, ran it manually and same issue. :( Since backups to Tuxis datastore are working fine, I thought the issue was the PBS installation, so I decided to reinstall PBS from scratch on the...

one other strange thing is that I have that backup scheduled, that gives errors, and another backup, the remote one, on Tuxis, and the remote one is perfect, never an error, and I backup everything like the local one with errors. does it give you some more info about what could the issue be?