Build error during upgrade
I am building from source. I have xo-server 5.50.1 and xo-web 5.50.3 installed. I am getting the following error, any guidance would be appreciated.
[15:17:49] 'buildScripts' errored after 2.02 min [15:17:49] Error: Cannot find module '@xen-orchestra/template' from '/opt/xen-orchestra/packages/xo-web/src/xo-app/new-vm' at /opt/xen-orchestra/node_modules/browser-resolve/node_modules/resolve/lib/async.js:46:17 at process (/opt/xen-orchestra/node_modules/browser-resolve/node_modules/resolve/lib/async.js:173:43) at ondir (/opt/xen-orchestra/node_modules/browser-resolve/node_modules/resolve/lib/async.js:188:17) at load (/opt/xen-orchestra/node_modules/browser-resolve/node_modules/resolve/lib/async.js:69:43) at onex (/opt/xen-orchestra/node_modules/browser-resolve/node_modules/resolve/lib/async.js:92:31) at /opt/xen-orchestra/node_modules/browser-resolve/node_modules/resolve/lib/async.js:22:47 at FSReqWrap.oncomplete (fs.js:152:21) [15:17:49] 'build' errored after 2.02 min
I've restored from a snapshot and rebuilt. Now the build process finished and everything seems to be working, but i did get following errors during the build:
Segmentation fault /usr/bin/env: error while loading shared libraries: libc.so.6: cannot map zero-fill pages Segmentation fault error Command failed with exit code 127. error Command failed with exit code 139. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. error Command failed with exit code 139. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
when the build finished i got this:
Successfully compiled 127 files with Babel. [15:43:40] Finished 'buildScripts' after 3.12 min [15:43:40] Finished 'build' after 3.12 min ✖ 4 error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Thanks for any insight..
Danp last edited by
I just rebuilt my VM without any issues, so it appears to be a localized problem. What process are you using to update the source and rebuild?
@Danp thanks for replying.
I do the standard update as per the wiki.
$ git pull --ff-only $ yarn $ yarn build
I have isolated the problem. The issue was with dynamic memory allocation on our test server. This was definitely a localized issue.