Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

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.

olivier

In any case, you'll hit the same issues: you can't guess what's inside the user network. Believe me, you don't want to spend your non-working time making support for free because someone forgot there is a proxy between their Xen Orchestra installation and outside.

edit: I think I have roughly some stats on support, at least half of the time is related to user configuration issues.

edit2 : my 2 cents on the current issue: not enough RAM to build npm packages.

DustinB3403

@olivier and @danp it was a joke regarding the issues that @brandon is having. I don't want to get into that bed....

olivier

@DustinB3403 no worries, you can try The problem is not an appliance vs a script anyway

DustinB3403

@olivier oh I know it's a PEBCAK issue.

Dashrender

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

In any case, you'll hit the same issues: you can't guess what's inside the user network. Believe me, you don't want to spend your non-working time making support for free because someone forgot there is a proxy between their Xen Orchestra installation and outside.

LOL - he's already doing that.

olivier

@DustinB3403 Not especially, it could be a lot of various things related to the user network installation, etc.

olivier

@Dashrender it was just an example, is it the issue here? If it's the case, it's accidental

brandon

I allocated 4gb of ram to the vm....

After opening the firewall and git config --global url."https://".insteadOf git://

This is now my error :

root@xenorc:/opt/xo-web# sudo npm install
Killed ............] \ fetchMetadata: sill mapToRegistry uri https://registry.npmjs.org/xo-lib

DustinB3403

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

@DustinB3403 Not especially, it could be a lot of various things related to the user network installation, etc.

PEBCAK means Problem exist between chair and keyboard.

Meaning anything that the user is in control of. Aka himself and network.

olivier

@DustinB3403 Sometimes the user is not aware of the network (if working in teams, net admin etc.)

brandon

@olivier I think you might be right, I am on the test network and I dont really mess with the network admins config on the main router its quite a big network... Will try to install Orchastra on the main network and see maybe you are right...