[SOLVED] Cluster is functioning properly but showing all nodes as OFFLINE on web GUI

madyoda

New Member
Dec 18, 2016
2
0
1
33
Hello all,

I'm sure you've all come across this issue before. I just managed to setup a Proxmox 4.4.1 cluster (pve-manager/4.4-1/eb2d6f1e (running kernel: 4.4.35-1-pve)) and everything seems to be working perfectly. There is quorum, all nodes see each other, they communicate fine (omping), the only storage is 'local' (/var/lib/vz) and no errors are being thrown (in syslog, etc).

My problem comes to the web GUI, where all nodes show offline (see: http://i.imgur.com/OIpgX5w.png ). On the Datacenter -> Summary page, proxmox shows everything as okay (see: http://i.imgur.com/hp99UxA.png ) but the nodes as 'offline' and it reflects below (see: http://i.imgur.com/kSaYkLc.png )

VM's are running perfectly on the 'kappa' node as I had them all on there before, but as the nodes are showing offline I cannot create a new VM as it tells me the specified node is offline.

If I navigate to the 'zeus' web panel, everything above is reflected apart from it showing the 'zeus' server IP address as apposed to the 'kappa' IP address (see: http://i.imgur.com/b9C0ZE6.png ) (note: both IP's start in 3 but they *are* different, just blurred)

I've been through google, restarted pvestatd, pve-cluster, corosync, etc multiple times but no avail.

Does anyone have any solutions/pointers?

Thanks in advanced :)
 
Apologies, I forgot to click the post reply button on this.
I managed to solve it:

Alright, finally managed to fix it.

The problem was to do with hosts, as I was using a local 10.10.10.x VPN (I am using two OVH nodes), because I cannot multicast over the public network. By adding a few more entries in /etc/hosts (thanks to step 4 of this guide: https://forum.ovh.co.uk/showthread.php?7071-Poor-man-s-Proxmox-cluster-with-NAT ) and giving zeus a kick, they are now clustering perfectly and both showing online.

To show it better, here's a screenshot from before: https://i.imgur.com/kSaYkLc.png - you can see the IP for kappa starts with 3 which is my public IPv4.
Once fixed, it's now showing the following: http://i.imgur.com/Wbi7zqG.png which is now 100% working​