Bad Node in Cluster: How to Remove?

[slam]

One of my nodes in the cluster just died and it's affecting the remaining nodes and the cluster. Is there a way to forcefully remove that bad node from whole cluster? or is there a way to recreate the cluster with the remaining good nodes?

Here's my current config:

root@proxmox:~# pvecm nodes
Node Sts Inc Joined Name
1 M 140 2012-04-30 20:56:57 proxmox
2 M 1564 2012-05-14 20:38:33 p2
3 M 164 2012-05-08 08:32:27 p3

proxmox = master node
p2 = bad node
p3 = good node

 

[dietmar]

1.) turn of p2 (and remove physically from network)
2.) on proxmox run:

# pvecm expected 2
# pvecm delnode p2

 

[slam]

root@proxmox:~# pvecm expected 2
root@proxmox:~# pvecm delnode p2
node p2 does not exist in /etc/pve/cluster.conf

root@proxmox:~# pvecm nodes
Node Sts Inc Joined Name
1 M 140 2012-04-30 20:56:57 proxmox
2 M 23680 2012-05-15 12:16:37 p2
3 M 23680 2012-05-15 12:16:38 p3

The bad node is still listed.

 

[dietmar]

Please can you post your cluster.conf

# cat /etc/pve/cluster.conf

Seems it does not contain node 'p2'?

 

[npublish]

Hello,
sorry to warm this old topic up again, Google brought me here due to very few hits on this specific error message.
We have a similar situation:

• Proxmox 3.4 on three node cluster
• node 2 prematurely removed from cluster by "pvecm delnode proxmox02" on node 2, itself
• then node 2 was turned off
• we issued "pvecm expected 2" on node 1
  
• on node 1, we now get "node proxmox02 does not exist in /etc/pve/cluster.conf" when issueing "pvecm delnode proxmox02" - same goes for node 3
  
• /etc/pve/cluster.conf does not contain node proxmox02 on any of the remaining two nodes
• "pvecm nodes" still shows node 2 in status X: "2 X 55928 proxmox02"

How can we fix this? Might rebooting the remaining two nodes fix this?
Thanks for a quick clarification.
Best regards from Cologne
Chris