Increasing node votes in a cluster

abale.ls

New Member
Oct 19, 2016
5
0
1
35
I have a cluster with 2 nodes, and as configured by default, they both have 1 vote and will not reach quorum:

Code:
Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      1
Quorum:           2 Activity blocked
Flags:
I've tried stopping the pve-cluster service and coreosync, editing the corosync.conf file in /etc/corosync (on both machines) to increase the votes of the primary nodes to 2 and increment the configversion, but it seems that after starting both corosync and pve-cluster, the file will be back to the old config with 1 vote.

If somebody can point me in the right direction (or tell me if 2 node cluster is not supported) then I would appreciate it!

Code:
nodelist {
  node {
    name: hv02
    nodeid: 2
    quorum_votes: 1
    ring0_addr: hv02
  }

  node {
    name: hv01
    nodeid: 1
    quorum_votes: 1
    ring0_addr: hv01
  }

}

quorum {
  provider: corosync_votequorum
}
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,600
339
103
Austria
www.proxmox.com
You have:

Total votes: 1

So only one node seems to be online (or multicast is not working).
 

abale.ls

New Member
Oct 19, 2016
5
0
1
35
If I reset the cluster and re-add them, they can see eachother until a reboot, at which point they can no longer see one-another.
 

abale.ls

New Member
Oct 19, 2016
5
0
1
35
multicast seems to be working:

from first node:

Code:
# omping stl2hv01 stl2hv02
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : joined (S,G) = (*, 232.43.211.234), pinging
stl2hv01 :   unicast, seq=1, size=69 bytes, dist=0, time=0.261ms
stl2hv01 : multicast, seq=1, size=69 bytes, dist=0, time=0.311ms
stl2hv01 :   unicast, seq=2, size=69 bytes, dist=0, time=0.349ms
stl2hv01 : multicast, seq=2, size=69 bytes, dist=0, time=0.375ms
stl2hv01 :   unicast, seq=3, size=69 bytes, dist=0, time=0.356ms
from second node:

Code:
# omping stl2hv01 stl2hv02
stl2hv02 : waiting for response msg
stl2hv02 : joined (S,G) = (*, 232.43.211.234), pinging
stl2hv02 :   unicast, seq=1, size=69 bytes, dist=0, time=0.384ms
stl2hv02 :   unicast, seq=2, size=69 bytes, dist=0, time=0.345ms
stl2hv02 : multicast, seq=2, size=69 bytes, dist=0, time=0.439ms
 

abale.ls

New Member
Oct 19, 2016
5
0
1
35
I just caught this actually, from the second node - not sure fi related (crm and lrm both throw this)

Oct 19 13:20:09 stl2hv02 pve-ha-crm[2421]: ipcc_send_rec failed: Connection refused
Oct 19 13:20:09 stl2hv02 pve-ha-crm[2421]: ipcc_send_rec failed: Connection refused
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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!