Search results

  1. Node3 will not cluster

    shoot you maybe right, having it checked now
  2. Node3 will not cluster

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

    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
  4. Node3 will not cluster

    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.
  5. Node3 will not cluster

    any help will be great, thanks
  6. Node3 will not cluster

    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 ./ systemctl stop pve-cluster systemctl stop corosync pmxcfs -l rm /etc/pve/corosync.conf rm...
  7. Node3 will not cluster

    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 and for me 1. Yes package versions...
  8. Cluster Node to Node IP

    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...
  9. ERROR: vma_queue_write: write error - Broken pipe

    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
  10. ERROR: vma_queue_write: write error - Broken pipe

    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...
  11. ERROR: vma_queue_write: write error - Broken pipe

    I see, maybe node what you do to fix ?
  12. ERROR: vma_queue_write: write error - Broken pipe

    I know, which is why I'm very confused.
  13. ERROR: vma_queue_write: write error - Broken pipe

    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 --storage nfs-105 INFO: Starting Backup of VM 110 (qemu) INFO: status = running...
  14. Question openvz to ltc (networking failing)

    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...
  15. Question openvz to ltc (networking failing)

    Correct, i have re added the network config but will not come up some reason will not ping


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 your own in 60 seconds.

Buy now!