[SOLVED] link0: cannot use IP '10.10.1.1', not found on local node!

[BEElieve]

Hey.
Im running out of ideas on how to re-add a node to my existing cluster.
This node was previously part of the cluster, but i had to temporarily use the server elsewhere.

Ive reinstalled proxmox but i just cant add it to the cluster (with 2 other nodes) anymore.

As far as i can tell the two existing nodes both have two networks.

A seemingly inactive separate cluster network in 10.10.1.0/24
And the actually used network in 10.1.0.0/16

The nodes corosync.conf

logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: pve2
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 10.10.1.2
    ring1_addr: 10.1.1.78
  }
  node {
    name: pve3
    nodeid: 3
    quorum_votes: 1
    ring0_addr: 10.10.1.3
    ring1_addr: 10.1.1.79
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: xxxxx
  config_version: 10
  interface {
    linknumber: 0
  }
  interface {
    linknumber: 1
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

But they dont use the 10.10.0.0 network. They cant even reach each other there.


Nonetheless i configured my new node exactly the same. It can communicate with them in the 10.1.0.0 network and i created the 10.10.0.0 network the same way its configured for the cluster nodes (just an ip in cidr and active is no)

Naturally everytime i try to join the cluster i get this:

detected the following error(s):
* link0: cannot use IP '10.10.1.1', not found on local node!

TASK ERROR: Check if node may join a cluster failed!


Does anyone have any ideas?
Any help is much appreciated

 

[jsterr]

Please post /etc/hosts and /etc/network/interfaces of one cluster node and the node you want to add.

 

[BEElieve]

Please post /etc/hosts and /etc/network/interfaces of one cluster node and the node you want to add.

cluster node:

127.0.0.1 localhost.localdomain localhost
10.1.1.78 pve2.my.domain.de pve2

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

auto lo
iface lo inet loopback

iface eno1 inet manual

iface ens6f0 inet manual

iface ens6f1 inet manual

iface eno2 inet static
    address 10.10.1.2/24

auto vmbr0
iface vmbr0 inet static
    address 10.1.1.78/16
    gateway 10.1.1.201
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

lonely node:

127.0.0.1 localhost.localdomain localhost
10.1.1.77 pve1.my.domain.de pve1

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet static
    address 10.10.1.1/24

auto vmbr0
iface vmbr0 inet static
    address 10.1.1.77/16
    gateway 10.1.1.201
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0

 

[jsterr]

cluster node:

127.0.0.1 localhost.localdomain localhost
10.1.1.78 pve2.my.domain.de pve2

Please edit all /etc/hosts (of all nodes) to:

10.1.1.77 pve1.my.domain.de pve1
10.1.1.78 pve2.my.domain.de pve2
10.1.1.79 pve3.my.domain.de pve3

and then try again

 

[BEElieve]

Please edit all /etc/hosts (of all nodes) to:

10.1.1.77 pve1.my.domain.de pve1
10.1.1.78 pve2.my.domain.de pve2
10.1.1.79 pve3.my.domain.de pve3

and then try again

Sadly nothing changed

 

[jsterr]

Sadly nothing changed

On command line can you ping each node from each other? Can you share a screenshot of your join- fingerprint (join information dialog)?

EDIT: Hmm seems like your eno2 has no auto startup. Is eno2 up? What does ip a tell you? You need to autostart eno2 on boot (can be done via gui or cli by adding auto eno2 one line above iface eno2 ....

 

[BEElieve]

On command line can you ping each node from each other? Can you share a screenshot of your join- fingerprint (join information dialog)?

EDIT: Hmm seems like your eno2 has no auto startup. Is eno2 up? What does ip a tell you? You need to autostart eno2 on boot (can be done via gui or cli by adding auto eno2 one line above iface eno2 ....

THANK YOU!

Jesus christ. It was really the fact that eno2 was not up. Having it pretend to be up let me finally join the cluster.