Proxmox 4.3 Communication Problems

[axion.joey]

Hi,

We just created a new cluster using Proxmox VE 4.3. One node out of 11 randomly shows it's offline in the GUI. Here's the proxmox version information.

root@ProxmoxLV4:~# pveversion -v
proxmox-ve: 4.3-66 (running kernel: 4.4.19-1-pve)
pve-manager: 4.3-1 (running version: 4.3-1/e7cdc165)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-46
qemu-server: 4.0-88
pve-firmware: 1.1-9
libpve-common-perl: 4.0-73
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-61
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.1-6
pve-container: 1.0-75
pve-firewall: 2.0-29
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.4-1
lxcfs: 2.0.3-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80

Pings to that server never drop. How do I go about troubleshooting this error?

 

[mir]

network congestion makes multicast fail?

Best advise is to separate cluster communication on a dedicated network. If that is not possible then isolate cluster communication to a dedicated vlan.

 

[t.lamprecht]

Hi,

Pings to that server never drop. How do I go about troubleshooting this error?

you may try omping, which is ping over multicast.
https://pve.proxmox.com/wiki/Troubl...luster_issues#Diagnosis_from_first_principles

Test step 3 to 5 from the Diagnosis section.

If nothing comes up please post logs from the seemingly failing node:

journalctl -u corosync -u pve-cluster

would be interesting.