BRRABill's Field Report With XenServer
-
@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?
-
@BRRABill Sure... here's the commands:
sudo bash <password> sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash
-
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
-
@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
-
@BRRABill Does it start with
sudo systemctl start xo-server
? -
@Danp said in BRRABill's Field Report With XenServer:
@BRRABill Does it start with
sudo systemctl start xo-server
?Does what? My script?
-
@BRRABill xo server
-
-
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.
-
@BRRABill Trying on my install now (still on Ubuntu 15.10).
-
@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. -
@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 rightsudo 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 ```
-
@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 rightThere'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-sassDon't see anything inherently wrong here. <shrug>
-
@BRRABill Did you try restarting XO after doing this?
-
@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!
-
@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. -
@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.
-
@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. -
Set up a new 15.10 VM, and installed XO with no issues.
Man I love open source and virtualization!
-
@BRRABill Just remember that 15.10s EOL was July 28, so it will not be receiving any more updates.