Hi,
It's normal; your package comes from SID and not Trixie.
First why do you have SID configured on your PVE (it should not, and can potentially break stuff, like that) ?
Second, you should use the Trixie version.
See :
Trixie ...
Not tried it by myself but CLI should work: https://forum.proxmox.com/threads/cluster-join-with-2fa-oath.44131/
There is no need to "remove" 2FA as there is an enable/disable checkbox. So you could temporarily disable root 2FA while joining that...
Not sure if this will solve the problem, but what I did is create a script using the System Daemon to automatically adjust the NIC settings I stated above when the server reboots.
I will monitor for a week and if no further crashes, will update here
Thanks, Lukas.
That sounds great. Let's see if I can pull it off with my rudimentary Linux skills.
At least I have a lab environment that I can easily rebuild without any issues.
What do you mean by “+ a USB-Drive as external datastore for...
Hi,
It's normal; your package comes from SID and not Trixie.
First why do you have SID configured on your PVE (it should not, and can potentially break stuff, like that) ?
Second, you should use the Trixie version.
See :
Trixie ...
I tried the browser my distro came with (Konqueror) and did not have an issue. In doing so I was reminded of a Vivaldi browser setting that I had recently changed. I found in the Vivaldi settings Privacy and Security section, under Website...
I am using Vivaldi. I saw some old stuff about a similar issue with Firefox. This just started very recently, I've never had a problem with Proxmox before. It did not seem to happen as a result of anything I have don't. I also keep having an...
And I came here after I installed PBS on top of an existing old-many-times-upgraded Debian install. The network interface wasn't initialised as it should. It turned out to be a different issue, but when I compared it to my new PBS install, I...
I updated Proxmox and kernel was updated `6.8.12-23-pve` => `6.8.12-29-pve` After reboot machine did not start fully, it ended up with repeating message each several seconds: WARNING: Pool 'rpool' has encountered an unrecorrectable I/O failure...
I was a little hasty and jumped to conclusions. In a nutshell I was correct about the nvidia drivers preventing the kernel upgrade. I simply had to uninstall the Nvidia driver, then the kernel upgrade proceeded without issue. I simply reinstalled...
AFAIK /etc/systemd/network/ is a good place for .link files - /etc/ really is the first place i would look for them.
(We've had it there since 7.x and still in 9.2; we pin manually with more insightful names than the pinning tool nowadays...
I came here to ask the question about whether there is a good reason that I shouldn't move my .link files to /etc/systemd/network (which is where the man pages seem to suggest they should be anyway) so I was pleased to find this thread at the top...
If you really have to create a container with lxc.* parameters via the API and your use case cannot be solved via the exposed parameters, then yes, cloning a prepared template is the only option I can think of.
you can set the environment with the `env` parameter and a PVE hookscript with the `hookscript` one (both are root only IIRC). arbitrary low level options are intentionally not exposed on the API.
Not via the API. The available phases in a hookscript are pre-start, post-start, pre-stop, and post-stop.
Depends on what your goal is. The env parameter sets the environment variables inside the container. They do not apply to hook scripts.