Cluster waiting for quorum...ok

Maher Khalil

Member
Jul 11, 2021
232
10
23
44
Hello
I am trying to create my first cluster.
For each time I create new installation and trying to join the cluster, it will stop waiting for quorum...ok (check the attached photo). also i cannot access GUI
I do not know if I should wait or something is wrong
i am not able to add node 3 because node 2 not yet completed
I am providing separate network for cluster
please advice on this
 

Attachments

  • Screenshot from 2023-01-02 00-26-30.png
    Screenshot from 2023-01-02 00-26-30.png
    23.5 KB · Views: 42
  • Screenshot from 2023-01-02 00-31-39.png
    Screenshot from 2023-01-02 00-31-39.png
    122.1 KB · Views: 34
  • Screenshot from 2023-01-02 00-32-34.png
    Screenshot from 2023-01-02 00-32-34.png
    41.3 KB · Views: 32
Since you are starting with a separate cluster network prior to having a cluster try the link below.

Read here, https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_redundancy , find the section copied below to start. Then follow the link within that section to add to a separate cluster network. Most of install then added a separate network after cluster creation.

Separate On Cluster Creation​

This is possible via the linkX parameters of the pvecm create command, used for creating a new cluster.
If you have set up an additional NIC with a static address on 10.10.10.1/25, and want to send and receive all cluster communication over this interface, you would execute:

pvecm create test --link0 10.10.10.1

To check if everything is working properly, execute:

systemctl status corosync

Afterwards, proceed as described above to add nodes with a separated cluster network.
 
Hello
I followed this tutorial but I still get the same result
waiting for quorum...ok
 

Attachments

  • Screenshot from 2023-01-02 02-31-19.png
    Screenshot from 2023-01-02 02-31-19.png
    59.7 KB · Views: 16
  • Screenshot from 2023-01-02 02-31-57.png
    Screenshot from 2023-01-02 02-31-57.png
    5.8 KB · Views: 17
  • Web capture_2-1-2023_23534_104.217.250.74.jpeg
    Web capture_2-1-2023_23534_104.217.250.74.jpeg
    42.7 KB · Views: 17
Last edited:
This looks like corosync expects the nodes to be using 10.10.10.1 and 10.10.10.2

not the 10.10.1.10/24 10.10.1.20/24 and 10.10.1.30/24 you set up earlier today.
 
I would slow down, your /etc/pve/corosync.conf might already be messy.

I have a separate redundant corosync network, but I think like most home users that go this far I first set up clustering through the GUI using my vmbr0 network/IP on all nodes. Then I later added the separate Corosync network and finally made that network primary. First time I have seen someone do separate network before clustering, so I can't offer much more help. Maybe the proxmox staff will have better advice on what to do from this direction.