Search results

  1. M

    Node red after pmxcfs error

    My cluster seems to stay up for 3 or 4 days.
  2. M

    Node red after pmxcfs error

    I had the same issue. restarting "/etc/init.d/pve-cluster restart" fixed the issue for me This has happened 2 times since upgrading to 2.3
  3. M

    2 nodes showing red after upgrade to 2.3

    Ok I have both nodes working again. I dont know if this was right but I restarted /etc/init.d/pve-cluster stop than /etc/init.d/pve-cluster start and both nodes show online now.
  4. M

    2 nodes showing red after upgrade to 2.3

    /etc/init.d/cman restart Stopping cluster: Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Waiting for corosync to shutdown:[ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] Starting cluster: Checking if...
  5. M

    2 nodes showing red after upgrade to 2.3

    I upgraded 3 nodes yesterday to 2.3 and restsrted all three nodes. All was fine. When I returned to work this morning 2 nodes are showing red. I restated cman and did not help. I also restarted one node still not working. can someone help me with is.
  6. M

    Web Interface showing wrong node

    I am running Proxmox 2.2 with lasted update with 3 nodes. When I start a vm on node vs0 the tasks view shows the right node but when I click on the Console the node changes to vs1. Vs1 is the master node. The same with the other node. Is this a problem?

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!