BRRABill's Field Report With XenServer

Danp

@olivier Which debug option? I I already have "verboseApiLogsOnErrors": true in the config.json file.

olivier

@Danp Well, so we don't have enough to draw any conclusion

Danp

@olivier Ok... I'm sure there will be more patches soon to test again.

BRRABill

@olivier

I used XO tonight to reboot a XS and it got stuck in maintenance mode.

Think that was something strange on my end?

(I ended up using XC to reboot it afterwards.)

Danp

@BRRABill It's a bug. Here's the GH Issue.

BRRABill

Stupid GitHub.

Just. Don't. Get. It.

BRRABill

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

@BRRABill It's a bug. Here's the GH Issue.

So what causes that bug?

I was just trying to reboot after a patch update.

Danp

@BRRABill My take is that there are multiple issues at work here --

Coding error (host.enabled vs host.enable). This is fixed in xo-server next-release branch.
XO's implementation of host reboot is very different from that found in XC

BRRABill

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

@BRRABill My take is that there are multiple issues at work here --

Coding error (host.enabled vs host.enable). This is fixed in xo-server next-release branch.

XO's implementation of host reboot is very different from that found in XC

Yeah I went to the server room and was surprised the XS was just sitting there. Then XC said it was i maintenance mode. I right clicked in XC and rebooted again, and it went to maintenance mode for a second and rebooted.

Very strange.

BRRABill

Anyone using XO...

When you run an update, do you have to reboot to get the next version to show up?

Or is there a service to restart?

xo-web always updates to the right version in the GUI. xo-server never does until I reboot.

olivier

No need to reboot, you are not on Windows xo-server runs in memory, so to get last version, you need to restart the process. That's all.

BRRABill

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

No need to reboot, you are not on Windows xo-server runs in memory, so to get last version, you need to restart the process. That's all.

Thanks @olivier

I try not to ping you on these. You have better stuff to do than to educate me, which you always do a great job of anyway!

Danp

@BRRABill Are you updating manually or with the script? The script will stop and restart the service for you.

BRRABill

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

@BRRABill Are you updating manually or with the script? The script will stop and restart the service for you.

Manually.

THOUGH ... I did just take a stab at writing my own script!

THOUGH THOUGH ... why not just use one already made.

BRRABill

So, went to log into XO today, it's not accessible. I reboot the server, still not.

I figure, eh, I'll update the version.

xoserver updates fine, but xo-web fails with the below messages...

This is on Ubuntu 16.04

Is it possible some OS update broke something in my system?


[16:15:17] 'buildStyles' errored after 1.56 s
[16:15:17] Error: The `libsass` binding was not found in /opt/xo-web/node_modules/node-sass/vendor/linux-x64-48/binding.node
This usually happens because your node version has changed.
Run `npm rebuild node-sass` to build the binding for your current node version.
    at Object.sass.getBinaryPath (/opt/xo-web/node_modules/node-sass/lib/extensions.js:158:11)
    at Object.<anonymous> (/opt/xo-web/node_modules/node-sass/lib/index.js:16:36)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/opt/xo-web/node_modules/gulp-sass/index.js:186:21)
[16:15:17] 'build' errored after 1.57 s
[16:15:17] The following tasks did not complete: buildPages, buildScripts, copyAssets
[16:15:17] Did you forget to signal async completion?

npm ERR! Linux 4.4.0-34-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v6.2.2
npm ERR! npm  v3.10.7
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: `npm run build-indexes && NODE_ENV=production gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script 'npm run build-indexes && NODE_ENV=production gulp build'.
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-web package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run build-indexes && NODE_ENV=production gulp build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs xo-web
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls xo-web
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /opt/xo-web/npm-debug.log

tiagom

Has your node version changed?

BRRABill

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

Has your node version changed?

I didn't purposely change anything.

tiagom

What version of node is installed?

BRRABill

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

What version of node is installed?

v6.2.2

olivier

This usually happens because your node version has changed.
Run `npm rebuild node-sass` to build the binding for your current node version.

Did you tried that?