BRRABill's Field Report With XenServer

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?

BRRABill

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

@BRRABill Did you try restarting XO after doing this?

Yeah.

I'm just going to reinstall XO.

And make a mental note to take snapshots before updating anything!

momurda

@BRRABill
I'm wondering if you ever solved the 4 TB of data/snapshots/stuff that you had a problem with. That is a lot of posts to read and I don't know where it was in the thread.

BRRABill

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

@BRRABill
I'm wondering if you ever solved the 4 TB of data/snapshots/stuff that you had a problem with. That is a lot of posts to read and I don't know where it was in the thread.

That wasn't me.

I have had an f-ton of problems, but not that one.

momurda

@BRRABill
Ah, whoops.
I was going to suggest XOA Free's web interface, specifically the SR view that shows disk details for a given SR. I had a similar issue and that view allowed me to erase the bad vdis accurately and easily in case that person(don't remember who it was apparently) is reading this thread too.

BRRABill

Set up a new 15.10 VM, and installed XO with no issues.

Man I love open source and virtualization!

Romo

@BRRABill Just remember that 15.10s EOL was July 28, so it will not be receiving any more updates.

BRRABill

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

@BRRABill Just remember that 15.10s EOL was July 28, so it will not be receiving any more updates.

I only used that because that is what everyone else is using and I got comments moving to 16.

But now I am questioning my decision.

StrongBad

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

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

@BRRABill Just remember that 15.10s EOL was July 28, so it will not be receiving any more updates.

I only used that because that is what everyone else is using and I got comments moving to 16.

But now I am questioning my decision.

Just an old thread. If you use Ubuntu, you update continuously. Just how it works.

BRRABill

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

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

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

@BRRABill Just remember that 15.10s EOL was July 28, so it will not be receiving any more updates.

I only used that because that is what everyone else is using and I got comments moving to 16.

But now I am questioning my decision.

Just an old thread. If you use Ubuntu, you update continuously. Just how it works.

This was a few weeks ago.

I think it was more a "XO doesn't support" 16, but technically they don't support anything.

scottalanmiller

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

I think it was more a "XO doesn't support" 16, but technically they don't support anything.

"Support" is always a weird term. Microsoft doesn't support any product unless you pay for extra support. Why do people never worry that Windows isn't supported but are worried that a non-critical web application is?