[SOLVED] Proxmox 3.3-1 SRV corosync restart failed waiting for quorum Timed out waiting cluste

martink

Renowned Member
Jun 17, 2011
23
0
66
Dear Promox community,


we wanted to set up a Proxmox cluster with 3 nodes :


srv005 10.5.1.5
srv04 10.5.1.4
srv01 10.5.1.30




we had the three servers installed with Proxmox 3.2 wihout clustering, made the upgrade to Proxmox 3.3.


Then we changed the ip addresses von 10.3.1.XX to 10.5.1.XX


All VMs from the srv04 and srv01 were backed up to get a clean machine, but on srv005 all VMs were not deleted.


we modified /etc/hosts on every server


127.0.0.1 localhost.localdomain localhost
10.5.1.4 srv04.xxxxxxxx.com srv04 pvelocalhost
10.5.1.5 srv005.xxxxxxxx.com srv005
10.5.1.30 srv01.xxxxxxxx.com srv01


Then we took srv005 for our first node, and added two more nodes : srv01 and srv04

Something went wrong or we did a mstake, this now the result :

SRV corosync restart failed waiting for quorum Timed out waiting for cluster


Proxmox_SRV_corosync_Restart.png


We can start and stop VMs on srv005, but we cannot create new VMS on the other two servers.
All servers below the datacenter are marked red

Proxmox_cluster_server_red01.png

Error from the syslog :

cpg_send_message failed

Proxmox_cluster_server_corosync_syslog.png


We have checked multicast with asmping, should be working fine

Proxmox_cluster_server_red01_multicast_working.png


root@srv005:/etc/init.d# pvecm nodes
Node Sts Inc Joined Name
1 M 4 2014-09-21 17:44:05 srv005
2 X 300 srv01
3 X 12 srv04


root@srv005:/etc/init.d# pvecm status
Version: 6.2.0
Config Version: 3
Cluster Name: rzdog01
Cluster Id: 14245
Cluster Member: Yes
Cluster Generation: 6420
Membership state: Cluster-Member
Nodes: 1
Expected votes: 1
Total votes: 1
Node votes: 1
Quorum: 2 Activity blocked
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: srv005
Node ID: 1
Multicast addresses: 239.192.55.220
Node addresses: 10.5.1.5
root@srv005:/etc/init.d#



any tips and hints to get this cluster working are welcome, thanks !
 
Last edited by a moderator:
Re: Proxmox 3.3-1 SRV corosync restart failed waiting for quorum Timed out waiting cl

error solved : double ip address entry for proxmox node, all system up & running now
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, 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 yours easily in our online shop.

Buy now!