Recent content by Ivan Gonzalez

shoot you maybe right, having it checked now

Hello, yes i have try that as well both host file and ip... the results are the same :(

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

correct, new node with no VM thats the server you login and join with existing but thats what i been doing and getting that error.

any help will be great, thanks

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 pmxcfs -l rm /etc/pve/corosync.conf rm...

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...

says "lzop: No space left on device: <stdout>" but is on 24TB storage device and all other backups are fine, is just 1 KVM that just wont backup! any help will be great

bump, still getting this INFO: starting new backup job: vzdump 110 --mailto ivanjr@xx --compress lzo --mode snapshot --mailnotification always --storage nfs-105 --quiet 1 INFO: Starting Backup of VM 110 (qemu) INFO: status = running INFO: update VM 110: -lock backup INFO: VM Name: CID203-PBX...

Bump

main proxmox df -i

I have all the backups going to NFS

I see, maybe node what you do to fix ?

I know, which is why I'm very confused.