Search results

In my case this was a trick. Thanks.

One day I found somewhere this walkthrough and since then use it when my cluster suddenly broke apart by adding a new node. Hope it would help you.

The problem was in misconfigured shorewall on the host. I found incorrect setting by using tcpdump. The problem is solved.

I have a server with Proxmox 6. It was set up a couple of months ago. Everything looked fine. But yesterday I noticed that I couldn't update neither containers nor virtual machines with OS Linux. Both command apt update (in debian) and yum update (in centos) return errors like "Could not connect...

After some investigations I managed to manually removed a bad node from the cluster. (I took the steps from the section "Separate A Node Without Reinstalling" of the official guide). But when I tried to join this node to the cluster again (now via command line), I faced with "waiting for...

Thank you for your help. Could you please tell me how to manually remove the bad node from the cluster? Or give me a link to the guide. Because it's impossible to remove it using GUI. I googled the official guide with that instructions. But it would be difficult to power off the node because it...

My working cluster consisted of 2 nodes. When I was adding the third node something went wrong. The process wasn't finished and just timed out. When I started to investigate possible reasons of such unexpected result, I noticed that I made a mistake while adding a new node to /etc/hosts file on...