Installier dir mal die inotify tools mit "apt install inotify-tools" und dann schau mir "inotifywait -mr /zPool/postgres" was da so passiert. Inotify zeigt dir alle Dateisystem actions an.
And today this issue is back, i took a quick look into pveproxy/access.log. I can see there is a callback which starts with ?code=... and a long string which is about 1066 bytes long, followed by some more stuff like state=, session_state= and so on. Maybe the issue is that code= is over 1024...
ah yes, and i fixed it. Error on my side. i reconfigured it and used key id and not secret for the secret. It works now.
Thank you.
Ps. Works on both, PVE and PBS.
Hi Mira,
i just installed this version on one of my non-subscription hosts, i restarted pvepoxy (dont know if required) but AzureAD still fails with 401. Autocreate is on so this should work.
--2022-04-20 11:24:24--...
Patch suffix looks like rust, i think without a full pve development environment we cant to anything with that diff by ourself because rust stuff has to be compiled.
I am sure that the Debian version under PVE 5.x is no longer supported. If your environment is not 100% air gapped, then this is a very bad security practice.
I would recommend using a single 10g, less power usage and a single connection can use as much bandwith this physical connection provide. In my home setup i have two Proxmox hosts and one OPNsense Firewall connected via 10g, i do a cross backup between these two hosts where 10g helps a lot.
As...
I setup my new network today and i wanted to use vxlan at home to learn more about vxlan and Proxmox using SDN.
So i got a new switch and rebuild my network today, my configuration looks like this:
Aruba 2930F, default VLAN is jumbo with and mtu of 1550 and max-frame-size of 1568
Proxmox 7.0...
My old Proxmox installation had HDDs for Data and two 850 Pro in a mirror for two Windows 10 VMs, these SSD wearout quiete quickly, on died after just 10 month due to wearout and had no more spare blocks to compensate.
My new Proxmox hosts is based on 4x Intel D3-S4510 3.84TB in a ZFS Strip...
Hi,
good idea, but i tried a different approach, i installed a debian bullseye container and tried to use the approach from the proxmox developer docs, i failed because there are a lots of dependencies that are not native debian packages and only exist for amd64...
Hello,
today i got one of the Oracles always free Ampere A1 ARM instance and thought it would be a good idea to backup content to my proxmox backup server, sadly it looks like there is no arm64 build of the Proxmox backup client.
Skipping acquire of configured file 'main/binary-arm64/Packages'...
Windows Server 2022 requires Secure Boot with TPM 2.0. VMware has TPM for quite some time. oVirt added TPM 2.0 with Version 4.4.6 and so does RHEV. I hope we see TPM support soon. Customers Buying Windows Server 2022 without Assurance has no way to run it on Proxmox because they have no...
Oracle ist ja schon seit 2006 dabei und lxc container gab es irgendwann mit version 7, eigentlich wundert es mich da so wenige die Dist auf dem Schirm haben. Schnellere point releases im Vergleich zu CentOS, vollen Errata Support im Repo. Ok manche mögen evtl. die Company dahinter nicht...
Wegen der CentOS Thematik sind die ganzen RHEL clones sehr beliebt. Ich hab da schon länger nicht mehr reingeschaut was aktuell eigentlich von Proxmox unterstützt wird. Ich schau mir mal die verfügbaren Clone an und prüfe für welche es LXC Container gibt, teste dann bisschen durch händisches...
Neben den Templates braucht man leider auch Support in einer der Perl Dateien von Proxmox. Es gibt z.B. lxc images von Oracle Linux, leider konnte ich es nie benutzen weil Proxmox das OS nicht erkennt, es fehlte einfach die OS Detection für das System. Natürlich kann man die Datei verändern aber...
46% Wearout on your sdp drive? that looks really bad, afaik consumer SSD have only a reserve for around 15% until they die.
In the past i run a small Proxmox Server with four Samsung 850 and they wearout in about 4 month with just a few containers running. I changed SSD to Intel D3-S4510 and...
I have the same issue. I always get stuck "dev" folders in container directorys after a reboot. I think this dev folders comes from tun device passtrough not getting cleaned up after restarting Proxmox host. I give your solution i try.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.