[SOLVED] Cluster authentification failure

proxene

Member
Sep 15, 2017
14
1
8
33
Belgique
face-h.eu
Hello,

I will need help and fresh blood to solve my problem.

This is the first time I have this problem, usually everything works normally except when I want to add a new node to make a cluster I get this error :

Code:
Etablishing API connection with host '************'
The authenticity of host '************' can't be established.
X509 SHA256 key fingerprint is ************.
Are you sure you want to continue connecting (yes/no)? yes

401 401 authentication failure


I went through the forum and checked my actions on the wiki but without success. I already try to use -use_ssh and it doesn't work.

Can you help me ?

Thank you in advance.

Best regards,
Proxene
 
Last edited:
what command do you run?
you first have to do
Code:
pvecm create <clustername> [options]

and then from a second node to the one where you created the cluster
Code:
pvecm add <hostname/ip-of-node-already-in-cluster> [options]
 
what command do you run?
you first have to do
Code:
pvecm create <clustername> [options]

and then from a second node to the one where you created the cluster
Code:
pvecm add <hostname/ip-of-node-already-in-cluster> [options]


Thank you for your reply :)

Yeah I already created a cluster on the 1th node.
I use this command on the 2th node : pvecm add *****


Best regards,
Proxene
 
what is the pveversion -v of both nodes?
 
For the first node it's

proxmox-ve: 5.1-26 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.17-1-pve: 4.10.17-18
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve5
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-4
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-8
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.2-4
pve-qemu-kvm: 2.11.1-5
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-5
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.9-pve1~bpo9


For the second node it's

proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-2
pve-kernel-4.15.17-2-pve: 4.15.17-10
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

Best regards,
Proxene
 
Last edited:
please upgrade your nodes so that both have the same version and try again
 
  • Like
Reactions: proxene