Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

brandon

@DustinB3403 Nope, Nothing see it never even ran npm install & rebuild in xo-web?

If I try to start npm I get this

root@xenorc:/opt# npm start
npm ERR! Linux 4.8.0-22-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v7.4.0
npm ERR! npm v4.0.5
npm ERR! path /opt/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open

npm ERR! enoent ENOENT: no such file or directory, open '/opt/package.json'
npm ERR! enoent ENOENT: no such file or directory, open '/opt/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR! /opt/npm-debug.log

travisdh1

@brandon Is xo-web installed directly in /opt? Looks like you might be trying to start it from the wrong place to me.

brandon

@travisdh1 Cant go to xo-web...

root@xenorc:/opt# ls
node_modules npm-debug.log xo-server

DustinB3403

@travisdh1 the installer script should create the directories and install into them without any user intervention.

@brandon are the folders xo-web and xo-server under /opt/ ?

brandon

@DustinB3403 No it didnt clone from git... Should we try to fix the Debian one since it is 90 % done?

travisdh1

@brandon said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@travisdh1 Cant go to xo-web...

root@xenorc:/opt# ls
node_modules npm-debug.log xo-server

Ah, well, something didn't work right in the script then. You should have an xo-web directory as well.

brandon

@travisdh1 I have been trying for days...

brandon

@travisdh1

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

Danp

Need to determine why git clone -b stable https://github.com/vatesfr/xo-web is failing.

brandon

@Danp I am going to run :

git clone -b stable https://github.com/vatesfr/xo-web
sudo cp sample.config.yaml .xo-server.yaml
sudo sed -i /mounts/a\" '/': '/opt/xo-web/dist'" .xo-server.yaml
cd /opt/xo-web
sudo npm install
sudo npm run build

since that is where it stopped?

travisdh1

@brandon Yes, should get the web interface working.

brandon

This happened after getting to npm install

root@xenorc:/opt/xo-web# sudo npm install
npm ERR! git fetch -a origin (git://github.com/fizzed/font-mfizz.git)
npm ERR! git fetch -a origin (git://github.com/gulpjs/gulp.git)
npm WARN addRemoteGit Error: Command failed: git config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12)
npm WARN addRemoteGit at emitTwo (events.js:106:13)
npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16)
npm WARN addRemoteGit at Socket.<anonymous> (internal/child_process.js:334:11)
npm WARN addRemoteGit at emitOne (events.js:96:13)
npm WARN addRemoteGit at Socket.emit (events.js:188:7)
npm WARN addRemoteGit at Pipe._handle.close [as _onclose] (net.js:501:12)
npm WARN addRemoteGit fizzed/font-mfizz resetting remote /root/.npm/_git-remotes/git-https-github-com-fizzed-font-mfizz-git-b15d96d5 because of error: { Error: Command failed: git config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit at ChildProcess.exithandler (child_process.js:211:12)
npm WARN addRemoteGit at emitTwo (events.js:106:13)
npm WARN addRemoteGit at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit at maybeClose (internal/child_process.js:885:16)
npm WARN addRemoteGit at Socket.<anonymous> (internal/child_process.js:334:11)
npm WARN addRemoteGit at emitOne (events.js:96:13)
npm WARN addRemoteGit at Socket.emit (events.js:188:7)
npm WARN addRemoteGit at Pipe._handle.close [as _onclose] (net.js:501:12)
npm WARN addRemoteGit killed: false,
npm WARN addRemoteGit code: 1,
npm WARN addRemoteGit signal: null,
npm WARN addRemoteGit cmd: 'git config --get remote.origin.url' }
Killed

root@xenorc:/opt/xo-web#

travisdh1

@olivier Any reason the first two lines error out on your end?

@brandon This looks like another git problem. The npm install script wants to download a couple things from git, which fail and cause the rest of the script to fail.

brandon

@travisdh1 I have no idea.... network connection is fine...

Dashrender

can you manually fetch those two gits that fail?

brandon

@Dashrender Okay must I run:
git fetch -a origin (git://github.com/fizzed/font-mfizz.git)
git fetch -a origin (git://github.com/gulpjs/gulp.git)

but after that I need to rerun npm install then it will bomb out again?

Danp

@brandon May want to read this thread for some possible solutions.

Dashrender

@Danp said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@brandon May want to read this thread for some possible solutions.

Interesting - so he possibly has an application filtering firewall that is blocking git calls.

See @BRRABill, a change of git: to https: gets around the filtering in this case - application filtering, rarely worth the expense.

DustinB3403

I wonder if it would be easier for "us" to simply build an appliance version of XO and offer that as a direct download.

Maybe XOS?

Danp

@DustinB3403 No thanks. I'll leave that to @olivier and crew.