Cant build cluster in 3.0

[hambleto]

Hello. I have been following the instructions in http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster to create a cluster on the same subnet with private IPs. I have made sure the hosts files are correct, and time is synced. However when I log into the second node and run pvecm add IP-ADDRESS-CLUSTER the following happens:

root@IP-ADDRESS-CLUSTER's password:
copy corosync auth key
stopping pve-cluster service
Stopping pve cluster filesystem: pve-cluster.
backup old database
Starting pve cluster filesystem : pve-clustercan't create shared ssh key database '/etc/pve/priv/authorized_keys'
.
Starting cluster:
Checking if cluster has been disabled at boot... [ OK ]
Checking Network Manager... [ OK ]
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Starting cman... [ OK ]
Waiting for quorum... Timed-out waiting for cluster
[FAILED]
waiting for quorum...

It will just sit there for ages and do nothing. I have reformatted and reinstalled the node again and the same thing happens. Am I missing something? Any idea as to where to look would be greatly appreciated.
Thank you,
Ben

 

[webfrank]

Hello. I have been following the instructions in http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster to create a cluster on the same subnet with private IPs. I have made sure the hosts files are correct, and time is synced. However when I log into the second node and run pvecm add IP-ADDRESS-CLUSTER the following happens:

root@IP-ADDRESS-CLUSTER's password:
copy corosync auth key
stopping pve-cluster service
Stopping pve cluster filesystem: pve-cluster.
backup old database
Starting pve cluster filesystem : pve-clustercan't create shared ssh key database '/etc/pve/priv/authorized_keys'
.
Starting cluster:
Checking if cluster has been disabled at boot... [ OK ]
Checking Network Manager... [ OK ]
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Starting cman... [ OK ]
Waiting for quorum... Timed-out waiting for cluster
[FAILED]
waiting for quorum...

It will just sit there for ages and do nothing. I have reformatted and reinstalled the node again and the same thing happens. Am I missing something? Any idea as to where to look would be greatly appreciated.
Thank you,
Ben

hi, the same appenedeto me with new 3.0 cluster, I solved recreating keys on first node and using foce option on second.

 

[hambleto]

In the end it turned out for me that I did not have multicast enabled on the switches. Once I upgraded the firmware on the switches and had multicast enabled I was able to create the cluster with no problem at all.