[bug] socket hang up #668

iyn · 2016-10-11T17:49:08Z

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When running yarn with existing (and correct) package.json and empty node_modules I get socket hang up error on a X package. Next time I run yarn I get the same error, but for Y package.

Example output:

$ yarn                                                                                                                                                                   
yarn install v0.15.1
info No lockfile found.
[1/4] Resolving packages...
error https://registry.yarnpkg.com/semver: socket hang up
    at createHangUpError (_http_client.js:252:15)
    at TLSSocket.socketCloseListener (_http_client.js:284:23)
    at emitOne (events.js:101:20)
    at TLSSocket.emit (events.js:188:7)
    at TCP._handle.close [as _onclose] (net.js:493:12)

If the current behavior is a bug, please provide the steps to reproduce.
Hard to think of steps to reproduce the issue. Below are my dependencies:

  "dependencies": {
    "axios": "^0.14.0",
    "babel-polyfill": "^6.13.0",
    "babel-runtime": "^6.11.6",
    "classnames": "^2.2.5",
    "dom-helpers": "^2.4.0",
    "elemental": "^0.6.1",
    "flexboxgrid": "^6.3.1",
    "get-env": "^0.5.1",
    "icheck": "^1.0.2",
    "immutable": "^3.8.1",
    "js-combinatorics": "^0.5.2",
    "localforage": "^1.4.2",
    "lodash": "^4.15.0",
    "moment": "^2.15.1",
    "moment-duration-format": "^1.3.0",
    "normalizr": "^2.2.1",
    "qs": "^6.2.1",
    "ramda": "^0.22.1",
    "rc-time-picker": "^2.0.2",
    "react": "^15.3.2",
    "react-addons-css-transition-group": "^15.3.2",
    "react-addons-shallow-compare": "^15.3.2",
    "react-addons-transition-group": "^15.3.2",
    "react-dates": "^3.1.1",
    "react-dom": "^15.3.2",
    "react-flexbox-grid": "^0.10.2",
    "react-highlight-words": "^0.4.1",
    "react-icheck": "^0.3.5",
    "react-popover": "^0.4.4",
    "react-redux": "^5.0.0-beta.3",
    "react-responsive": "^1.1.5",
    "react-router": "^2.7.0",
    "react-router-redux": "^4.0.5",
    "react-select": "^1.0.0-rc.1",
    "react-selectize": "^2.0.3",
    "react-skylight": "^0.4.1",
    "react-smooth-collapse": "^1.1.0",
    "react-tabs": "^0.8.0",
    "react-virtualized": "^8.0.11",
    "reactstrap": "^3.4.0",
    "recharts": "^0.14.1",
    "redux": "^3.6.0",
    "redux-actions": "^0.12.0",
    "redux-form": "^6.1.0",
    "redux-logger": "^2.6.1",
    "redux-logic": "^0.9.3",
    "redux-thunk": "^2.1.0",
    "reselect": "^2.5.4",
    "rxjs": "^5.0.0-beta.12",
    "tether": "^1.3.7",
    "uuid-js": "^0.7.5"
  },
  "devDependencies": {
    "autoprefixer": "^6.4.0",
    "babel-core": "^6.14.0",
    "babel-eslint": "^6.1.2",
    "babel-loader": "^6.2.5",
    "babel-plugin-transform-class-properties": "^6.11.5",
    "babel-plugin-transform-object-rest-spread": "^6.8.0",
    "babel-plugin-transform-runtime": "^6.12.0",
    "babel-preset-es2015": "^6.14.0",
    "babel-preset-es2016": "^6.11.3",
    "babel-preset-es2017": "^6.14.0",
    "babel-preset-react": "^6.11.1",
    "css-loader": "^0.24.0",
    "eslint": "^3.4.0",
    "eslint-config-airbnb-base": "^5.0.3",
    "eslint-import-resolver-webpack": "^0.5.1",
    "eslint-plugin-import": "^1.14.0",
    "eslint-plugin-jsx-a11y": "^2.2.0",
    "eslint-plugin-lodash-fp": "^2.0.1",
    "eslint-plugin-react": "^6.2.0",
    "extract-text-webpack-plugin": "^2.0.0-beta.4",
    "file-loader": "^0.9.0",
    "handlebars": "^4.0.5",
    "handlebars-loader": "^1.3.0",
    "html-webpack-plugin": "^2.22.0",
    "node-sass": "^3.10.1",
    "postcss-loader": "^0.11.1",
    "postcss-modules-values": "^1.2.2",
    "postcss-scss": "^0.2.1",
    "postcss-strip-inline-comments": "^0.1.5",
    "precss": "^1.4.0",
    "react-immutable-proptypes": "^2.1.0",
    "react-moment-proptypes": "^1.2.0",
    "sass-loader": "^4.0.2",
    "source-map-loader": "^0.1.5",
    "style-loader": "^0.13.1",
    "stylelint": "^7.2.0",
    "stylelint-config-standard": "^13.0.0",
    "stylelint-webpack-plugin": "^0.3.1",
    "url-loader": "^0.5.7",
    "webpack": "2.1.0-beta.21",
    "webpack-dashboard": "^0.1.8",
    "webpack-dev-server": "2.1.0-beta.1"
  }

What is the expected behavior?
Yarn should install all packages, npm works just fine with my current setup.

Please mention your node.js, yarn and operating system version.
yarn: 0.15.1
OS: Linux 4.7.6-1
node: v6.6.0

I suppose this may be the problem with servers being overloaded but I'm posting this issue in case there's something else and this is in fact some bug.

The text was updated successfully, but these errors were encountered:

iyn · 2016-10-11T18:26:54Z

OK, it seems that it's not yarn specific problem. I've just run npm install and it also failed (where it was ok very recently). The npm error log is more verbose though:


> [email protected] install /home/user/projects/p1/node_modules/node-sass
> node scripts/install.js

Start downloading binary at https://github.com/sass/node-sass/releases/download/v3.10.1/linux-x64-48_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.10.1/linux-x64-48_binding.node": ode:

ESOCKETTIMEDOUT

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

> [email protected] postinstall /home/user/projects/p1/node_modules/node-sass
> node scripts/build.js

"/home/user/projects/p1/node_modules/node-sass/vendor/linux-x64-48/binding.node" exists.
 testing binary.
[1]    23887 bus error (core dumped)  npm install

annapoulakos · 2016-10-11T19:55:28Z

I am getting the socket hang up issue also, but do not get the issue when running npm install

From my package.json:

  "dependencies": {
    "pg": "^6.1.0"
  },
  "devDependencies": {
    "jasmine": "^2.5.2",
    "jasmine-spec-reporter": "^2.7.0",
    "mock-require": "^1.3.0"
  }

λ yarn install
yarn install v0.15.1
info No lockfile found.
warning [email protected]: No license field
[1/4] Resolving packages...
error socket hang up
    at TLSSocket.onHangUp (_tls_wrap.js:1049:19)
    at TLSSocket.g (events.js:260:16)
    at emitNone (events.js:72:20)
    at TLSSocket.emit (events.js:166:7)
    at endReadableNT (_stream_readable.js:913:12)
    at nextTickCallbackWith2Args (node.js:442:9)
    at process._tickCallback (node.js:356:17)
info Visit http://yarnpkg.com/en/docs/cli/install for documentation about this command.

One thing I do know is that our corporate firewall is currently blocking yarnpkg.com and should hopefully be cleared up tomorrow some time. Not sure if this is an issue.

gitnik · 2016-10-12T14:17:31Z

This is also happening to me. But like for @jimpoulakos , npm i is working fine

jromero2k · 2016-10-12T20:01:05Z

Windows 10, 512kbps... I can't finish any install. Lots of (random) socket hang ups. NPM works properly most of the time

Example:

yarn add v0.15.1
info No lockfile found.
[1/4] Resolving packages...
error https://registry.yarnpkg.com/babel-preset-es2015-node: socket hang up
at createHangUpError (_http_client.js:252:15)
at TLSSocket.socketOnEnd (_http_client.js:344:23)
at emitNone (events.js:91:20)
at TLSSocket.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

iyn · 2016-10-12T20:13:46Z

I'm reopening this issue, since other people seem to be affected by it.

kabirbaidhya · 2016-10-13T04:42:26Z

Not sure if this issue has been fixed but I'm also getting the same issue when doing yarn with empty node_modules directory. I have tested it with npm install and it works correctly though without any problem.

But yarn gives this error and halts:

 ➜ yarn
yarn install v0.15.1
info No lockfile found.
[1/4] Resolving packages...
warning grunt > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning grunt > glob > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning grunt-modernizr > customizr > glob > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning wiredep > glob > [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
warning grunt-modernizr > customizr > [email protected]: use [cross-spawn](https://github.com/IndigoUnited/node-cross-spawn) or [cross-spawn-async](https://github.com/IndigoUnited/node-cross-spawn-async) instead.
warning generator-jhipster > yo > [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
warning generator-jhipster > yeoman-generator > cross-spawn > [email protected]: cross-spawn no longer requires a build toolchain, use it instead!
warning grunt > glob > [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
warning wiredep > bower-config > [email protected]: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
warning protractor > request > [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
warning yo > fullname > [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
error https://registry.yarnpkg.com/binary-extensions: socket hang up
    at createHangUpError (_http_client.js:250:15)
    at TLSSocket.socketCloseListener (_http_client.js:282:23)
    at emitOne (events.js:101:20)
    at TLSSocket.emit (events.js:188:7)
    at TCP._handle.close [as _onclose] (net.js:485:12)
info Visit http://yarnpkg.com/en/docs/cli/install for documentation about this command.

younesmln · 2016-10-13T23:33:15Z

same problem here "socket hang up"

keysona · 2016-10-14T03:09:45Z

Same problem about "socket hang up"
I set a http_proxy.

yofine · 2016-10-14T03:17:23Z

I am getting the socket hang up issue too

yoohan-dex · 2016-10-14T07:01:53Z

it's happening to me

sxcsfan · 2016-10-14T07:52:34Z

Same problem here.

abdulhaq-e · 2016-10-15T00:30:51Z

Same problem. The error appears randomly at different packages. Here is a sample:

error https://registry.yarnpkg.com/postcss-modules-extract-imports: socket hang up
at createHangUpError (_http_client.js:252:15)
at TLSSocket.socketCloseListener (_http_client.js:284:23)
at emitOne (events.js:101:20)
at TLSSocket.emit (events.js:188:7)
at TCP._handle.close as _onclose
info Visit http://yarnpkg.com/en/docs/cli/install for documentation about this command.

It doesn't matter if a node_modules directory exist or not. npm i works fine. If I didn't find this thread and due to the randomness of the error, I would have thrown the blame on my horrible ISP. However, surely not everyone here has a stone age internet connection!

masihyeganeh · 2016-10-15T09:55:33Z

Same here.
I think it is related to Internet speed.
I'm not sure how Yarn works internally but I believe it fetches more than one package at a time with no limit (correct me if I'm wrong), so with weak/slow internet connections it produces many random socket hang ups and timeouts.
I tried to install angular-cli for days and couldn't succeed but with npm it installs with no problem.
It I am right, there should be a way to limit concurrent connections.

iyn · 2016-10-15T18:50:41Z

@masihyeganeh I think you are right. I just came home where I have regular internet connection and yarn works as expected (whereas when I had this error, I was on unstable mobile connection). Also agree, that it would be good to have the feature to limit opened sockets.

shinygang · 2016-10-17T03:34:20Z

Same problem here.

kabirbaidhya · 2016-10-17T04:12:32Z

I think this is one of the major issues as I couldn't start working on a existing project using yarn after I did rm -rf node_modules/ and tried yarn, as the installation wouldn't just complete. So, I have to fallback to npm install anyway to make it work.
However, this works in the projects with only few dependencies. But for the projects with large number of dependencies it fails with this socket hang up error.

kshern · 2016-10-17T08:46:06Z

Same problem here.

michel-kraemer · 2016-10-17T09:07:43Z

I think it is related to Internet speed.

I can confirm this. At home I only have 2Mbit/s and it does not work there. At work I have a decently fast Internet connection and I don't get any errors.

johmsalas · 2016-10-18T03:08:11Z

I agree, bandwidth is the problem. After 5 attempts I moved closer to the router and it is working

keysona · 2016-10-18T09:53:16Z

@masihyeganeh
@michel-kraemer
I agree.
It's network speed problem.

Catorpilor · 2016-10-18T14:59:23Z

Same problem here.

michel-kraemer · 2016-10-19T17:33:12Z

It seems to be fixed in 0.16.0. Can anyone confirm this?

alextes · 2016-10-19T18:57:06Z

That's hard to say of course @michel-kraemer. I don't think anyone has consistently reproduced it.
I can say I'm seeing warning There appears to be trouble with your network connection. Retrying... haven't seen that before and I have seen the socket hangup on this network.
However now I'm getting an ETIMEDOUT error which is perhaps related. ~~I'll create a new issue~~

alextes · 2016-10-19T19:01:23Z

I reproduced the ETIMEDOUT 3 times, then the fourth time it worked. The error in yarn-error.log is:

Trace:
Error: read ETIMEDOUT
at exports._errnoException (util.js:1026:11)
at TLSWrap.onread (net.js:569:26)
Would you like a new issue for this or is this still considered the same problem?

Fast.com shows 20 Mbps internet.
Simple ping test:
--- google.com ping statistics ---
32 packets transmitted, 32 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 4.681/10.677/44.197/11.293 ms

jromero2k · 2016-10-19T19:16:04Z

With v0.16.0 now I get:

[2/4] Fetching packages...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
error An unexpected error occured, please open a bug report with the information provided in "***\yarn-error.log".

and yarn-error.log contains:

Trace:
Error: read ECONNRESET
at exports._errnoException (util.js:1036:11)
at TLSWrap.onread (net.js:564:26)

alextes · 2016-10-19T19:25:59Z

That's exactly what I just described @jromero2k.

alextes · 2016-10-20T08:47:20Z

What I was trying to say in the comment right above yours @george3447 is please use github's reactions feature. Maintainers of this repo will likely be drowning in messages to go through as is 😉 . Also we won't all get notified of your +1's or duplicate messages.

hustcer · 2016-10-21T01:05:54Z

yarn v0.16.0
node v6.9.1
macOS v10.12

warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
...

however, npm works fine.

alextes · 2016-10-21T12:32:20Z

Yarn connects to wholly different servers though so npm working where Yarn doesn't that might just be a bad connection to the Yarn proxy repo. Still that shouldn't cause exceptions.

bsed · 2016-11-12T04:19:07Z

[1/4] Resolving packages...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
warning There appears to be trouble with your network connection. Retrying...
error An unexpected error occured, please open a bug report with the information provided in "/home/kelvin/workspace/nodejs/Mean-Blog/server/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

alextes · 2016-11-14T12:37:55Z

@bsed Why not use githubs' reactions feature?

rccoder · 2017-03-19T11:52:45Z

Yep. Same problem here. But when i checkouted another network, It become ok

voxsim · 2017-04-28T16:29:59Z

@bestander for what I understand we can close this in favor of more specific issues.

shleycarter · 2018-06-25T20:55:03Z

I was able to solve this problem by disabling my antivirus (Malwarebytes in my case).

davquar · 2018-07-04T08:58:01Z

Like @shleycarter, I also solved by disabling Malwarebytes

SDMitchell · 2018-08-16T01:22:39Z

Indeed Malwarebytes was the culprit in my case as well. For future reference, I was trying to install JHipster when it happened (yarn global add generator-jhipster).

alienfractal · 2018-10-30T13:54:36Z

Any news on this ???

3dots · 2018-12-15T20:33:23Z

Running on ubuntu app in Windows 10, trying to compile angular.

Yarn version:
1.12.3

Node version:
10.14.2

Platform:
linux x64

Trace:
Error: https://registry.yarnpkg.com/bower/-/bower-1.8.2.tgz: ESOCKETTIMEDOUT
at ClientRequest. (/mnt/c/Program Files (x86)/Yarn/lib/cli.js:129645:19)
at Object.onceWrapper (events.js:273:13)
at ClientRequest.emit (events.js:182:13)
at TLSSocket.emitRequestTimeout (_http_client.js:662:40)
at Object.onceWrapper (events.js:273:13)
at TLSSocket.emit (events.js:182:13)
at TLSSocket.Socket._onTimeout (net.js:453:8)
at ontimeout (timers.js:436:11)
at tryOnTimeout (timers.js:300:5)
at listOnTimeout (timers.js:263:5)

HamidOsouli-zz · 2020-09-12T10:29:19Z

Any working solution?

iyn closed this as completed Oct 11, 2016

AlicanC mentioned this issue Oct 12, 2016

Error when run Install: socket hang up #912

Closed

iyn reopened this Oct 12, 2016

sebmck added the needs triage label Oct 14, 2016

muddlebee mentioned this issue Dec 23, 2016

Unable to connect to the address ? Cloud-CV/Origami#27

Closed

TobiahRex mentioned this issue Mar 22, 2017

Implement React [email protected] coryhouse/react-slingshot#393

Merged

bestander closed this as completed Apr 28, 2017

bestander added bug-resolution triaged and removed needs triage labels Apr 28, 2017

[bug] socket hang up #668

[bug] socket hang up #668

Comments

iyn commented Oct 11, 2016

iyn commented Oct 11, 2016

annapoulakos commented Oct 11, 2016

gitnik commented Oct 12, 2016

jromero2k commented Oct 12, 2016

iyn commented Oct 12, 2016

kabirbaidhya commented Oct 13, 2016 • edited Loading

younesmln commented Oct 13, 2016

keysona commented Oct 14, 2016

yofine commented Oct 14, 2016

yoohan-dex commented Oct 14, 2016

sxcsfan commented Oct 14, 2016

abdulhaq-e commented Oct 15, 2016

masihyeganeh commented Oct 15, 2016

iyn commented Oct 15, 2016

shinygang commented Oct 17, 2016

kabirbaidhya commented Oct 17, 2016

kshern commented Oct 17, 2016

michel-kraemer commented Oct 17, 2016

johmsalas commented Oct 18, 2016

keysona commented Oct 18, 2016

Catorpilor commented Oct 18, 2016

michel-kraemer commented Oct 19, 2016

alextes commented Oct 19, 2016 • edited Loading

alextes commented Oct 19, 2016 • edited Loading

jromero2k commented Oct 19, 2016

alextes commented Oct 19, 2016

alextes commented Oct 20, 2016 • edited Loading

hustcer commented Oct 21, 2016

alextes commented Oct 21, 2016

bsed commented Nov 12, 2016

alextes commented Nov 14, 2016

rccoder commented Mar 19, 2017

voxsim commented Apr 28, 2017

shleycarter commented Jun 25, 2018

davquar commented Jul 4, 2018

SDMitchell commented Aug 16, 2018 • edited Loading

alienfractal commented Oct 30, 2018

3dots commented Dec 15, 2018 • edited Loading

HamidOsouli-zz commented Sep 12, 2020

kabirbaidhya commented Oct 13, 2016 •

edited

Loading

alextes commented Oct 19, 2016 •

edited

Loading

alextes commented Oct 19, 2016 •

edited

Loading

alextes commented Oct 20, 2016 •

edited

Loading

SDMitchell commented Aug 16, 2018 •

edited

Loading

3dots commented Dec 15, 2018 •

edited

Loading