Search results

  1. pveproxy become blocked state and cannot be killed

    I have had this happen a few times with 4.4. Each time the problem is that corosync isn't running on one of the machines. Its always the machine not showing the 'D' states.
  2. I broke my proxmox node ( Can't locate PVE/OTP.pm in @INC )

    I was able to recover a system that had this happen to it. I think the key bit was to run: <code>dpkg --purge libappconfig-perl libjs-extjs libtemplate-perl</code> Not totally sure about all three packages, and I sure don't want to go through that again. Just recording here for future...
  3. pveproxy become blocked state and cannot be killed

    Yeah, I am sorry. I wish it was otherwise. It could still be ZFS, but I don't understand how it could be related to the cluster.
  4. pveproxy become blocked state and cannot be killed

    I am exclusively using ZFS, ECC RAM and E3 Xeon processors in my cluster.
  5. pveproxy become blocked state and cannot be killed

    Ran into this problem today, running a new-ish kernel. 4.4.6-1-pve Running /etc/init.d/pve-cluster restart on one node fixed the issue on all nodes. Did I just happen to guess correctly on the broken node? pvecm status said everything was fine. I could read files inside /etc/pve After I...

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 your own in 60 seconds.

Buy now!