Hello,
We used to work with Xenserver but we are testing Proxmox and will probably start using it.
The issue is that we have set up a cluster of 4 servers 192.168.1.230-233 setting the master
as 192.168.1.230.
We are able to create cluster without a problem:
root@hv01:~# pvecm create dc01cluster01
Corosync Cluster Engine Authentication key generator.
Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
But everytime we try to add a new member, takes forever to get quorum and when it gets quorum
fails in the end with this message:
root@hv02:~# pvecm add 192.168.1.230
The authenticity of host '192.168.1.230 (192.168.1.230)' can't be established.
ECDSA key fingerprint is 39:56:ad:6d:bf:4e:2f:c3:80:05:bd:f3:56:ba:e7:17.
Are you sure you want to continue connecting (yes/no)? yes
root@192.168.1.230's password:
copy corosync auth key
stopping pve-cluster service
backup old database
waiting for quorum...OK
generating node certificates
unable to create directory '/etc/pve/nodes' - Permission denied
After this the cluster block:
root@hv01:~# pvecm status
Quorum information
------------------
Date: Fri Jan 26 16:55:09 2018
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1/60
Quorate: No
Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.1.230 (local)
We are unable to add new nodes and it will never "unlock".
The directory /etc/pve/nodes exists on hv01 (cluster master) :
dr-xr-xr-x 2 root www-data 0 Jan 26 15:17 hv01
dr-xr-xr-x 2 root www-data 0 Jan 26 15:54 hv02
but it doesn't exist on the second server we are trying to add:
-r--r----- 1 root www-data 151 Jan 1 1970 .clusterlog
-r--r----- 1 root www-data 444 Jan 26 15:54 corosync.conf
-rw-r----- 1 root www-data 2 Jan 1 1970 .debug
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 local -> nodes/hv02
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 lxc -> nodes/hv02/lxc
-r--r----- 1 root www-data 228 Jan 1 1970 .members
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 openvz -> nodes/hv02/openvz
dr-x------ 2 root www-data 0 Jan 26 16:17 priv
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 qemu-server -> nodes/hv02/qemu-server
-r--r----- 1 root www-data 216 Jan 1 1970 .rrd
-r--r----- 1 root www-data 378 Jan 1 1970 .version
-r--r----- 1 root www-data 18 Jan 1 1970 .vmlist
We see there some broken soft links (local, lxc and qemu.server) nut no nodes directory.
We've tried with Proxmox 5.1-3 severeal times reinstalling from ground and also with the 4.4 version, both versions happens the same...
We are new at this and is kind of strange on a new system this. The search on Google didn't help.
Any ideias why this might happen?? We are talking about fresh install nothing other Proxomox on it.
Cheers,
Hugo Ferreira
We used to work with Xenserver but we are testing Proxmox and will probably start using it.
The issue is that we have set up a cluster of 4 servers 192.168.1.230-233 setting the master
as 192.168.1.230.
We are able to create cluster without a problem:
root@hv01:~# pvecm create dc01cluster01
Corosync Cluster Engine Authentication key generator.
Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
But everytime we try to add a new member, takes forever to get quorum and when it gets quorum
fails in the end with this message:
root@hv02:~# pvecm add 192.168.1.230
The authenticity of host '192.168.1.230 (192.168.1.230)' can't be established.
ECDSA key fingerprint is 39:56:ad:6d:bf:4e:2f:c3:80:05:bd:f3:56:ba:e7:17.
Are you sure you want to continue connecting (yes/no)? yes
root@192.168.1.230's password:
copy corosync auth key
stopping pve-cluster service
backup old database
waiting for quorum...OK
generating node certificates
unable to create directory '/etc/pve/nodes' - Permission denied
After this the cluster block:
root@hv01:~# pvecm status
Quorum information
------------------
Date: Fri Jan 26 16:55:09 2018
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1/60
Quorate: No
Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.1.230 (local)
We are unable to add new nodes and it will never "unlock".
The directory /etc/pve/nodes exists on hv01 (cluster master) :
dr-xr-xr-x 2 root www-data 0 Jan 26 15:17 hv01
dr-xr-xr-x 2 root www-data 0 Jan 26 15:54 hv02
but it doesn't exist on the second server we are trying to add:
-r--r----- 1 root www-data 151 Jan 1 1970 .clusterlog
-r--r----- 1 root www-data 444 Jan 26 15:54 corosync.conf
-rw-r----- 1 root www-data 2 Jan 1 1970 .debug
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 local -> nodes/hv02
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 lxc -> nodes/hv02/lxc
-r--r----- 1 root www-data 228 Jan 1 1970 .members
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 openvz -> nodes/hv02/openvz
dr-x------ 2 root www-data 0 Jan 26 16:17 priv
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 qemu-server -> nodes/hv02/qemu-server
-r--r----- 1 root www-data 216 Jan 1 1970 .rrd
-r--r----- 1 root www-data 378 Jan 1 1970 .version
-r--r----- 1 root www-data 18 Jan 1 1970 .vmlist
We see there some broken soft links (local, lxc and qemu.server) nut no nodes directory.
We've tried with Proxmox 5.1-3 severeal times reinstalling from ground and also with the 4.4 version, both versions happens the same...
We are new at this and is kind of strange on a new system this. The search on Google didn't help.
Any ideias why this might happen?? We are talking about fresh install nothing other Proxomox on it.
Cheers,
Hugo Ferreira
