question, you asking me to go to "main node" and try to add host3 or go host3 and add?
correct i been adding nodes was to add from the new node
this cluster has 11 nodes, this is the first i ran into this error
thank you for the reply (host3 is master node
New Node (emply no vms)
# pvecm add host2 -f
i remove it from host2
# pvecm delnode host3
when it fails. i run script on host3
root@host3:~# cat ./remove.sh
systemctl stop pve-cluster
systemctl stop corosync
no matter what i do or how many times i try to add node3 will not make a connection then i remove it re-add all the same justs hangs and have to remove it, matter a fact i tried to add and remove so many times that i made a script that will add.sh and remove.sh for me
1. Yes package versions...
I like to swap from public ip to private ip for the Cluster of nodes
for months i been waiting to swap that, both have public and private but noticed that cluster is node to node is using the public ip..
can i change, from public to private on all nodes and restart cluster and not restart...
i get this on only 1 VM while backing up, the others dont happen not sure why
INFO: starting new backup job: vzdump 110 --mode snapshot --compress lzo --mailnotification always --quiet 1 --mailto firstname.lastname@example.org --storage nfs-105
INFO: Starting Backup of VM 110 (qemu)
INFO: status = running...
sorry dont understand, i have added the new network details from the web cp, and i edit the network details within the container.. it boots up but just doesnt want to ping or get access online.
please keep in mind the old vm is from 3.4 and new system is running the latest 5.x proxmox, it boots...