Search results

  1. S

    old timestamp - dead?

    It seems pxdev01 and pxdev02 are failing to start corosync. How can I fix it? Here is the results. * pxdev01 root@pxdev01:~# systemctl status pve-cluster corosync ● pve-cluster.service - The Proxmox VE cluster filesystem Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)...
  2. S

    old timestamp - dead?

    It seems no problem. Here is the results. When I moved the servers to My IDC. pxdev01 and pxdev02 was started at first. and pxmx01, pxmx02 and pxmx03 was started a few hours later. Was it a cause of the problem? * pcdev01 pxdev02 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev =...
  3. S

    old timestamp - dead?

    Sorry, it was not simultaneously. This is the results. * pxdev01 pxdev02 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.088/0.154/0.347/0.039 pxdev02 : multicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.093/0.161/0.355/0.044 pxmx01 : unicast...
  4. S

    old timestamp - dead?

    root@pxmx01:~omping -c 10000 -i 0.001 -F -q pxdev01 pxdev02 pxmx01 pxmx02 pxmx03 pxdev01 : waiting for response msg pxdev02 : waiting for response msg pxmx02 : waiting for response msg pxmx03 : waiting for response msg It seems it doesn't work. Is multicast necessarily required?
  5. S

    old timestamp - dead?

    I created a cluster that has 5 nodes. My local test was good. so I moved them to my production environment, but 2 nodes were removed from the cluster. How can I re-join them again? The two nodes are not active. pxdev01 and pcdev02 is running as standalone.