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 Thank you all for your guidance :) On 18 December 2016 at 14:10, Tom <[email protected]> wrote: > Change reverted. > > A friend pointed this out to me: Dec 18 13:53:53 kappa corosync[7047]: > [VOTEQ ] flags: quorate: Yes Leaving: No WFA Status: No First: No Qdevice: > No QdeviceAlive: No QdeviceCastVote: No QdeviceMasterWins: No > > Unsure though, I have pastebinned the syslog from zeus from startup to > when the cluster tick goes to green below: > https://paste.ee/p/ybuBv#op2dyxxtu9MPFRVTDFuQT02pS69K5iFb > > Thanks > > > On 18 December 2016 at 13:49, Dietmar Maurer <[email protected]> wrote: > >> > Tried adding the token thing to the config, no change. >> >> Please revert that change. It makes no sense to fix things which are >> already working ;-) >> >> Is there any hint in /var/log/syslog? >> >> _______________________________________________ >> pve-user mailing list >> [email protected] >> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user >> > > _______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
