Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
@FATeknollogee said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
Just curious, why this guide uses Ubuntu & not Debian like the XOA appliance?
btw, is this the latest guide?
This works on debian as well.
-
Script is broken on Ubuntu 16.10 due to missing package (libpng12-dev).
FWIW, the original instructions call for libpng-dev.
-
@scottalanmiller there is the bat signal...
-
@Danp A simple change to the script, I'll build a clean install today (assuming it's not a mad-house here) and test with a new script.
-
Script updated and working.
See the OP for installation instructions.
-
@DustinB3403 Those changes were made to your fork. I believe everyone is pulling from Scott's repository.
-
@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@DustinB3403 Those changes were made to your fork. I believe everyone is pulling from Scott's repository.
Thank you, just noticed.
Updated the source.
-
Still needs to be updated for the new file restore feature to work.
-
@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
Still needs to be updated for the new file restore feature to work.
On Ubuntu? I don't have anything connected to this system yet, will check in a bit.
-
@DustinB3403 On any install. There are additional packages required (libvhdi-utils and fuser, IIRC).
-
And on Ubuntu 16.04, there's an older version of libvhdi-utils in the repository, so you can just apt-get the library.
-
ok I've manually install vhdiutils-lib, checking for fuser
-
Fusermount is installed to Ubuntu 16.10 by default.
Only need to install libvhdi-utils and then we should be good.
Building a clean system now with a sample file.
-
Does anyone know the correct version of node and npm we should use?
I have installed Ubuntu and when I run the script it freaks out when it gets to the sudo npm run build... My first attempt was on Debian 8 and it also freaked out at that step...
I see that we install node ver 5 but when n stable runs it gets upgraded to v7.4, so I tried skipping n stable but no luck
-
@brandon I recently tested the script on Ubuntu Server 16.10 and it worked fine. Post the error shown so that we can see what is happening.
There is one known issue that you will need to deal with unless you build with the next-release branch.
-
-
@DustinB3403 Here is my error:
index generated src/common/intl/locales/index.js
[16:01:46] Using gulpfile /opt/xo-web/gulpfile.js
[16:01:46] Starting 'build'...
[16:01:46] Starting 'buildPages'...
[16:01:46] Starting 'buildScripts'...
[16:01:46] Starting 'buildStyles'...
[16:01:46] Starting 'copyAssets'...
[16:01:51] 'buildStyles' errored after 5.51 s
[16:01:51] Error: ENOENT: no such file or directory, scandir '/opt/xo-web/node_modules/node-sass/vendor'
at Object.fs.readdirSync (fs.js:871:18)
at Object.getInstalledBinaries (/opt/xo-web/node_modules/node-sass/lib/extensions.js:122:13)
at foundBinariesList (/opt/xo-web/node_modules/node-sass/lib/errors.js:20:15)
at foundBinaries (/opt/xo-web/node_modules/node-sass/lib/errors.js:15:5)
at Object.module.exports.missingBinary (/opt/xo-web/node_modules/node-sass/lib/errors.js:45:5)
at module.exports (/opt/xo-web/node_modules/node-sass/lib/binding.js:15:30)
at Object.<anonymous> (/opt/xo-web/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
[16:01:51] 'build' errored after 5.53 s
[16:01:51] The following tasks did not complete: buildPages, buildScripts, copyAssets
[16:01:51] Did you forget to signal async completion?npm ERR! Linux 4.2.0-16-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v7.4.0
npm ERR! npm v4.0.5
npm ERR! code ELIFECYCLE
npm ERR! xo-web@5.5.3 build:npm run build-indexes && NODE_ENV=production gulp build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the xo-web@5.5.3 build script 'npm run build-indexes && NODE_ENV=production gulp build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the xo-web package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run build-indexes && NODE_ENV=production gulp build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs xo-web
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls xo-web
npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request:
npm ERR! /opt/xo-web/npm-debug.log -
Did you run the installer as root?
-
@DustinB3403 Yes I did: sudo su, sudo ./script
-
@DustinB3403 Should I install 16 lts?
