Join information greyed out in 6.4.8 cluster

[Tmanok]

Hi Everyone,

My cluster doesn't allow me to look at join information... I've recently lost a node (RAID controller failure) so I reinstalled using HBA, but I can't join the "new" node to the cluster? The cluster's join information is greyed out... See screenshot. Thanks.


*Update*: No comments yet... Both nodes in the cluster (the Node1 G6 and Node2 G7 in this case) have this same cluster screen. DL380G6 experienced the failed controller. They are of course on the same network and can easily ping each other, but the trouble is that they won't give me the join information.

Tmanok

 

[Moayad]

Hi,

Please post the output of:

pvesh get /cluster/config/join
cat /etc/pve/corosync.conf
pveversion -v

 

[Tmanok]

Uh oh... I can update but this cluster has hardly been touched. The two issues I've experienced is one node's storage controller dying, and one node has had some crashes (I'm not sure what the cause is, thinking Mobo or CPUs).

hostname lookup 'DL380G6' failed - failed to get address info for: DL380G6: Name or service not known

root@DL360G6:~# cat /etc/pve/corosync.conf
logging {
  debug: off
  to_syslog: yes
}


nodelist {
  node {
    name: DL360G6
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 192.168.75.140
  }
  node {
    name: DL360G7
    nodeid: 2
    quorum_votes: 1
    ring0_addr: 192.168.75.150
  }
  node {
    name: DL380G6
    nodeid: 3
    quorum_votes: 1
    ring0_addr: 192.168.75.160
  }
}


quorum {
  provider: corosync_votequorum
}


totem {
  cluster_name: Seaflora
  config_version: 3
  interface {
    linknumber: 0
  }
  ip_version: ipv4-6
  link_mode: passive
  secauth: on
  version: 2
}

root@DL360G6:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.119-1-pve)
pve-manager: 6.4-8 (running version: 6.4-8/185e14db)
pve-kernel-5.4: 6.4-3
pve-kernel-helper: 6.4-3
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-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.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

 

[Moayad]

Thank you for the output.

hostname lookup 'DL380G6' failed - failed to get address info for: DL380G6: Name or service not known

Please can you confirm if the hosts/hostname file in DL380G6 is correct? also the IP address

 

[Tmanok]

Thank you for the output.


Please can you confirm if the hosts/hostname file in DL380G6 is correct? also the IP address

Well it is correct, but the node is dead remember? So why does this interrupt sharing join information where there is still a quorum? Seems like a flaw in the design.

Tmanok

 

[Tmanok]

To anyone else, I did not resolve this. Ended up reinstalling on a new node after backing up all of my VMs and CTs.