XO and Debian10
I have installed XO from source on Debian9. After upgrade to Debian10, it started complaining abour leveldown NPM module and does not start.
Is Debian10 supported or only Debian9 for now?
How did you installed XO? Following our official doc? https://xen-orchestra.com/docs/from_the_sources.html
If you didn't, it's probably the issue: Node must be installed separately and not via the Debian package manager. In your case, I suppose your upgrade also upgraded Node to an unsupported version.
Yes, it was installed via the gitbook. I will check again for node.
I get the same problem but with a fresh install. With Debain 9.9. it was okay. Netinstall with ssh server nothin g elese. Than install with apt-get install curl. and using the script. Everyting is running fine.
Same Way with 10.0 no web interface, and i cant find a error in th bash ..
looking mostly the same like 9.9
I hope i can try it next time again ..
@axel which script? There's no script, just a small procedure to follow in our doc.
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh | bash
@axel this is not the "official" way...
This is the official way: https://xen-orchestra.com/docs/from_the_sources.html
Indeed @axel if you have an issue with this 3rd party script, you must report it to the people who did the script, here: https://github.com/Jarli01/xenorchestra_installer/issues
We can't monitor what's in a 3rd party script and if it follows our doc, that can change depending on what's added/removed in XO.
For a turnkey solution, you have XOA, at least to compare to a manual install and see if the issue comes from your environment or a real XO bug: https://xen-orchestra.com/#!/xoa
Danp last edited by
@axel I just ran the installation script on a Debian 10 VM and it worked as expected.
Even when using the "official" way, sometimes the installation can fail due to things like --
- issues with recent commit to github repo
- issues with upstream dependency
This is why the pre-built XOA appliance exists.
Feel free to open an issue over on the script's Github repo if you continue to encounter issues.