Xen Orchestra on Ubuntu 15.10 - Complete installation instructions

Alex Sage

npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v5.4.0
npm ERR! npm  v3.3.12
npm ERR! code ELIFECYCLE
npm ERR! xo-server@4.11.0 start: `node bin/xo-server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the xo-server@4.11.0 start script 'node bin/xo-server'.
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-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/xo-server
npm ERR! You can get their info via:
npm ERR!     npm owner ls xo-server
npm ERR! There is likely additional logging output above.

scottalanmiller

Remember when I asked what node version you were installing? That looks like Node 5. I thought XO could only work with Node 4.

scottalanmiller

@scottalanmiller said:

What Node.js version do you have installed?

There was the question ^^^^

I never saw a response. We could have tracked this down sooner You can't just use the Node that comes with the distro. Use NVM and control the Node version.

Romo

@scottalanmiller said:

@anonymous said:

@scottalanmiller Because it's the lastest LTS release. Isn't using LTS best practice?

No, it's a bad practice. Using something with "long term support" is a good practice, but with Ubuntu it is just a naming thing for marketing purposes. Even Canonical themselves do not recognize it as an LTS. It's just letters that they slap on every fourth release to make it sound like an enterprise product like RHEL. It isn't. Ubuntu is a rolling release will full support only for the latest build. So sticking to LTS is just "not updating" in this case. One of the many reasons that Ubuntu isn't that good. It's not "bad", but it isn't up to par.

Ubuntu is like Fedora, you always want to be on the latest unless there is a compatibility issue. You would never intentionally use an LTS release unless you are doing something like MongoDB which only releases for certain versions. And the answer there is not to use Ubuntu but to use CentOS which is kept up to date.

If you want a true LTS, Ubuntu is not an option for you. RHEL and SLES are the only enterprise long term support options in the Linux world.

@scottalanmiller Why aren't ubuntu LTS releases trully considered as having long term support? I usually use Centos but I do have several Ubuntu LTS boxes and from their documentation they appear as having long term support.

0_1452612753264_2016-01-12 09_30_26-Release end of life _ Ubuntu.png

scottalanmiller

@Romo said:

@scottalanmiller Why aren't ubuntu LTS releases trully considered as having long term support? I usually use Centos but I do have several Ubuntu LTS boxes and from their documentation they appear as having long term support.

Because Long Term Support suggests that when things break, they fix them and provide support. But Canonical doesn't do that. If things really break they tell their LTS clients to upgrade to the latest non-LTS release to continue getting support. True LTS support never requires "going to the non-LTS release" to continue getting support. The label LTS and their "support marketing timelines" are just made up marketing.

scottalanmiller

@Romo said:

from their documentation they appear as having long term support.

Thats where terms like "marketing" and "lying" come into it.

Alex Sage

@scottalanmiller Like this?

Install Node Using the Node Version Manager

https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-a-centos-7-server

scottalanmiller

@Romo said:

I know shops that in 2011 were already being told by Canonical that to get support they had to leave 10.04 LTS because they would only try to fix things in the 11.04 or 11.10 releases. 10.04 has major stability bugs that were just ignored because the 11 series fixed them. The LTS theory is that fixes would be backported. But they are not. Canonical just uses LTS to fool customers, they do not mean it to mean that they will support the product.

scottalanmiller

@anonymous said:

@scottalanmiller Like this?

Install Node Using the Node Version Manager

https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-a-centos-7-server

Exactly. I was just about to look for this.

Alex Sage

@scottalanmiller Do I have to remove the old version first?

Alex Sage

npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/root/.nvm/v4.2.2/bin/node" "/root/.nvm/v4.2.2/bin/npm" "start"
npm ERR! node v4.2.2
npm ERR! npm  v2.14.7
npm ERR! code ELIFECYCLE
npm ERR! xo-server@4.11.0 start: `node bin/xo-server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the xo-server@4.11.0 start script 'node bin/xo-server'.
npm ERR! This is most likely a problem with the xo-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/xo-server
npm ERR! You can get their info via:
npm ERR!     npm owner ls xo-server
npm ERR! There is likely additional logging output above.

Alex Sage

Doh! NPM is out of date too. How do I update it?

scottalanmiller

@anonymous said:

@scottalanmiller Do I have to remove the old version first?

No but better if you do. It will keep being the default.

scottalanmiller

@anonymous said:

Doh! NPM is out of date too. How do I update it?

I think NVM will handle that too.

Alex Sage

Updated NPM using:

 curl -L https://npmjs.com/install.sh | sh

Still isn't working

npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/root/.nvm/v4.2.2/bin/node" "/root/.nvm/v4.2.2/bin/npm" "start"
npm ERR! node v4.2.2
npm ERR! npm  v3.5.3
npm ERR! code ELIFECYCLE
npm ERR! xo-server@4.11.0 start: `node bin/xo-server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the xo-server@4.11.0 start script 'node bin/xo-server'.
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-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node bin/xo-server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs xo-server
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls xo-server
npm ERR! There is likely additional logging output above.

scottalanmiller

Did you do a fresh install using Node 4?

Alex Sage

@scottalanmiller No, I can try that.

Alex Sage

[xo@xo ~]$ sudo yum -y install build-essential redis-server libpng-dev git python-minima
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.net.cen.ct.gov
 * epel: mirror.cogentco.com
 * extras: mirror.cc.columbia.edu
 * updates: mirror.us.leaseweb.net
No package build-essential available.
No package redis-server available.
No package libpng-dev available.
Package git-1.8.3.1-6.el7.x86_64 already installed and latest version
No package python-minima available.
Nothing to do
[xo@xo ~]$

Alex Sage

Any idea what the correct packages might be?

Alex Sage

[11:39:58] Using gulpfile ~/xo-server/gulpfile.js
[11:39:58] Starting 'build'...
[11:39:58] Starting 'buildCoffee'...
[11:39:58] Starting 'buildEs6'...
[11:39:59] 'buildEs6' errored after 925 ms
[11:39:59] Error: EACCES: permission denied, mkdir '/home/xo/xo-server/dist'
at Error (native)

[11:39:59] 'build' errored after 929 ms
[11:39:59] The following tasks did not complete: buildCoffee
[11:39:59] Did you forget to signal async completion?

npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/home/xo/.nvm/versions/node/v4.2.2/bin/node" "/home/xo/.nvm/versions/node/v4.2.2/bin/npm" "run" "build"
npm ERR! node v4.2.2
npm ERR! npm v3.5.3
npm ERR! code ELIFECYCLE
npm ERR! xo-server@4.11.0 build: gulp build --production
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the xo-server@4.11.0 build script 'gulp build --production'.
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-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp build --production
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs xo-server
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls xo-server
npm ERR! There is likely additional logging output above.
npm ERR! Linux 3.10.0-327.el7.x86_64
npm ERR! argv "/home/xo/.nvm/versions/node/v4.2.2/bin/node" "/home/xo/.nvm/versions/node/v4.2.2/bin/npm" "run" "build"
npm ERR! node v4.2.2
npm ERR! npm v3.5.3
npm ERR! path npm-debug.log.1635463929
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall open

npm ERR! Error: EACCES: permission denied, open 'npm-debug.log.1635463929'
npm ERR! at Error (native)
npm ERR! { [Error: EACCES: permission denied, open 'npm-debug.log.1635463929']
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'open',
npm ERR! path: 'npm-debug.log.1635463929' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR! /home/xo/xo-server/npm-debug.log
[xo@xo xo-server]$