Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xo-server fails to start due to missing @xen-orchestra/xva #7344

Closed
ronivay opened this issue Jan 31, 2024 · 4 comments · Fixed by #7346
Closed

xo-server fails to start due to missing @xen-orchestra/xva #7344

ronivay opened this issue Jan 31, 2024 · 4 comments · Fixed by #7346

Comments

@ronivay
Copy link
Contributor

ronivay commented Jan 31, 2024

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

None

Provide your commit number

3ab2a83

Describe the bug

xo-server fails to start due to missing package @xen-orchestra/xva

Seems to be due to commit 2d047c4

Error message

Jan 31 02:07:56 foobar xo-server[62092]: node:internal/errors:496
Jan 31 02:07:56 foobar xo-server[62092]:     ErrorCaptureStackTrace(err);
Jan 31 02:07:56 foobar xo-server[62092]:     ^
Jan 31 02:07:56 foobar xo-server[62092]: Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@xen-orchestra/xva' imported from /opt/xo/xo-builds/xen-orchestra-202401310204/packages/xo-server/dist/xo-mixins/migrate-vm.mjs
Jan 31 02:07:56 foobar xo-server[62092]:     at new NodeError (node:internal/errors:405:5)
Jan 31 02:07:56 foobar xo-server[62092]:     at packageResolve (node:internal/modules/esm/resolve:916:9)
Jan 31 02:07:56 foobar xo-server[62092]:     at moduleResolve (node:internal/modules/esm/resolve:973:20)
Jan 31 02:07:56 foobar xo-server[62092]:     at defaultResolve (node:internal/modules/esm/resolve:1193:11)
Jan 31 02:07:56 foobar xo-server[62092]:     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:403:12)
Jan 31 02:07:56 foobar xo-server[62092]:     at ModuleLoader.resolve (node:internal/modules/esm/loader:372:25)
Jan 31 02:07:56 foobar xo-server[62092]:     at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:249:38)
Jan 31 02:07:56 foobar xo-server[62092]:     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
Jan 31 02:07:56 foobar xo-server[62092]:     at link (node:internal/modules/esm/module_job:75:36) {
Jan 31 02:07:56 foobar xo-server[62092]:   code: 'ERR_MODULE_NOT_FOUND'
Jan 31 02:07:56 foobar xo-server[62092]: }
Jan 31 02:07:56 foobar xo-server[62092]: Node.js v18.19.0

To reproduce

install xo-server from latest master branch and try to start it

Expected behavior

xo-server builds and runs correctly

Screenshots

No response

Node

v18.19.0

Hypervisor

XCP-ng 8.2.0

Additional context

No response

@TristisOris
Copy link

same problem

Jan 31 10:18:24 xo-rp xo-server[993037]: Node.js v18.19.0
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 4.
Jan 31 10:18:24 xo-rp systemd[1]: Stopped XO Server.
Jan 31 10:18:24 xo-rp systemd[1]: Started XO Server.
Jan 31 10:18:24 xo-rp xo-server[993061]: node:internal/errors:496
Jan 31 10:18:24 xo-rp xo-server[993061]:     ErrorCaptureStackTrace(err);
Jan 31 10:18:24 xo-rp xo-server[993061]:     ^
Jan 31 10:18:24 xo-rp xo-server[993061]: Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@xen-orchestra/xva' imported from /opt/xo/xo-builds/xen-orchestra-202401311010/pa>
Jan 31 10:18:24 xo-rp xo-server[993061]:     at new NodeError (node:internal/errors:405:5)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at packageResolve (node:internal/modules/esm/resolve:916:9)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at moduleResolve (node:internal/modules/esm/resolve:973:20)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at defaultResolve (node:internal/modules/esm/resolve:1193:11)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:403:12)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at ModuleLoader.resolve (node:internal/modules/esm/loader:372:25)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:249:38)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:39)
Jan 31 10:18:24 xo-rp xo-server[993061]:     at link (node:internal/modules/esm/module_job:75:36) {
Jan 31 10:18:24 xo-rp xo-server[993061]:   code: 'ERR_MODULE_NOT_FOUND'
Jan 31 10:18:24 xo-rp xo-server[993061]: }
Jan 31 10:18:24 xo-rp xo-server[993061]: Node.js v18.19.0
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
Jan 31 10:18:24 xo-rp systemd[1]: Stopped XO Server.
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Start request repeated too quickly.
Jan 31 10:18:24 xo-rp systemd[1]: xo-server.service: Failed with result 'exit-code'.
Jan 31 10:18:24 xo-rp systemd[1]: Failed to start XO Server.

@TristisOris
Copy link

rollback to 0f1dcda, no problems.

@fbeauchamp
Copy link
Collaborator

Hi Roni,
this is an import problem with our new import library, can you test if the branch #7346 fixes the problem ?
Regards

julien-f pushed a commit that referenced this issue Jan 31, 2024
Fix #7344
Introduced by 2d047c4

Cause: we did not run the normalize-package command after renaming
@ronivay
Copy link
Contributor Author

ronivay commented Jan 31, 2024

Hi Roni, this is an import problem with our new import library, can you test if the branch #7346 fixes the problem ? Regards

Yep, build from fix_xva_import branch starts successfully, thank you. I guess Julien already verified that :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants