Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
@DustinB3403 Okay will be a clean server install so the script will install everything needed?
-
@brandon it should.
-
@brandon said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@DustinB3403 Yes I did: sudo su, sudo ./script
To ensure that you are using the most recent version of the installation script, it is recommended to install using --
sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash -
@Danp Hi Danp I tried to use the script but the new Ubuntu server is just so unstable... Cant install anything then apt crashes and I have to run dpkg --configure -a , while running the script it will randomly stop and say Killed... Busy running the script manually I am currently busy with sudo npm install and npm run build in the ox-server dir. Will give an update if the install is successful or not.... Why is the new Ubuntu such a pain? I use Xubuntu 14.04 as my main driver at home and work and I haven't had any real problem besides the wallpaper reverting back after every reboot but that was minor.
-
Okay so I dont even get as far anymore keep getting "Killed" when I run "sudo npm install" in the xo-server dir...
root@xenorc:/opt# git clone -b stable https://github.com/vatesfr/xo-server
Cloning into 'xo-server'...
remote: Counting objects: 10478, done.
remote: Compressing objects: 100% (59/59), done.
remote: Total 10478 (delta 31), reused 0 (delta 0), pack-reused 10419
Receiving objects: 100% (10478/10478), 2.71 MiB | 959.00 KiB/s, done.
Resolving deltas: 100% (7503/7503), done.
Checking connectivity... done.
root@xenorc:/opt# git clone -b stable https://github.com/vatesfr/xo-web
Cloning into 'xo-web'...
remote: Counting objects: 26052, done.
remote: Compressing objects: 100% (81/81), done.
remote: Total 26052 (delta 33), reused 0 (delta 0), pack-reused 25968
Receiving objects: 100% (26052/26052), 9.20 MiB | 1.41 MiB/s, done.
Resolving deltas: 100% (17340/17340), done.
Checking connectivity... done.
root@xenorc:/opt# cd xo-server
root@xenorc:/opt/xo-server# sudo npm install
^[[B[ ..] - extract:lodash: verb gentlyRm don't care about contennpm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g[email protected] install /opt/xo-server/node_modules/argon2
node-gyp rebuildKilled
-
Hi Everyone
Okay installed Debian 7.8, Installation gave me a lot less problems than Ubuntu 16.10, the installation wasn't successful....
Here is the complete installation output of xo-server and webxo-server : http://pastebin.com/yH0MRFpJ
xo-web: http://pastebin.com/XVxXs9gf
Here is my error:
root@xen-orcha:/opt/xo-web# sudo npm run build
[email protected] build /opt/xo-web
npm run build-indexes && NODE_ENV=production gulp build[email protected] build-indexes /opt/xo-web
index-modules --auto srcindex generated src/common/intl/locales/index.js
[13:27:41] Using gulpfile /opt/xo-web/gulpfile.js
[13:27:41] Starting 'build'...
[13:27:41] Starting 'buildPages'...
[13:27:41] Starting 'buildScripts'...
[13:27:41] Starting 'buildStyles'...
[13:27:41] Starting 'copyAssets'...
[13:27:47] Finished 'buildPages' after 6.7 s
[13:27:53] Finished 'buildStyles' after 12 s
[13:27:54] Finished 'copyAssets' after 14 s
Killednpm ERR! Linux 3.2.0-4-amd64
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! [email protected] build:npm run build-indexes && NODE_ENV=production gulp build
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the [email protected] 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.logDoes anyone know what to do?
-
Brandon it looks like you're trying to run the manual installation. Which I haven't updated those instructions in some time.
Use the installation script at the very top of the first post.
-
@DustinB3403 Hi DustinB3403, I am copy and pasting from the installation script?
wget https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh -
@brandon said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:
@DustinB3403 Hi DustinB3403, I am copy and pasting from the installation script?
wget https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.shAnd are you running the script by
chmod +x xo_install.shand then running./xo_install.sh? -
@DustinB3403 At first I did "sudo su" then chmod 777 xo_install.sh and then sudo ./xo_install.sh script ran and bugged out so I tried copied and paste everything into the terminal
-
@DustinB3403 Debian 7.8 has gotten the closes to installing, Debian 8, Ubuntu 15 and 16 didn't get this far before giving errors
-
@brandon Assuming you still have the Ubuntu 16.10 VM you were working on before.
Did you install curl and bash?
If so did you try this exact command?
sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash -
@DustinB3403 Yes I did I can run it again if you like but it will fail
-
I'm troubleshooting some other things for work at the moment. Please create a new post, list what OS you're using and we can proceed from there.
if you connect to the vm with SSH can you log everything into a text file and post it so we can investigate from there.
-
@DustinB3403 Okay I have two VM's Debian 7.8 and Ubuntu 16.10 both are clean installs the only thing I did before running the scripts were apt-get update and upgrade... I removed Ubuntu 15 and Debian 8
The previous error was from Debian 7.8...
I just ran sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash as the root user on Ubuntu will copy and paste the output as soon as it is done, it looks like the script is at npm install & rebuild part in the xo-server dir
-
@brandon Using putty on windows you can have it output everything into a log file so you don't have to try and scroll for the info.
-
@DustinB3403 Haha sorry I don't use Windows... but will log the output
-
@brandon Well, any output tool works.
That was just the first tool to pop to mind.
-
Okay after running the script this is what happened:
root@xenorc:/opt# sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1146 100 1146 0 0 604 0 0:00:01 0:00:01 --:--:-- 604
Reading package lists... Done
Building dependency tree
Reading state information... Done
nfs-common is already the newest version (1:1.2.8-9.2ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.Installing the NodeSource Node.js v6.x repo...
Populating apt-get cache...
- apt-get update
Get:1 http://security.ubuntu.com/ubuntu yakkety-security InRelease [102 kB]
Hit:2 http://za.archive.ubuntu.com/ubuntu yakkety InRelease
Get:3 http://za.archive.ubuntu.com/ubuntu yakkety-updates InRelease [102 kB]
Hit:4 https://deb.nodesource.com/node_6.x yakkety InRelease
Get:5 http://za.archive.ubuntu.com/ubuntu yakkety-backports InRelease [102 kB]
Get:6 http://za.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 Packages [146 kB]
Get:7 http://za.archive.ubuntu.com/ubuntu yakkety-updates/main i386 Packages [144 kB]
Get:8 http://za.archive.ubuntu.com/ubuntu yakkety-updates/universe i386 Packages [76.0 kB]
Get:9 http://za.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages [78.4 kB]
Fetched 752 kB in 1s (392 kB/s)
Reading package lists... Done
Confirming "yakkety" is supported...
- curl -sLf -o /dev/null 'https://deb.nodesource.com/node_6.x/dists/yakkety/Release'
Adding the NodeSource signing key to your keyring...
- curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
OK
Creating apt sources list file for the NodeSource Node.js v6.x repo...
- echo 'deb https://deb.nodesource.com/node_6.x yakkety main' > /etc/apt/sources.list.d/nodesource.list
- echo 'deb-src https://deb.nodesource.com/node_6.x yakkety main' >> /etc/apt/sources.list.d/nodesource.list
Running
apt-get updatefor you...- apt-get update
Hit:1 http://za.archive.ubuntu.com/ubuntu yakkety InRelease
Hit:2 http://za.archive.ubuntu.com/ubuntu yakkety-updates InRelease
Hit:3 http://za.archive.ubuntu.com/ubuntu yakkety-backports InRelease
Hit:4 http://security.ubuntu.com/ubuntu yakkety-security InRelease
Hit:5 https://deb.nodesource.com/node_6.x yakkety InRelease
Reading package lists... Done
Run
apt-get install nodejs(as root) to install Node.js v6.x and npmReading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version (6.9.4-1nodesource1~yakkety1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15245 100 15245 0 0 7949 0 0:00:01 0:00:01 --:--:-- 7948
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
git is already the newest version (1:2.9.3-1).
libpng-dev is already the newest version (1.6.25-1).
python-minimal is already the newest version (2.7.11-2).
redis-server is already the newest version (2:3.2.1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Cloning into 'xo-server'...
remote: Counting objects: 10478, done.
remote: Compressing objects: 100% (59/59), done.
remote: Total 10478 (delta 31), reused 0 (delta 0), pack-reused 10419
Receiving objects: 100% (10478/10478), 2.71 MiB | 1.11 MiB/s, done.
Resolving deltas: 100% (7503/7503), done.
Checking connectivity... done.
Cloning into 'xo-web'...
remote: Counting objects: 26050, done.
remote: Compressing objects: 100% (11/11), done.
error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g
npm WARN prefer global [email protected] should be installed with -g[email protected] install /opt/xo-server/node_modules/argon2
node-gyp rebuildmake: Entering directory '/opt/xo-server/node_modules/argon2/build'
CC(target) Release/obj.target/libargon2/argon2/src/opt.o
CC(target) Release/obj.target/libargon2/argon2/src/argon2.o
CC(target) Release/obj.target/libargon2/argon2/src/core.o
CC(target) Release/obj.target/libargon2/argon2/src/blake2/blake2b.o
CC(target) Release/obj.target/libargon2/argon2/src/thread.o
CC(target) Release/obj.target/libargon2/argon2/src/encoding.o
AR(target) Release/obj.target/argon2.a
COPY Release/argon2.a
CXX(target) Release/obj.target/argon2/src/argon2_node.o
SOLINK_MODULE(target) Release/obj.target/argon2.node
COPY Release/argon2.node
make: Leaving directory '/opt/xo-server/node_modules/argon2/build'[email protected] install /opt/xo-server/node_modules/bcrypt
node-pre-gyp install --fallback-to-buildbash: line 13: 3533 Killed sudo npm install
bash: line 16: cd: /opt/xo-web: No such file or directory
node-pre-gyp ERR! Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v1.0.2/bcrypt_lib-v1.0.2-node-v51-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v51 ABI) (falling back to source compile with node-gyp)
make: Entering directory '/opt/xo-server/node_modules/bcrypt/build'shing
CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.osIntoIdealTree
SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.nodeDepsIntoIdealTree
COPY Release/bcrypt_lib.node
COPY /opt/xo-server/node_modules/bcrypt/lib/binding/bcrypt_lib.node
TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/opt/xo-server/node_modules/bcrypt/build'
npm WARN prepublish-on-install As of npm@5,prepublishscripts will run only fornpm publish.
npm WARN prepublish-on-install (In npm@4 and previous versions, it also runs fornpm install.)
npm WARN prepublish-on-install See the deprecation note innpm help scriptsfor more information.
npm WARN lifecycle [email protected]~prepublish: cannot run in wd %s %s (wd=%s) [email protected] npm run build /opt/xo-server
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})[email protected] prebuild /opt/xo-server
index-modules src/api src/xapi/mixins src/xo-mixinsindex generated src/api/index.js
index generated src/xo-mixins/index.js
index generated src/xapi/mixins/index.js[email protected] build /opt/xo-server
gulp build --production[15:34:46] Using gulpfile /opt/xo-server/gulpfile.js
[15:34:46] Starting 'build'...
[15:34:46] Starting 'clean'...
[15:34:46] Finished 'clean' after 8.5 ms
[15:34:46] Starting 'buildCoffee'...
[15:34:46] Starting 'buildEs6'...
[15:34:53] Finished 'buildCoffee' after 6.68 s
[15:35:33] Finished 'buildEs6' after 47 s
[15:35:33] Finished 'build' after 47 s
root@xenorc:/opt# - apt-get update
-
Warning aren't critical.
Go to the ip address of this server and see if you have XO running.
The default login is [email protected] and admin as the password if i remember correctly.
