ECONNRESET on npm install

nodejs
npm

#1

Fairly often (but not always), I’m getting the following error on instilling lwip (the Node image processing library):

make: Leaving directory `/home/ubuntu/API/Avenue/node_modules/lwip/build'
npm ERR! Linux 3.13.0-86-generic
npm ERR! argv "/home/ubuntu/nvm/versions/node/v4.3.0/bin/node"     "/home/ubuntu/nvm/versions/node/v4.3.0/bin/npm" "install"
npm ERR! node v4.3.0
npm ERR! npm  v2.14.12
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! syscall read
npm ERR! network read ECONNRESET
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

Has anyone found a way of fixing this on CircleCI?


#2

Thanks for reporting this. Our current recommendation is to upgrade to a newer version of node. Currently the newest versions of node we have preinstalled are 5.5 and 6.1 on our 12.04 and 14.04 build images respectively. You can change the build image via the menu in Project settings > Build environment.

These GitHub issues give more context on this error: https://github.com/npm/registry/issues/10#issuecomment-217141066 and https://github.com/nodejs/node/issues/3595

Basically node and npm have bug fixes to improve their http handling in newer versions.

To see all versions of node available on our images go here for 12.04 and here for 14.04.


#3

I have the same issue.

I updated the node version by following https://circleci.com/docs/language-nodejs/#version


#4

Just to add information onto Tom’s post, users in the npm issues thread reported the following versions of Node fixed their issues:

  • >= 4.4.0
  • >= 5.4.0
  • >= 6.0.0

You should be able to upgrade your application Node version to any of the above major versions.


#5

I am using node version 7 and am currently getting this same problem after ssh’ing into the box


#6

This post is over two years old. Its likely that your issue is something else. Can you start a new thread with the following info:

  1. Specific version fo Node
  2. Which version of CircleCI you are using (1.0 vs 2.0)
  3. If 2.0 which container you are using

#7