Search results

  1. V

    Join cluster failed, how to solve

    I tried to join an existing cluster with a new node. The main IP of the nodes is different from the ip/subnet that the existing nodes should communicate on. I forgot to specify the -link0 <ip> parameter and even though joined the cluster. It kept waiting on "waiting for quorum" so I stopped this...
  2. V

    [SOLVED] Can't get corosync up after joining 2 new nodes

    I joined an existing cluster with 2 (I think) identical servers. First one I joined using 'pvecm add 192.168.1.66'. This one joined well, although I still have some strange problem using migrations (live migration tries to use the primary ip 10.1.51.41 of the new node to transfer, but this IP...
  3. V

    Adding swaps leads to corrupted file system, what is wrong?

    Yesterday I experienced a big data crash on one of my Proxmox nodes. Almost all VM's corrupted and not working anymore. It was an awful day recovering data and accepting some data loss. I'm worried something like this happens again and I hope someone can tell me what went wrong and/or what to...
  4. V

    Irrelevant packets as present for every VM on proxmox-host

    My network has some issues. When the network traffic increases, the network connections tend to be very slow even though it's an 10GB network. I'm not sure whether it's proxmox-related or not. Example: VMx = virtual machine x VHx = proxmox virtual host x VM1 = 192.168.0.51 (E2:A9:CC:75:79:AF)...
Top Bottom