Xen Orchestra - Updating
-
@DustinB3403 said:
Well after rerunning in both ~/xo-server and ~/xo-web
npm install && npm run build sudo npm start
Has started, now to determine if I'm on 4.11
5.2.0 is what your screen cap says.
-
Yeah I know, which is why I'm lost. Maybe just dump the whole lot and start over?
-
Oh, your xo-web version is 4.10.0. Your Node version is 5.2.0.
-
Which this screen should have the delta icon as shown in the documentation.
Or maybe it only shows up after performing a full?
-
WARNING 2: NodeJS 5 is not supported for now due to some dependencies problems.
-
You need to get onto a supported platform version, I'm guessing that running a language version that they believe does not work is probably the issue. An issue, even if not, THE issue.
-
I ran the installer following their guide...
And everything seems functional..... but the web console isn't updated to 4.11.
-
@DustinB3403 said:
I ran the installer following their guide...
And everything seems functional..... but the web console isn't updated to 4.11.
Which installer installed that Node version?
-
5.2.0 I'm removing it now and looking for a direct link to 4.1.1
-
Use NVM for installing and controlling Node versions.
-
I'm just gonna start with a clean install. NVM doesn't want to remove the files without being a pain in the arse.
-
@scottalanmiller the Node version was 5.2.0 which was installed directly from the default repo.
Going to perform a depreciated install for Node v 4.x
-
By default I would expect Node to install the latest. For XO, though, you have to manually ensure that you are on the Node 4 family.
-
Ya I'm on node 5 also. I didn't change anything. I did it as a test to see if it would work, and I haven't had an issue yet but I wouldn't put it in production.
-
Built a new VM, and installed node version 4.2.3. NPM is running version 2.14.7
-
Well something is definitely off.... No such file ENOENT
-
And in /usr/local/lib I don't have "node_modules"
-
Have you run
npm install
before this? -
Yup.
-
I'm starting the build over as it seems to have something funky with it..
Clean Ubuntu 15.10 server and will go from here.