Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 170583

quorum timeout adding node to cluster unicast

$
0
0
I have a two node cluster (node name pm0 and pm1 ) with unicast enabled ( transport="udpu" )

Code:

<?xml version="1.0"?>
<cluster name="alidays-cluster" config_version="15">

  <cman keyfile="/var/lib/pve-cluster/corosync.authkey" transport="udpu">
  </cman>

  <clusternodes>
  <clusternode name="pm1" votes="1" nodeid="1"/>
  <clusternode name="pm0" votes="1" nodeid="2"/></clusternodes>

</cluster>

pveversion :
Code:

root@pm1:~# pveversion
pve-manager/2.3/7946f1f1

I setup a new host (pm2) with a fresh installation of pve . When adding this node to the cluster I got the error "Waiting for quorum... Timed-out waiting for cluster"
Code:

root@pm2:/var/log# pvecm add pm1
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...

the new cluster configuration on pm1:
Code:

<?xml version="1.0"?>
<cluster name="alidays-cluster" config_version="16">

  <cman keyfile="/var/lib/pve-cluster/corosync.authkey" transport="udpu">
  </cman>

  <clusternodes>
  <clusternode name="pm1" votes="1" nodeid="1"/>
  <clusternode name="pm0" votes="1" nodeid="2"/><clusternode name="pm2" votes="1" nodeid="3"/></clusternode
s>

</cluster>

the new node seem to be added to the cluster but when cman start it's fail to join the cluster
Code:

Jul 23 15:23:08 corosync [MAIN  ] Successfully configured openais services to load
Jul 23 15:23:08 corosync [TOTEM ] Initializing transport (UDP/IP Unicast).
Jul 23 15:23:08 corosync [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Jul 23 15:23:08 corosync [TOTEM ] The network interface [192.168.169.15] is now up.
Jul 23 15:23:08 corosync [QUORUM] Using quorum provider quorum_cman
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync cluster quorum service v0.1
Jul 23 15:23:08 corosync [CMAN  ] CMAN 1352871249 (built Nov 14 2012 06:34:12) started
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync CMAN membership service 2.90
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: openais cluster membership service B.01.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: openais event service B.01.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: openais checkpoint service B.01.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: openais message service B.03.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: openais distributed locking service B.03.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: openais timer service A.01.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync extended virtual synchrony service
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync configuration service
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync cluster config database access v1.01
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync profile loading service
Jul 23 15:23:08 corosync [QUORUM] Using quorum provider quorum_cman
Jul 23 15:23:08 corosync [SERV  ] Service engine loaded: corosync cluster quorum service v0.1
Jul 23 15:23:08 corosync [MAIN  ] Compatibility mode set to whitetank.  Using V1 and V2 of the synchronization engine.
Jul 23 15:23:08 corosync [TOTEM ] adding new UDPU member {192.168.169.10}
Jul 23 15:23:08 corosync [TOTEM ] adding new UDPU member {192.168.169.5}
Jul 23 15:23:08 corosync [TOTEM ] adding new UDPU member {192.168.169.15}
Jul 23 15:23:08 corosync [CLM  ] CLM CONFIGURATION CHANGE
Jul 23 15:23:08 corosync [CLM  ] New Configuration:
Jul 23 15:23:08 corosync [CLM  ] Members Left:
Jul 23 15:23:08 corosync [CLM  ] Members Joined:
Jul 23 15:23:08 corosync [CLM  ] CLM CONFIGURATION CHANGE
Jul 23 15:23:08 corosync [CLM  ] New Configuration:
Jul 23 15:23:08 corosync [CLM  ]      r(0) ip(192.168.169.15)
Jul 23 15:23:08 corosync [CLM  ] Members Left:
Jul 23 15:23:08 corosync [CLM  ] Members Joined:
Jul 23 15:23:08 corosync [CLM  ]      r(0) ip(192.168.169.15)
Jul 23 15:23:08 corosync [TOTEM ] A processor joined or left the membership and a new membership was formed.
Jul 23 15:23:08 corosync [QUORUM] Members[1]: 3
Jul 23 15:23:08 corosync [QUORUM] Members[1]: 3
Jul 23 15:23:08 corosync [CPG  ] chosen downlist: sender r(0) ip(192.168.169.15) ; members(old:0 left:0)
Jul 23 15:23:08 corosync [MAIN  ] Completed service synchronization, ready to provide service.


Viewing all articles
Browse latest Browse all 170583

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>