Closed NavCC closed 3 years ago
Hi,
There was some changes related to importing those hooks (lines in service log that prevent it from starting) in xen orchestra repo around the time you encountered this. Due to active development happening there, it's possible that from time to time the build against master branch fails, which seems to be the case here. Nothing i can do about that unfortunately.
Did a clean install on Ubuntu 20.04 just now and worked fine. Could you try again and let me know how it goes.
Hello @ronivay
I Did another clean install of Ubuntu 20.04 yesterday, updated and followed same procedure and everything installed without an issue. Just bad timing on my part. Would it be possible for your script to check if the master branch is passing or failing at the time and perhaps warn during the procedure? Looking at https://github.com/vatesfr/xen-orchestra the build is currently failing again.
Thanks for fast response, and I love the script keep up the great work.
Hi,
Happy to hear that, thank you. It might be possible to check that information, but my fear is it might be unreliable. IIRC that travis status has been failing even when actual build from sources is still successful.
I'd rather try to make this fact more clear in script output/readme that there are moments when build simply doesn't work due to development happening in master branch. I'll look into that when i have a moment, closing this now.
OS Version: Ubuntu 20.04 LTS Node.js version: v14.16.1 Yarn version: 1.22.10
Server specs 4v Cores ( Normally two when operational ) 12GB RAM 20GB Storage
Issue Was unable to update to version 5.57 of XO via the script.
stderr: ' Logical volume ubuntu-vg/ubuntu-lv contains a filesystem in use.\n'
Can't deactivate volume group "ubuntu-vg" with 1 open logical volume(s)
Got a few other errors also, so decided to play around with Yarn and Node.js versions to no avail.
Installation logfile
Same output as below only 57 Lines.
Please let me know if you require any additonal information.