Search results

Welcome to the forum, Aaron! The Proxmox forum is English only so that more people can benefit from the conversations on here. Please post in English in future posts. For your post, I'm not sure if I understand what you are trying to achieve completely. As far as I understand, you have two...

Thanks for sharing your solution with the forum! It will surely help other people facing similar issues.

Freut mich zu hören, dass das System nun stabil läuft! Es würde mich und sicher weitere Forum-User interessieren, ob mit dem neuen Microcode-Update von Intel der Fehler behoben wurde oder ob es weiterhin zu Instabilitäten kommt. Erstelle dafür gerne ein weiteren Thread (und referenziere evtl...

Have you already resolved the problem in the mean time? If not, you're probably right about that the system has reordered the drive names and now the ZFS filesystem cannot be mounted as the newly connected SSD is not part of the zpool yet. You can try to boot the system with the new SSD...

Have you checked that you have no IPv4 address collisions in your network, i.e. that 192.168.0.3 is only used for your pve node? Have you also checked the output from pvecm status from the pve node itself? Have you tried to restart the following services on your nodes? systemctl restart...

Have you already resolved the problem? If not, could you post: - if your network device is showing up and has a proper driver loaded with lspci -nnk | grep -A2 -E '(Network|Ethernet)' - the syslog from a boot from each kernel, e.g. boot with each kernel and then pipe the output of journalctl...

Just for anyone stumbling on this post, the bug report associated with the problem can be seen at [1]. [1] https://bugzilla.proxmox.com/show_bug.cgi?id=5585

Have you tried to change the enp3s0f0 in the line post-up echo 1 > /proc/sys/net/ipv4/conf/enp3s0f0/proxy_arp to the actual network card's name enp4s0f1? It could be that pfSense or your hosting provider is strict about which MAC addresses are on the network or are using your IP addresses and...

It's hard to tell what could cause the high network traffic without any logging information. What is currently running on your system (e.g. Ceph)? Does the output of journalctl --since '2024-08-29 11:25' --until '2024-08-29 12:25' indicate anything related to the high inward network traffic...

It would be helpful to have more information what happens during those down times. As I can see from the screenshots, the first one is from the second node P-proxmox2 and the second one is from the first node P-proxmox1. Can you ping the second node from the first node and vice versa without any...

It would be helpful to have a little bit more information on your PVE node setup. Can you post the output of pveversion -v? Could you post the output of cat /proc/cmdline and journalctl -b -1 -e for the syslog of the last boot? Otherwise, I have seen that there a quite a few issues with Dell...

Soweit ich gesehen habe, werden diese Submenüs bei jedem Mal, wenn eine Node angeklickt wurde, von neu expandiert. Es wäre womöglich sinnvoll, dass entweder der Zustand, ob ein Submenü geöffnet / geschlossen war, gespeichert wird oder wie du beschrieben hast insgesamt global geschlossen bleiben...

Hey there! First of all, you can set the DNS settings for your containers in your WebGUI at "LXC2 > DNS". By default, they use the same DNS servers you have set up on your PVE host. As you can successfully ping google.com your DNS for external services should probably be fine. Are your...

Hello there! This is not an error per se, but just a notice that you do not use the proxmox-boot-tool, which just means that you are probably not using ZFS on your root directory (that is, you haven't chosen ZFS as a root filesystem when installing Proxmox VE). It could also mean, that you've...

Hallo Crash1601! Es könnte gut sein, dass durch die dezidierte Zuteilung, die du vorgenommen hast, nun vermehrt auch auf dem scheinbar instabilen Core ausgeführt wurde, anstatt KVM die Policy zu überlassen und das dadurch der Fehler erst aufgefallen ist. Ich bin jedoch selbst erst oberflächlich...

I suppose that the interfaces configuration is for the raspberrypi. It would be helpful if you could test if you're able to connect to the other nodes through SSH and if there is any error as @sw-omit already mentioned. Also check if your network has any IP address collisions, especially with...

Danke für die Antwort! Bei einem Kommando habe ich mich leider verschrieben, falls du das in deinem Post eventuell noch mal editieren/neu posten könntest: journalctl --since '2024-08-25' --until today --unit pvestatd.service > journal.log, da sollte ein Log-Output des pvestatd Services mit den...

Danke für den ausführlichen Post, es wäre hilfreich wenn du dazu noch folgendes posten könntest: die aktuell installierten PVE Paketversionen: pveversion -v den vollen Syslog der pvestatd systemd unit: journalctl --since '2024-08-25' --unit pvestatd --unit pveproxy und auch den apt history log...

As far as I can tell this bug was fixed for Proxmox VE v8.1 at the latest, as can be viewed in the release notes for PVE v8.1 under the header "Access control" at [1]. The correlated bug report for this can be found at [2]. [1] https://pve.proxmox.com/wiki/Roadmap#Access_control_3 [2]...

As for the backups, I'm not sure if I fully understand what you mean with "backup functionality". Have you already added the two disks as storages for your PVE host? There are plenty of ways to backup VMs, for one you can setup a backup job in "Datacenter > Backup" and set the schedule...