On first node
############################################################################
root@main1:~# pvecm create MyCluster
Corosync Cluster Engine Authentication key generator.
Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
root@main1:~# pvecm status
Quorum information
------------------
Date: Sun Mar 6 16:14:00 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 4
Quorate: Yes
Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.0.1 (local)
root@main1:~#
while trying to create proxmox cluster:
On second or third node ( eternally stuck on "waiting for quorum" )
###############################################################################
root@main3:~# pvecm add 192.168.0.1
The authenticity of host '192.168.0.1 (192.168.0.1)' can't be established.
ECDSA key fingerprint is 07:ed:ee:e6:35:0f:21:e2:08:59:21:4b:dc:fa:71:98.
Are you sure you want to continue connecting (yes/no)? yes
root@192.168.0.1's password:
copy corosync auth key
stopping pve-cluster service
backup old database
Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.
waiting for quorum...
**** Note *** Actual IP is different , 192.168.0.1 is used for representation.
Both main1 and main3 server can ping each other , and its added to /etc/hosts entry of each other server.
*** Proxmox VE Version: 4.1-1
Please advise.
############################################################################
root@main1:~# pvecm create MyCluster
Corosync Cluster Engine Authentication key generator.
Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
root@main1:~# pvecm status
Quorum information
------------------
Date: Sun Mar 6 16:14:00 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 4
Quorate: Yes
Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.0.1 (local)
root@main1:~#
while trying to create proxmox cluster:
On second or third node ( eternally stuck on "waiting for quorum" )
###############################################################################
root@main3:~# pvecm add 192.168.0.1
The authenticity of host '192.168.0.1 (192.168.0.1)' can't be established.
ECDSA key fingerprint is 07:ed:ee:e6:35:0f:21:e2:08:59:21:4b:dc:fa:71:98.
Are you sure you want to continue connecting (yes/no)? yes
root@192.168.0.1's password:
copy corosync auth key
stopping pve-cluster service
backup old database
Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details.
waiting for quorum...
**** Note *** Actual IP is different , 192.168.0.1 is used for representation.
Both main1 and main3 server can ping each other , and its added to /etc/hosts entry of each other server.
*** Proxmox VE Version: 4.1-1
Please advise.