New XOA setup, cant register

rkelley

@danp Yup. I was offering another method to get his XOA running (to see if he would run into the same issue).

Danp

@rkelley You offered a method of getting XO up and running.

FWIW, XO is not the same thing as XOA, so that wouldn't solve an issue with not being able to register XOA.

olivierlambert

You need to register, that's normal to NOT have a registration file if you are not registered

What's the exact issue with registration?

rkelley

@danp said in New XOA setup, cant register:

@rkelley You offered a method of getting XO up and running.

FWIW, XO is not the same thing as XOA, so that wouldn't solve an issue with not being able to register XOA.

Yes, I know. But, aside from the registration part, don't they do pretty much the exact same thing? My point is, @TheNorthernLight might not know XOA is a paid product (requires subscription) when he can get XO (built from sources) free.

In the end, he is just trying to get the Orchestra server up and running. He can do it via XOA or XO from sources. Unless I totally misunderstand the relationship between the two...

Danp

@rkelley said in New XOA setup, cant register:

In the end, he is just trying to get the Orchestra server up and running. He can do it via XOA or XO from sources. Unless I totally misunderstand the relationship between the two...

No, you've got it correct. I am left brained, so I like things to be explicit and I don't always follow the conversaion when things are implied. Hope you'll forgive me.

rkelley

@danp LOL, no worries dude! I know you are here to help people, and I (for one) really appreciate all the feedback and guidance you give. Hope I didn't come across too argumentative.

Danp

@rkelley

olivierlambert

@rkelley It's up to @TheNorthernLight to decide if we want to play with XOA, and it's a very good way to test XO without having to install things manually

Also, to answer the question "My point is, @TheNorthernLight might not know XOA is a paid product (requires subscription) when he can get XO (built from sources) free.". Well, if everybody think like that, XO project would be stopped years ago and XCP-ng wouldn't even exists

TheNorthernLight

@rkelley I already have the compiled XO version working without issue. However we are moving to paid support, so I'm setting up XOA in preparation. This is an entirely new install using the Quick Deploy, so its rather odd that I cant do anything else.

@olivierlambert When I go to register from the web interface, it seems to do nothing. If I try from the CLI, I get the above error message.

rkelley

@thenorthernlight said in New XOA setup, cant register:

@rkelley I already have the compiled XO version working without issue. However we are moving to paid support, so I'm setting up XOA in preparation. This is an entirely new install using the Quick Deploy, so its rather odd that I cant do anything else.

Gotcha - makes sense. Hope you get your issues sorted out.

TheNorthernLight

@olivierlambert If I try xoa-updater --register I get:

connect ECONNREFUSED 127.0.0.1:9001

If I try xoa-updater --upgrade I get:

Your xoa-updater service may not be running. Use xoa-updater-start to run it.

If I try xoa-updater-start , I get:

2021-12-10T13:47:05.363Z xoa-updater WARN registration from XenStore {
  error: Error: Command failed: xenstore-read vm-data/xoa-updater-credentials
  xenstore.Open error: open /proc/xen/xenbus: permission denied

      at ChildProcess.exithandler (child_process.js:319:12)
      at ChildProcess.emit (events.js:376:20)
      at ChildProcess.patchedEmit [as emit] (/usr/local/lib/node_modules/xoa-upd                               ater/node_modules/@xen-orchestra/log/dist/configure.js:115:17)
      at maybeClose (internal/child_process.js:1055:16)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) {
    killed: false,
    code: 1,
    signal: null,
    cmd: 'xenstore-read vm-data/xoa-updater-credentials'
  }
}
2021-12-10T13:47:05.398Z xoa-updater INFO WS Server listening { address: '::', f                               amily: 'IPv6', port: 9001 }
2021-12-10T13:47:05.400Z xoa-updater INFO HTTP Server listening { address: '127.                               0.0.1', family: 'IPv4', port: 9002 }

I may just try a re-install quickly to see if it helps.

olivierlambert

You need to restart the service as root/sudoer, eg sudo systemctl restart xoa-updater.

Note that you can have XOA support with our ticket system, even on XOA Free If you want someone at Vates dedicated to your issue, please create a ticket!