Joining a cluster fails

[SteveT1970]

Hi all

I have two fresh machines installed with the latest Proxmox and updated.

pve1 - 192.168.1.10
pve2 - 192.168.1.11

On pve1 I used the GUI to create a cluster. I then moved to pve2 and initially used the GUI to add pve2 to the cluster. This failed so I tried the command line and received the same error message. The thing is, the error doesn't make sense

root@pve2:/etc/network# pvecm add pve2.23wwc.io
detected the following error(s):
* local node address: cannot use IP '192.168.6.2', it must be configured exactly once on local node!

Check if node may join a cluster failed!

My network is 192.168.0.0/21 so 192.168.6.2 is a valid address but I have no idea why it's appearing here unless pve2 picked up that address from DHCP during the install - I set the IPs manually during the install process.

Either way, I can't get this message to go away. I've even tried greping the entire hard disk for 192.168.6.2 and found nothing. Googling for "local node address: cannot use IP " and/or "it must be configured exactly once on local node!" finds one person who experienced this error but not for same reason and the actual source code the generates this message but I didn't find a solution.

Can anyone help me make this message go away or do I need to do a reinstall?

Thanks

Steve

 

[dietmar]

What is the output of (on pve2)

# ip address show up

 

[SteveT1970]

Hi,

It's what you'd expect

root@pve2:~# ip address show up
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether a8:20:66:11:3d:4c brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether a8:20:66:11:3d:4c brd ff:ff:ff:ff:ff:ff
inet 192.168.1.11/21 brd 192.168.7.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::aa20:66ff:fe11:3d4c/64 scope link
valid_lft forever preferred_lft forever


root@pve2:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp2s0f0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.11
netmask 21
gateway 192.168.1.1
bridge-ports enp2s0f0
bridge-stp off
bridge-fd 0

 

[dietmar]

Please can you also post the data for the other node?

 

[SteveT1970]

root@pve1:~# ip addr show up
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether a8:20:66:28:f6:4f brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether a8:20:66:28:f6:4f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.10/21 brd 192.168.7.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::aa20:66ff:fe28:f64f/64 scope link
valid_lft forever preferred_lft forever


root@pve1:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp1s0f0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.1.10
netmask 255.255.248.0
gateway 192.168.1.1
bridge_ports enp1s0f0
bridge_stp off
bridge_fd 0

 

[dietmar]

And what is the content of /etc/hosts - maybe the IP is configured there?

 

[SteveT1970]

That was it. Still have no idea how it got there though!

Thanks

 

[florian-n]

I had the same issue. It is the case if you change the ip-addresses of your node after the initial wizard run (where the hosts-file seems to be set).