Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
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 -
Need to determine why
git clone -b stable https://github.com/vatesfr/xo-web
is failing. -
@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 buildsince that is where it stopped?
-
@brandon Yes, should get the web interface working.
-
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' }
Killedroot@xenorc:/opt/xo-web#
-
-
@travisdh1 I have no idea.... network connection is fine...
-
can you manually fetch those two gits that fail?
-
@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?
-
@brandon May want to read this thread for some possible solutions.
-
@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.
-
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?
-
@DustinB3403 No thanks. I'll leave that to @olivier and crew.
-
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 no worries, you can try The problem is not an appliance vs a script anyway
-
@olivier oh I know it's a PEBCAK issue.
-
@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.
-
@DustinB3403 Not especially, it could be a lot of various things related to the user network installation, etc.
-
@Dashrender it was just an example, is it the issue here? If it's the case, it's accidental