Skip to content
This repository was archived by the owner on Apr 29, 2020. It is now read-only.

EADDRINUSE on macos worker #105

Closed
victorb opened this issue Aug 13, 2018 · 5 comments
Closed

EADDRINUSE on macos worker #105

victorb opened this issue Aug 13, 2018 · 5 comments

Comments

@victorb
Copy link
Contributor

victorb commented Aug 13, 2018

From @vmx on March 15, 2018 14:29

Having an EADDRINUSE error happened before, here's one case:
https://ci.ipfs.team/blue/organizations/jenkins/IPFS%2Fjs-ipfs-api/detail/get-ci-green/37/pipeline/14

[FS_js-ipfs-api_get-ci-green-F27XKKY5E6RA6ONRZJ3Q7HHMNHH5DJB4UA7HUYD2FFZMKXYOPBIQ] Running shell script

+ ./node_modules/.bin/yarn test

yarn run v1.5.1

$ aegir test

Test Node.js

listen EADDRINUSE 127.0.0.1:43134

Error: listen EADDRINUSE 127.0.0.1:43134

    at Object._errnoException (util.js:1031:13)

    at _exceptionWithHostPort (util.js:1052:20)

    at Server.setupListenHandle [as _listen2] (net.js:1367:14)

    at listenInCluster (net.js:1408:12)

    at GetAddrInfoReqWrap.doListen [as callback] (net.js:1523:7)

    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:102:10)

error An unexpected error occurred: "Command failed.

Exit code: 1

Command: sh

Arguments: -c aegir test

Directory: /private/var/jenkins/workspace/FS_js-ipfs-api_get-ci-green-F27XKKY5E6RA6ONRZJ3Q7HHMNHH5DJB4UA7HUYD2FFZMKXYOPBIQ

Output:

".

info If you think this is a bug, please open a bug report with the information provided in "/private/var/jenkins/workspace/FS_js-ipfs-api_get-ci-green-F27XKKY5E6RA6ONRZJ3Q7HHMNHH5DJB4UA7HUYD2FFZMKXYOPBIQ/yarn-error.log".

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Copied from original issue: ipfs-inactive/jenkins#97

@victorb
Copy link
Contributor Author

victorb commented Aug 13, 2018

From @vmx on March 15, 2018 16:2

It seems to happen on worker macstadium-macos-69e8c913 only.

@victorb
Copy link
Contributor Author

victorb commented Aug 13, 2018

From @Kubuxu on March 15, 2018 16:59

Is js using random port? IIRC form our previous experiences with MacOS on TeamCity, sometimes program instances were not closed after test finished which meant that if static port was used it would be failing.

@victorb
Copy link
Contributor Author

victorb commented Aug 13, 2018

I've turned off the worker for now and will look into the exact cause of npm going missing.

@Kubuxu most tests are using random port but some things are not. Wrote some more about it here: ipfs/js-ipfsd-ctl#212 (comment)

@daviddias
Copy link
Contributor

Still an issue?

@vmx
Copy link

vmx commented Dec 4, 2018

I haven't seen this in a long time, hence closing.

@vmx vmx closed this as completed Dec 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants