As XOA, after the update to version 5.56.2 pretty soon stopped working properly (can't change Servers but also can't see any errors as it doesn't list them), I tried to reboot the VM but didn't find a reboot button.
Didn't I find it or is there really no option on the webinterface to reboot XOA?
If not: This is a feature request! (could probably be inside the update menu)
@cg You are aware that XOA is just a VM that you can reboot.
As a matter of fact, I did it this morning (even halted it for maintenance).
Of course it's weird since you are "killing" the interface you are currently using.
@cg if you have an issue like this, a good reflex is to create a support ticket and open a support tunnel
@jedimarcus smart guy. Now if I only have access to the Server via XCP-ng - how do I reboot it?
I also didn't find out how to reboot the whole server from inside XOA, if the server is the only one. XOA denies restart, as there is a VM running (which is XOA itself). Is there any trick?
@cg You can manipulate the system and its VMs via the CLI by SSHing into the server and issuing
To reboot a single server, switch to the host's Advanced tab and then click the Force Reboot button.
@danp It would be good if XOA could handle that more smartly. XenCenter e.g. shows which VMs are still running (and being an issue for updates). I guess XOA could extract that infos, too and by that could find out it's the only VM running.
To make it safe it could have a dialog asking if you're sure you want to reboot as XOA can't be migrated to any other server and if autostart isn't activated it could leave the server 'dead'.
Just force reboot the host, it will shutdown VMs, reboot the host, and then boot XO VM if it got auto start enabled
@olivierlambert it turned out that the XCP-ng host was f*cked up. Whyever: About after the update of XOA and the reboot of the VM probably XCP-ng was going postal.
I noticed a bunch of weird IP addresses blocking my DHCP range and couldn't access the VM even via direct console: It didn't accept the root password.
I shut the whole host off manually and after reboot XOA and XPC-ng are working again.
Are you interested in some logfiles (dunno if there could be anything interesting)?
Probably the host got stuck somehow and that made XOA hung on trying to gather infos.
It's hard to tell. Let's say next time it happens please report