BRRABill's Field Report With XenServer
-
@travisdh1 said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
P.S. If I forget to preface commands with sudo one more time......
sudo -i or sudo su - are you're friends, good job using sudo, now make life easier on yourself and keep the "who ran that command as root" trace at the same time.
This is what I do, too.
sudo -i su -
@Dashrender said in BRRABill's Field Report With XenServer:
How did you get node 6? from apt-get or whatever the application update command is for the version you're using?
You can use NVM.
https://mangolassi.it/topic/5366/getting-nodejs-on-centos-7-with-nvm
-
@Dashrender said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
@Dashrender said in BRRABill's Field Report With XenServer:
How did you get node 6? from apt-get or whatever the application update command is for the version you're using?
That I do not know.
Like I said, I've done nothing but install XO and use apt-get update and upgrade.
OK, so how does one upgrade/update node? oh... and WTH is node?
With NVM if you want control over it. With apt-get if you just want the version locked to Ubuntu.
-
@scottalanmiller said in BRRABill's Field Report With XenServer:
@Dashrender said in BRRABill's Field Report With XenServer:
How did you get node 6? from apt-get or whatever the application update command is for the version you're using?
You can use NVM.
https://mangolassi.it/topic/5366/getting-nodejs-on-centos-7-with-nvm
I think what he asking was...
since I've done nothing other than upgrading, why did this happen? -
@BRRABill said in BRRABill's Field Report With XenServer:
Do you think my issue is fixable, or would you recommend just scrapping the VM and reinstalling XO?
If it is NPM, yes. Just have to track down which components are broken
-
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
Do you think my issue is fixable, or would you recommend just scrapping the VM and reinstalling XO?
If it is NPM, yes. Just have to track down which components are broken
XO installs, it just doesn't work.
I guess we could look through XO logs?
-
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
Do you think my issue is fixable, or would you recommend just scrapping the VM and reinstalling XO?
If it is NPM, yes. Just have to track down which components are broken
XO installs, it just doesn't work.
I guess we could look through XO logs?
That would be where to start
-
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
Do you think my issue is fixable, or would you recommend just scrapping the VM and reinstalling XO?
If it is NPM, yes. Just have to track down which components are broken
XO installs, it just doesn't work.
I guess we could look through XO logs?
That would be where to start
And where would these elusive logs be?
(AKA, are they stored with the app? Or in some central location?)
-
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
Do you think my issue is fixable, or would you recommend just scrapping the VM and reinstalling XO?
If it is NPM, yes. Just have to track down which components are broken
XO installs, it just doesn't work.
I guess we could look through XO logs?
That would be where to start
And where would these elusive logs be?
(AKA, are they stored with the app? Or in some central location?)
Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.
-
@scottalanmiller said
Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.
That answers my question.
That most logs are supposed to be in /var/log
-
Not in /var/log
Maybe another XO user with chime in, or eventually @olivier will come to the rescue!
-
@BRRABill said in BRRABill's Field Report With XenServer:
Not in /var/log
Maybe another XO user with chime in, or eventually @olivier will come to the rescue!
Have you modified the logs?
-
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said
Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.
That answers my question.
That most logs are supposed to be in /var/log
Yes, that is the standard log location.
-
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said
Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.
That answers my question.
That most logs are supposed to be in /var/log
Yes, that is the standard log location.
Wouldn't XO logs be in /var/log/syslog, since it is normally installed in ubuntu?
-
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
Not in /var/log
Maybe another XO user with chime in, or eventually @olivier will come to the rescue!
Have you modified the logs?
Noooooooooooooooooooooooooo
-
@Romo said in BRRABill's Field Report With XenServer:
@scottalanmiller said in BRRABill's Field Report With XenServer:
@BRRABill said in BRRABill's Field Report With XenServer:
@scottalanmiller said
Not sure, but unless you have some reason to assume that they are not where they belong in /var/log, assume that they are there.
That answers my question.
That most logs are supposed to be in /var/log
Yes, that is the standard log location.
Wouldn't XO logs be in /var/log/syslog, since it is normally installed in ubuntu?
Hey, there is xo-server stuff in there!!!
So, do all apps write to that one file?
-
This is what is appearing over and over and over and over again...
Aug 18 06:26:58 ubuntu systemd[1]: Started XO Server. Aug 18 06:27:01 ubuntu xo-server[26354]: (node:26354) 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 06:27:01 ubuntu xo-server[26354]: /opt/xo-server/node_modules/bindings/bindings.js:83 Aug 18 06:27:01 ubuntu xo-server[26354]: throw e Aug 18 06:27:01 ubuntu xo-server[26354]: ^ Aug 18 06:27:01 ubuntu xo-server[26354]: Error: Module version mismatch. Expected 48, got 47. Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at bindings (/opt/xo-server/node_modules/bindings/bindings.js:76:44) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/opt/xo-server/node_modules/leveldown/leveldown.js:4:46) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/opt/xo-server/node_modules/level/level.js:1:44) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/opt/xo-server/node_modules/level-party/index.js:1:13) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/source/xo-mixins/store.js:2) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/source/xo-mixins/index.js:46) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/source/xo.js:7) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/source/index.js:28) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/opt/xo-server/index.js:11:18) Aug 18 06:27:01 ubuntu xo-server[26354]: at require (internal/module.js:20:19) Aug 18 06:27:01 ubuntu xo-server[26354]: at Object.<anonymous> (/opt/xo-server/bin/xo-server:31:25) Aug 18 06:27:01 ubuntu systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE Aug 18 06:27:01 ubuntu systemd[1]: xo-server.service: Unit entered failed state. Aug 18 06:27:01 ubuntu systemd[1]: xo-server.service: Failed with result 'exit-code'. Aug 18 06:27:02 ubuntu systemd[1]: xo-server.service: Service hold-off time over, scheduling restart. Aug 18 06:27:02 ubuntu systemd[1]: Stopped XO Server. Aug 18 06:27:02 ubuntu systemd[1]: Started XO Server. -
@BRRABill try journalctl -u xo-server -f -n 50
-
@BRRABill said in BRRABill's Field Report With XenServer:
That I do not know.
Like I said, I've done nothing but install XO and use apt-get update and upgrade.
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.
-
It looks like your apt-get update and upgrade upgraded something to too new a version.
I cant remember what repos xo uses.
Can you roll back or reinstall then try using the upgrade button in xo web?
