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.
-
@travisdh1 said in BRRABill's Field Report With XenServer:
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.
You going over that in your MC session?
-
@BRRABill said in BRRABill's Field Report With XenServer:
@travisdh1 said in BRRABill's Field Report With XenServer:
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.
You going over that in your MC session?
I will now
Slide added to my deck, now I just have to fill it out. -
@olivier said in BRRABill's Field Report With XenServer:
Beside that Node 6 is not officially supported (only Node LTS, as you can read here: https://xen-orchestra.com/docs/from_the_sources.html) you should remove your
node_modulesfolder andnpm i.That allowed both packages to be installed/updated.
But XO still will not load. Comes up with "10.0.4.41 refused to connect."
Do you think some sort of something in an update hosed it? I can just reinstall from scratch if it's too much work to fix.
-
Nope but I'm not surprised
npmcan trigger this from time to time. That's why we are carefully testing our own packages before any release on XOAs. -
@olivier said in BRRABill's Field Report With XenServer:
Nope but I'm not surprised
npmcan trigger this from time to time. That's why we are carefully testing our own packages before any release on XOAs.So, at this point, maybe just start over, do you think?
(For me.)
-
How did you get node 6? from apt-get or whatever the application update command is for the version you're using?
-
@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.
-
@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?
-
@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?
You're over my pay grade!
-
@Dashrender said in BRRABill's Field Report With XenServer:
OK, so how does one upgrade/update node? oh... and WTH is node?
Only the most talked about programming platform of this decade. NodeJS. The language used to make NodeBB, that we are typing this on right now. Node powers tons of the latest, most up to date stuff. Amazing language and framework.
-
NodeJS is the server side JavaScript framework powered by Google V8.
-
Do you think my issue is fixable, or would you recommend just scrapping the VM and reinstalling XO?
-
@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
