Proxmox 3.4 add not to cluster issue

R

RaidoR

New Member
Aug 14, 2015
20
0
1
Hello,

When I try to add two nodes to cluster, I get error:

Code: 
root@tormsrvprox2:~# pvecm add tormsrvprox1
copy corosync auth key
stopping pve-cluster service
Stopping pve cluster filesystem: pve-cluster.
backup old database
Starting pve cluster filesystem : pve-cluster.
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...

My configurations:
tormsrvprox1 cluster master 192.168.1.20
tormsrvprox2 Node I am tryng to add 192.168.1.22


root@tormsrvprox1(TORMMET):~# more /etc/pve/cluster.conf

Code: 
<?xml version="1.0"?>
<cluster name="tormmet" config_version="15">

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

  <clusternodes>
  <clusternode name="tormsrvprox1" votes="1" nodeid="1"/>
  <clusternode name="tormsrvprox2" votes="1" nodeid="2"/></clusternodes>

</cluster>

root@tormsrvprox1(TORMMET):~# pvecm nodes
Code: 
Node  Sts   Inc   Joined               Name
   1   M      8   2016-03-05 11:04:58  tormsrvprox1

root@tormsrvprox1(TORMMET):~# pvecm status
Code: 
Version: 6.2.0
Config Version: 15
Cluster Name: tormmet
Cluster Id: 14426
Cluster Member: Yes
Cluster Generation: 168
Membership state: Cluster-Member
Nodes: 1
Expected votes: 1
Total votes: 1
Node votes: 1
Quorum: 1
Active subsystems: 5
Flags:
Ports Bound: 0
Node name: tormsrvprox1
Node ID: 1
Multicast addresses: 239.192.56.146
Node addresses: 192.168.1.20

root@tormsrvprox2(TORMMET):~# omping -m 239.192.56.146 192.168.1.22
Code: 
192.168.1.22 : waiting for response msg
192.168.1.22 : joined (S,G) = (*, 239.192.56.146), pinging
192.168.1.22 :   unicast, seq=1, size=69 bytes, dist=0, time=0.007ms
192.168.1.22 : multicast, seq=1, size=69 bytes, dist=0, time=0.015ms
192.168.1.22 :   unicast, seq=2, size=69 bytes, dist=0, time=0.038ms
192.168.1.22 : multicast, seq=2, size=69 bytes, dist=0, time=0.045ms

root@tormsrvprox2(TORMMET):~# more /etc/hosts
Code: 
#127.0.1.1 tormsrvprox2.torm.ee tormsrvprox2

127.0.0.1 localhost.localdomain localhost
192.168.1.22 tormsrvprox2.torm.ee tormsrvprox2 pvelocalhost

192.168.1.20 tormsrvprox1

root@tormsrvprox1(TORMMET):~# more /etc/hosts
Code: 
127.0.0.1 localhost.localdomain localhost
#127.0.1.1 tormsrvprox1.torm.ee tormsrvprox1
192.168.1.20 tormsrvprox1.torm.ee tormsrvprox1 pvelocalhost

192.168.1.21    tormsrvbacula
192.168.1.22    tormsrvprox2
Tried with unicast, but gets stuck at same spot "waiting for quorum..."
 
Hello,

More information. Ran omping from two nodes:

Code: 
root@tormsrvprox2(TORMMET):~#  omping -c 10000 -i 0.001 -F -q 192.168.1.22 192.168.1.20
192.168.1.20 : waiting for response msg
192.168.1.20 : waiting for response msg
192.168.1.20 : waiting for response msg
192.168.1.20 : waiting for response msg
192.168.1.20 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.1.20 : waiting for response msg
192.168.1.20 : server told us to stop

192.168.1.20 :   unicast, xmt/rcv/%loss = 9677/9677/0%, min/avg/max/std-dev = 0.197/0.241/1.074/0.01                                                                                                               9
192.168.1.20 : multicast, xmt/rcv/%loss = 9677/0/100%, min/avg/max/std-dev = 0.000/0.000/0.000/0.000

Code: 
root@tormsrvprox1(TORMMET):~# omping -c 10000 -i 0.001 -F -q 192.168.1.22 192.168.1.20
192.168.1.20 : waiting for response msg
192.168.1.20 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.1.20 : given amount of query messages was sent

192.168.1.20 :   unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.197/0.240/1.030/0.017
192.168.1.20 : multicast, xmt/rcv/%loss = 10000/0/100%, min/avg/max/std-dev = 0.000/0.000/0.000/0.000
 
You must log in or register to reply here.
Top Bottom