Xen Orchestra on Ubuntu 15.10 - Complete installation instructions
-
You have to uncommend mounts! =/
-
I must be missing something, because I am having issues with every distro I use.....
-
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! [email protected] start: `node bin/xo-server` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] 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. -
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 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. -
@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.
-
@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.
-
@Romo said:
from their documentation they appear as having long term support.
Thats where terms like "marketing" and "lying" come into it.
-
@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
-
@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.
-
@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.
-
@scottalanmiller Do I have to remove the old version first?
-
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! [email protected] start: `node bin/xo-server` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] 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. -
Doh! NPM is out of date too. How do I update it?
-
@anonymous said:
@scottalanmiller Do I have to remove the old version first?
No but better if you do. It will keep being the default.
-
@anonymous said:
Doh! NPM is out of date too. How do I update it?
I think NVM will handle that too.
-
Updated NPM using:
curl -L https://npmjs.com/install.sh | shStill 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! [email protected] start: `node bin/xo-server` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] 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. -
Did you do a fresh install using Node 4?
-
@scottalanmiller No, I can try that.
-
[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 ~]$
