BRRABill's Field Report With XenServer

BRRABill

The latest version of the update script does perform an update to the latest stable version of Node. I haven't found this to be a problem thus far, and I updated within the last day or so.

What update script?

BRRABill

@Romo said in BRRABill's Field Report With XenServer:

journalctl -u xo-server -f -n 50

journalctl -u xo-server -f -n 50
-- Logs begin at Thu 2016-08-18 16:57:07 EDT. --
Aug 18 17:05:26 ubuntu xo-server[4846]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:26 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:26 ubuntu systemd[1]: Started XO Server.
Aug 18 17:05:26 ubuntu xo-server[4854]: module.js:442
Aug 18 17:05:26 ubuntu xo-server[4854]:     throw err;
Aug 18 17:05:26 ubuntu xo-server[4854]:     ^
Aug 18 17:05:26 ubuntu xo-server[4854]: Error: Cannot find module './dist'
Aug 18 17:05:26 ubuntu xo-server[4854]:     at require (internal/module.js:20:19)
Aug 18 17:05:26 ubuntu xo-server[4854]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 17:05:26 ubuntu xo-server[4854]:     at require (internal/module.js:20:19)
Aug 18 17:05:26 ubuntu xo-server[4854]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:26 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:26 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:26 ubuntu systemd[1]: Started XO Server.
Aug 18 17:05:27 ubuntu xo-server[4862]: module.js:442
Aug 18 17:05:27 ubuntu xo-server[4862]:     throw err;
Aug 18 17:05:27 ubuntu xo-server[4862]:     ^
Aug 18 17:05:27 ubuntu xo-server[4862]: Error: Cannot find module './dist'
Aug 18 17:05:27 ubuntu xo-server[4862]:     at require (internal/module.js:20:19)
Aug 18 17:05:27 ubuntu xo-server[4862]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 17:05:27 ubuntu xo-server[4862]:     at require (internal/module.js:20:19)
Aug 18 17:05:27 ubuntu xo-server[4862]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:27 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:27 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:27 ubuntu systemd[1]: Started XO Server.
Aug 18 17:05:28 ubuntu xo-server[4870]: module.js:442
Aug 18 17:05:28 ubuntu xo-server[4870]:     throw err;
Aug 18 17:05:28 ubuntu xo-server[4870]:     ^
Aug 18 17:05:28 ubuntu xo-server[4870]: Error: Cannot find module './dist'
Aug 18 17:05:28 ubuntu xo-server[4870]:     at require (internal/module.js:20:19)
Aug 18 17:05:28 ubuntu xo-server[4870]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 17:05:28 ubuntu xo-server[4870]:     at require (internal/module.js:20:19)
Aug 18 17:05:28 ubuntu xo-server[4870]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 17:05:28 ubuntu systemd[1]: Stopped XO Server.
Aug 18 17:05:28 ubuntu systemd[1]: xo-server.service: Start request repeated too quickly.
Aug 18 17:05:28 ubuntu systemd[1]: Failed to start XO Server.

BRRABill

@Danp said

The latest version of the update script does perform an update to the latest stable version of Node. I haven't found this to be a problem thus far, and I updated within the last day or so.

Because I tried using the update script everyone else uses last week, and it failed. I have my own, so I just went back to that.

Danp

@BRRABill The same one that was mentioned earlier here.

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

@BRRABill The same one that was mentioned earlier here.

Yeah, I tried running that last week, and it failed on me.

I didn't think anything of it, but I haven't been back into XO since then. So apparently that could be what broke my stuff.

Danp

@BRRABill said in BRRABill's Field Report With XenServer:

Because I tried using the update script everyone else uses last week, and it failed. I have my own, so I just went back to that.

Failed how? Did you run it as root (sudo bash)? Details please.

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

@BRRABill said in BRRABill's Field Report With XenServer:

Because I tried using the update script everyone else uses last week, and it failed. I have my own, so I just went back to that.

Failed how? Did you run it as root (sudo bash)? Details please.

I honestly do no remember.

It just didn't work.

Want me to try running it now?

Danp

@BRRABill Sure... here's the commands:

sudo bash
<password>
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash

BRRABill

sudo bash xo-update.sh
Stopping xo-server...
Updating Node.js to latest stable version...

     install : node-v6.4.0
       mkdir : /usr/local/n/versions/node/6.4.0
       fetch : https://nodejs.org/dist/v6.4.0/node-v6.4.0-linux-x64.tar.gz
######################################################################## 100.0%
   installed : v6.4.0

Checking xo-server...
xo-update.sh: line 38: updateFromSource: command not found
Checking xo-web...
xo-update.sh: line 42: updateFromSource: command not found
Please manually restart xo-server

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

@BRRABill Sure... here's the commands:

sudo bash
<password>
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash

Oh, that's not what I did. I downloaded the file, and then ran it.

This command made it work.

Still not running xo-server though

Danp

@BRRABill Does it start with sudo systemctl start xo-server?

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

@BRRABill Does it start with sudo systemctl start xo-server?

Does what? My script?

Danp

@BRRABill xo server

BRRABill

@Danp

No. I mean, no error ever comes up.

The webpage just will not load.

BRRABill

Same thing...

Aug 18 21:56:16 ubuntu systemd[1]: Started XO Server.
Aug 18 21:56:19 ubuntu xo-server[17131]: (node:17131) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Aug 18 21:56:20 ubuntu xo-server[17131]: /opt/xo-server/node_modules/bindings/bindings.js:83
Aug 18 21:56:20 ubuntu xo-server[17131]:         throw e
Aug 18 21:56:20 ubuntu xo-server[17131]:         ^
Aug 18 21:56:20 ubuntu xo-server[17131]: Error: Module version mismatch. Expected 48, got 47.
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at bindings (/opt/xo-server/node_modules/bindings/bindings.js:76:44)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/opt/xo-server/node_modules/leveldown/leveldown.js:4:46)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/opt/xo-server/node_modules/level/level.js:1:44)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/opt/xo-server/node_modules/level-party/index.js:1:13)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/source/xo-mixins/store.js:2)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/source/xo-mixins/index.js:46)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/source/xo.js:7)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/source/index.js:28)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/opt/xo-server/index.js:11:18)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at require (internal/module.js:20:19)
Aug 18 21:56:20 ubuntu xo-server[17131]:     at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25)
Aug 18 21:56:20 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 18 21:56:20 ubuntu systemd[1]: xo-server.service: Unit entered failed state.
Aug 18 21:56:20 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'.
Aug 18 21:56:20 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart.
Aug 18 21:56:20 ubuntu systemd[1]: Stopped XO Server.

Danp

@BRRABill Trying on my install now (still on Ubuntu 15.10).

Danp

@BRRABill Mine built / loaded without issue. Did you try manually resolving the issue with npm rebuild node-sass? I'm guessing that you need to be in \opt\xo-web before issuing.

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

npm rebuild node-sass

When it is starting, said it was using node 6.4
Which @olivier said is not right

sudo npm rebuild node-sass
[sudo] password for willard:

> [email protected] install /opt/xo-web/node_modules/node-sass
> node scripts/install.js


> [email protected] postinstall /opt/xo-web/node_modules/node-sass
> node scripts/build.js

"/opt/xo-web/node_modules/node-sass/vendor/linux-x64-48/binding.node" exists.
 testing binary.
Binary is fine; exiting.
[email protected] /opt/xo-web/node_modules/node-sass

```

Danp

@BRRABill said in BRRABill's Field Report With XenServer:

When it is starting, said it was using node 6.4
Which @olivier said is not right

There's nothing wrong with the newer node version. It's just not officially supported by the XO team. You could switch to the older version using sudo n stable.

sudo npm rebuild node-sass
[sudo] password for willard:

[email protected] install /opt/xo-web/node_modules/node-sass
node scripts/install.js

[email protected] postinstall /opt/xo-web/node_modules/node-sass
node scripts/build.js

"/opt/xo-web/node_modules/node-sass/vendor/linux-x64-48/binding.node" exists.
testing binary.
Binary is fine; exiting.
[email protected] /opt/xo-web/node_modules/node-sass

Don't see anything inherently wrong here. <shrug>

Danp

@BRRABill Did you try restarting XO after doing this?