Search results

  1. B

    Ceph Quincy "Daemons have recently crashed" after node reboots

    I did have the same issue. I only have 3 servers in a cluster. After upgrading to Ceph Quincy it started. These days I have been doing a lot of debugging and found out that the ceph-crash service wants to read a keyring file, which did not exist. So I created...
  2. B

    GUI-Problem nach update auf 7.2-3

    Das wird auf dem Proxmox Host Datacenter -> Storage -> Name des Shares, Advanced, NFS Version
  3. B

    GUI-Problem nach update auf 7.2-3

    Nach dem Upgrade von 7.1 auf 7.2 gestern Abend hatte ich das gleiche Symptom. Ich habe 2 Shares auf einem QNAP gemountet. Ich konnte feststellen, dass beim Start der Mount der Shares auf das QNAP hängt. Auf Ebene CLI scheint alles zu funktionieren. Das GUI ist massiv reduziert. Ich konnte bei...
  4. B

    PVE upgrade 6.4 > 7 network completely down

    I did have exactly the same problem. I did follow the instructions https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0. I am using openvswitch. After the reboot, the network was gone. I configured a single interface to get network connectivity and then I did: apt-get install ifupdown2...
  5. B

    OpenBSD client uses 100% CPU and freezes

    Thank you, I moved now the configuration to serial without vga.
  6. B

    OpenBSD client uses 100% CPU and freezes

    Hi There I run 40 virtual machines in my cluster. All of them behave fine except the one openBSD based appliance. This appliance uses openBSD 6.1. I have contacted the vendor, but he cannot find anything suspicious on the appliance itself (www.seppmail.ch). I can trigger the situation by...
  7. B

    pvestatd problem

    It is the network card, which all this systems also got in common. The ones not working got intel, use the igb driver and use jumbo frames. The others that work all use realtek. It has nothing to do with the CPU.
  8. B

    pvestatd problem

    I have some more information: with kernel 4.13.8.2-pve, it does work on all my single CPU iCore 3/5/7 systems. with kernel 4.13.8.2-pve, it does NOT work on dual cpu Xeon systems exactly the same installation. In both cases I use openvswitch.
  9. B

    pvestatd problem

    Funny enough! I added a machine to the cluster, updated everything to the latest version. Kernel is pve-kernel-4.13.8.2-pve. Everything works. Repository is no-subscription. I have removed the one machine which does not work from the cluster. Reinstalled it exactly the same as the other...
  10. B

    pvestatd problem

    I have the same problem. When I boot the kernel "pve-kernel-4.13.8-2-pve", pvesm status hangs. I could track it down to the external ceph storage. With "pve-kernel-4.13.4-1-pve" everything works as expected. ceph is accessible. With the new kernel, the command /usr/bin/rados -p rbd <many...
  11. B

    NoVNC Bug

    I had the same problem and I have Safari Adblock installed. Configure Safari Adblock to "don't run on this site" and the problem is solved.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!