Orchestra 5.61.0 VM Doesn't Auto-Start in XCP-ng 8.2
kdm last edited by kdm
When I run XCP-ng (8.2), my XOA (5.61.0) appeared not to be auto-running. Auto-run is checked. On inspection of the XOA log, I can see that it does start, but then stops again about 10 minutes later.
*** EDIT: I think the log that it was stopping was me rebooting the server.
On reflection, it was simply never auto-starting. ***
xsconsole says XOA is "Unavailable". If I manually XOA from xsconsole, it runs perfectly well and keeps running.
Does anyone have any idea what's going on, or is there an enhanced log I can look at?
akurzawa last edited by
@kdm logs from XO
@akurzawa Indeed. The XO log is how I know it stops after 10 minutes. I'm hoping for a log which will tell me WHY it stops.
What do you mean exactly? What do you have in the XO logs?
@olivierlambert OKay. I've overcomplicated this.
XOA does not auto-run. I must start it manually from xsconsole.
Once running, it runs fine.
It is set to auto-run.
In the logs, all I can see is when XOA starts up (manually) and when it shuts down (by me shutting down XCP-ng).
Try to disable/re-enable autostart then.
@olivierlambert I don't get it. I've rebooted about 12 times in the last few days and the effect was repeatable and very predictable. Tonight, I installed an additional VM in order to see if it would autostart and .... (drum roll) they BOTH autostart. Despite my not having taken any specific action on my XOA instance.
n the logs, all I can see is when XOA starts up (manually) and when it shuts down (by me shutting down XCP-ng).
So for the instance where it stops be itself there is nothing in the XOA log? It starts with the host and then stops after 10 minutes every time or some random time?
@tony The log showed a record of it stopping. on reflection, I think that was probably me rebooting the server, though. I don't believe it actually ever started itself. (Not even the first time after it was installed.)
Either way, It started working after I created a second VM. It's entirely possible that the suggestion of switching auto start off and on again would have fixed it.