Connection failed - Unknown error
-
Under Settings, I have an exclamation red triangle next my non-master host in my pool as shown in the picture below. When I click on it, a popup says Unknown error. I don't see anything unusual in /var/log/daemon.log. I've tried Disabling/Enabling the host but no joy. Has anyone seen this before?
TIA,
Brad
-
@bradmbreer You only need to connect to the pool master. XO will find the other hosts in the pool. If you connect to a non-master, XO will be redirected to the master. If you connect to other hosts in the pool (after the master) it will just give an error. Just ignore the error connecting to other hosts in the same pool.
-
@Andrew thank you
-
B bradmbreer marked this topic as a question on
-
B bradmbreer has marked this topic as solved on
-
@bradmbreer and @Andrew
Thank you for clearing up why I see the red triangle on all my hosts that are not masters.
I wonder whether the developers will hide this little blemish in their next version. It is unsettling to a recent XCP-ng/XO user like me. -
Hi,
In theory, when you connect to a pool member while you already are connected via the master, you should have an error message. And when you add a host to a pool, the old connection should be removed.
So I wonder how you could end in this situation "silently" (ie without any warning)
-
@olivierlambert Thank you for your response.
I have followed most of the documentation on setting up HA, and made sure that I have 3 hosts. All are Dell 7090 64GB RAM with 2 dedicated HA NICS. XCP-ng 8.3 is patched, XO is up to date, Xen tools 9.4.0 on all Windows VMs, and using the Xen tools ISO that can be mounted.
eth0 1Gbs management network
eth1 10Gbs iSCSI network DAC
eth2 10Gbs VLAN Trunk, including backup network
eth3 1Gbs HA
eth4 1Gbs HAOverall, XCP-ng and XO are doing an excellent job. I feel like I am on an Easter egg hunt when pouring through documentation, but that is mostly my problem, because I see that you have put a lot of effort into organizing and updating it.
My "use case" is replacing the VMware ESXi/vSphere 2-node cluster with XCP-ng and XO at the small high school (non-profit) where I volunteer as the IT guy. I feel that I am at the point where I trust XCP-ng and XO enough to make the switch during the summer break.
Sorry to run on. The yellow triangles behind the non-master hostnames are just a small nuisance. I do notice that the hosts are hard to shutdown. Sending a shutdown command from either XO or from the host console causes a host to reboot, but not shutdown, even after having previously entered maintenance mode. I feel that this is not a big issue, just another small nuisance. The XO cluster is maintaining the integrity of the guest VMs.
I will be reading all of the documentation I can, and upgrading to 8.4 when it is available. Thank you for supporting your awesome hypervisor.
