Problems to add node PVE1.8 to cluster master PVE2.0

navearg

New Member
Sep 16, 2011
8
0
1
argentina
Dear:
Excuse my bad English but I speak in Castilian!
I'm setting a cluster of two servers, one with PVE1.8 (node ​​or slave) and one with PVE2.0 (master) The issue is that when you run the command on the node-to-h pveca <hostname>, asks my the password and returns it to the console this error:

proxmox:~# pveca -a -h gf
root@192.168.1.254's password:
bash: /usr/bin/pveca: No such file or directory
unable to add node: command failed - ssh 192.168.1.254 /usr/bin/pveca -a 'IP:192 .168.1.101' 'NAME:proxmox' 'HOSTRSAPUBKEY:AAAAB3NzaC1yc2EAAAABIwAAAQEAyQ585cdEMe 9hoJE3jISZ05skStI2p8j69KpoNURUQRb46QTKcdhfyLFNCniodU08rf0XWcg3w/eBrlakrjhb/axSf8 TCeBiJFD3tlHaN0P76EZhuh2czPwyzPizs23dkc5QotlRobTBu+pxicVjt55C3V8FlX50JUaLT9UFLMf /WNb7Kjr3+BZxn4PemKgvLGsUn0WS3aOlvwjHZmDQGU/DXYFfmsLJ2CxCOeudF5ZHFgnYphm+/wrTQ7Q JjC99hBhTY4/YrSt892J2jhiLdFf1djVUGIOCMC9EtgZoO9dQCY8eld/7y+Z/Wvf97uYxZjrf2bL06xv ULTPgUcL2y7w==' 'ROOTRSAPUBKEY:AAAAB3NzaC1yc2EAAAABIwAAAIEA1QI9wztc7ATLLz5E/jL7L PvQW5II77/1rzgl+ZMh1o6WenYK8pR2alntaRYHS/qTTxPYHfVBS2lG/VpUYoRXjm/wK22JctHjlVTHn dXCtolT0KGbK6AITDNTCWXMhDL555cbDmtsO8RiVE40x3newF3cFCmYpHCfrPw2sG47YNU='

The first time i run the comand, forget to delete VMs from the node and idk if it will havesomething to do.

Someone could tell me the problem I'm having and the solution?

Thank you very much!
 
Dear:
Excuse mybadEnglishbut I speak inCastilian!
I'msetting aclusterof twoservers, onewithPVE1.8(node​​or slave)and one withPVE2.0(master)The issue is thatwhen you runthe commandon the node-to-hpveca<hostname>,asks mythe password andreturns itto the consolethis error:

proxmox:~# pveca -a -h gf
root@192.168.1.254's password:
bash: /usr/bin/pveca: No such file or directory
unable to add node: command failed - ssh 192.168.1.254 /usr/bin/pveca -a 'IP:192 .168.1.101' 'NAME:proxmox' 'HOSTRSAPUBKEY:AAAAB3NzaC1yc2EAAAABIwAAAQEAyQ585cdEMe 9hoJE3jISZ05skStI2p8j69KpoNURUQRb46QTKcdhfyLFNCniodU08rf0XWcg3w/eBrlakrjhb/axSf8 TCeBiJFD3tlHaN0P76EZhuh2czPwyzPizs23dkc5QotlRobTBu+pxicVjt55C3V8FlX50JUaLT9UFLMf /WNb7Kjr3+BZxn4PemKgvLGsUn0WS3aOlvwjHZmDQGU/DXYFfmsLJ2CxCOeudF5ZHFgnYphm+/wrTQ7Q JjC99hBhTY4/YrSt892J2jhiLdFf1djVUGIOCMC9EtgZoO9dQCY8eld/7y+Z/Wvf97uYxZjrf2bL06xv ULTPgUcL2y7w==' 'ROOTRSAPUBKEY:AAAAB3NzaC1yc2EAAAABIwAAAIEA1QI9wztc7ATLLz5E/jL7L PvQW5II77/1rzgl+ZMh1o6WenYK8pR2alntaRYHS/qTTxPYHfVBS2lG/VpUYoRXjm/wK22JctHjlVTHn dXCtolT0KGbK6AITDNTCWXMhDL555cbDmtsO8RiVE40x3newF3cFCmYpHCfrPw2sG47YNU='

The first time irun the comand, forget to delete VMs from thenodeandidk ifitwill havesomething to do.

Someonecouldtell methe problem I'mhaving andthe solution?

Thank you very much!
Hi,
you can't mix pve-versions in a cluster. Between 1.8 and 1.9 it can work, but 2.0 is completly different. Switch all nodes to pve2.0!

Udo
 

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!