building from source - yarn fetch error

skottib

Hi,
I am trying to build xen-orchestra from the sources on recent Debian stretch and buster netinstalls.

It always fails at fetching a nodejs package.

This is on Debian Stretch:

Node:


root@xoce:~/xen-orchestra# node --version
v8.17.0
root@xoce:~/xen-orchestra# whereis node
node: /usr/bin/node /usr/include/node /usr/share/man/man1/node.1.gz


root@xoce:~/xen-orchestra# yarn build
yarn run v1.21.1
$ scripts/run-script --parallel build
module.js:550
    throw err;

Error: Cannot find module 'promise-toolbox'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/root/xen-orchestra/scripts/run-script:4:32)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
error Command failed with exit code 1.

I have attached yarn.lock & yarn-error.log

yarn.lock.txt
yarn-error.log.txt

thx
Sven

Danp

Did you run the command yarn before running yarn build?

skottib

I did:

root@xoce:~/xen-orchestra# yarn
yarn install v1.21.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
error An unexpected error occurred: "https://github.com/dodo/reconnect-core/tarball/merged: getaddrinfo ENOTFOUND codeload.github.com codeload.github.com:443".
info If you think this is a bug, please open a bug report with the information provided in "/root/xen-orchestra/yarn-error.log".

Danp

You will need to figure out this networking issue first. It may just be a temporary issue with the package provider.

FWIW, I just ran this on my local installation and it worked fine, so I'm guessing that your VM doesn't have access to the internet for some reason.

olivierlambert

@skottib please use Markdown syntax for your console/code copy/paste. I edited your post accordingly.

skottib

guys, it is solved, but thats something i will file again under technological harrassment.

it was a DNS Problem. the dns-servers at my hosting provider woudnt resolve properly, only when I forced googles DNS servers onto it did it work.

thanks for the push