[SOLVED] Wrong IP when adding a node to a cluster

davi_sehn

New Member
Nov 19, 2020
7
0
1
Hi, I'm new on proxmox and its communitty, and I faced an error that i couldn’t solve.

The error is that when I'm copying the information to join the cluster I created, the node IP "changes" from *.*.*.12 to *.*.*.175.
When I try to connect to the node with this information I get this message:
detected the following error(s):
* local node address: cannot use IP '*.*.*.174', not found on local node!

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

and I don't know what to do! Can someone please help me?
 
Hi, here is the network configs (ip a):

root@pve2:~# ip a
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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
link/ether 6c:3b:e5:51:09:fc brd ff:ff:ff:ff:ff:ff
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 6c:3b:e5:51:09:fd brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 6c:3b:e5:51:09:fc brd ff:ff:ff:ff:ff:ff
inet 10.1.1.12/24 brd 10.1.1.255 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::6e3b:e5ff:fe51:9fc/64 scope link
valid_lft forever preferred_lft forever

and when I tried to join the cluster via CLI I got the exact same error message.

NOTE: I do have some VMs on the cluster's node (10.1.1.12), but I have none in the node I'm trying to connect to the cluster.
 
Last edited:
Hi again,

Please post output of cat /etc/network/interfaces and pveversion -v for both nodes
 
Ok, here are the outputs from pve2 (10.1.1.12, the node I created the cluster on):

Code:
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 eno1 inet manual

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.1.1.12/24
        gateway 10.1.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0


Code:
root@pve2:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1



and here are the outputs from pve (10.1.1.10, the node I was trying to join the cluster):

Code:
root@pve:~# 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 eno1 inet manual

iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.1.1.10/24
        gateway 10.1.1.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0


Code:
root@pve:~# pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
 
Last edited:
Hi,

Please post output of cat /etc/hosts on both node, and consider to upgrade your PVE nodes to the current version.
 
Hi, here's the output from pve2:

Code:
root@pve2:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
10.1.1.175 pve2.gpssat.com.br 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

and here's the output from pve:

Code:
root@pve:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
10.1.1.174 pve.gpssat.com.br pve

# 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

I just upgraded both nodes, as you said. Now they're on version 6.2-15.
 
Last edited:
But I didn't change the IPs. Nor did my superior. Is it something that can occur automatically??


Should I change the 10.1.1.174 and 10.1.1.175 IPs on /etc/hosts to the original IPs, respectively, to 10.1.1.10 and 10.1.1.12?

Edit: I think the IPs changed because of the DNS service, but I'm not sure.
 
Last edited:
Should I change the 10.1.1.174 and 10.1.1.175 IPs on /etc/hosts to the original IPs, respectively, to 10.1.1.10 and 10.1.1.12?
Yes IPs in /etc/hosts file should be same original IP, so please edit your /etc/hosts file and change to 10.1.1.10 and 10.1.1.12.
afterwards do hostname --ip to be sure that your IP has changed.
 
  • Like
Reactions: davi_sehn
Glad to help!

Please mark the thread as [SOLVED] to help other people who have the same issue Thanks!

have a nice weekend :)
 
  • Like
Reactions: davi_sehn

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!