Closed GeekBoxIT closed 6 years ago
Can you provide the link to the ISO you used?
The fact that you're on XCP-ng should be moot as the installation process is contained within the VM.
A few follow up questions:
Did you perform all system updates? Did you run the installation process as outlined in the readme? (Just confirming you followed the installation process as outlined in the readme).
error upath@1.0.4: The engine "node" is incompatible with this module. Expected version ">=4 <=9".
Please post the output of node -v
. Once you confirm that it is greater than 9, then suggest that you revert using sudo n LTS
I have Node version 9.10.1 on a working 17.10 system here. Something else is causing this.
Are you able to duplicate the issue? If not, then I suspect he is on Node 10.x
I was hoping OP would respond to my questions before I had to go and test again.
But I just went through this process the other day for another issue on ML and it worked without issue.
Right. It's possible that something changed in one of the upstream packages, but IMO more likely that they installed using some method other than this script.
Sorry guys, Mobile. Will answer as soon as I get back to office.
-- Erick Smith
On Apr 25, 2018, at 1:34 PM, Dustin B notifications@github.com wrote:
I was hoping OP would respond to my questions before I had to go and test again.
But I just went through this process the other day for another issue on ML and it worked without issue.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Jarli01/xenorchestra_installer/issues/12#issuecomment-384370662, or mute the thread https://github.com/notifications/unsubscribe-auth/APK76sH_N_hfTLL0O4s645cKBY-n9mzQks5tsLPDgaJpZM4TjuKm .
Running through the installation process now, I see Node version 9 is installed. Will confirm in a few minutes.
1vCPU vm 😃
Ohhh they did just release node v10.0.0
info fsevents@1.1.3: The platform "linux" is incompatible with this module.
info "fsevents@1.1.3" is an optional dependency and failed compatibility check. Excluding it from installation.
error upath@1.0.4: The engine "node" is incompatible with this module. Expected version ">=4 <=9".
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
yarn run v1.6.0
(node:18133) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
$ scripts/run-script --parallel build
internal/modules/cjs/loader.js:573
throw err;
^
Error: Cannot find module 'promise-toolbox'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:571:15)
at Function.Module._load (internal/modules/cjs/loader.js:497:25)
at Module.require (internal/modules/cjs/loader.js:626:17)
at require (internal/modules/cjs/helpers.js:20:18)
at Object.<anonymous> (/opt/xen-orchestra/scripts/run-script:4:32)
at Module._compile (internal/modules/cjs/loader.js:678:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10)
at Module.load (internal/modules/cjs/loader.js:589:32)
at tryModuleLoad (internal/modules/cjs/loader.js:528:12)
at Function.Module._load (internal/modules/cjs/loader.js:520:3)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Created symlink /etc/systemd/system/multi-user.target.wants/xo-server.service → /lib/systemd/system/xo-server.service.
Installation complete, open a browser to:
10.200.105.135
Default Login:admin@admin.net Password:admin
Don't forget to change your password!
root@xoce:~# node -v
v10.0.0
You should be able to manually fix this by running the following commands from the main xen-orchestra subdirectory --
sudo n LTS
sudo yarn
sudo yarn build
@GeekBoxIT please try this
rm -rf /opt/xen-orchestra
sudo bash
single linesudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/af71f0d366b71c5ea45e1dd3ca6c1760e153e39c/xo_install.sh | bash
EoL
I have a beta fix there, need people to test it.
@Danp2 LTS should be lowercase, but yes, after running
sudo n lts
sudo yarn
sudo yarn build
in /opt/xen-orchestra it's building, but failed with the following...
* xo-web:build − Error: 137
✖ 1
error Command failed with exit code 1.
@Jarli01 I will spin up a fresh VM of 17.10 and test that now. Edit: The beta worked on fresh and on original with issue after rm -rf /opt/xen-orchestra.
@Jarli01 The following one worked for me on a fresh 17.10 install.
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/9689585263d4025cd74768a0db15aceb280125c6/xo_install.sh | bash
Completing another test here before I merge.
This issue is fixed in #13 please let us know if you have further issues!
Thanks for your support in finding this!
Expected Behavior
New install of XOCE in a fresh Ubuntu 17.10 minimal VM on XCP-ng
Actual Behavior
Error:
Confirm XOCE services are running
systemctl status xo-server.service
Failed.Provide the output of journalctl logs
journalctl -u xo-server -f -n 50
Provide answers to these questions:
Fresh install, XCP-ng, script install