Getting sporadic 500 code responses on installing NPM dependencies #4084

Closed
rsolomon opened this Issue Nov 4, 2013 · 32 comments

Comments

Projects
None yet
@rsolomon

rsolomon commented Nov 4, 2013

npm http 500 https://registry.npmjs.org/grunt-jsonlint/1.0.1
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/grunt-contrib-copy/0.4.1
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/assemble/0.4.6
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/grunt-contrib-clean/0.5.0
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/grunt-contrib-symlink/0.2.0
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/qunitjs/1.12.0
npm ERR! registry error parsing json
npm ERR! fetch failed https://registry.npmjs.org/karma-junit-reporter/-/karma-junit-reporter-0.1.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma-phantomjs-launcher/-/karma-phantomjs-launcher-0.1.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma-coverage/-/karma-coverage-0.1.0.tgz
npm http 500 https://registry.npmjs.org/grunt-contrib-copy/0.4.1
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/less/1.4.2
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/grunt-contrib-clean/0.5.0
npm ERR! registry error parsing json
npm http 500 https://registry.npmjs.org/grunt-contrib-symlink/0.2.0
npm ERR! registry error parsing json

Looks like this has been happening all weekend.

@tvanhens

This comment has been minimized.

Show comment Hide comment
@tvanhens

tvanhens Nov 4, 2013

I am as well. just started for me today.

tvanhens commented Nov 4, 2013

I am as well. just started for me today.

@kbaribeau

This comment has been minimized.

Show comment Hide comment
@kbaribeau

kbaribeau Nov 4, 2013

For what it's worth I'm also seeing this.

For what it's worth I'm also seeing this.

@luk-

This comment has been minimized.

Show comment Hide comment
@luk-

luk- Nov 4, 2013

Contributor

npm is broken right now, so that's why you're seeing this.

Contributor

luk- commented Nov 4, 2013

npm is broken right now, so that's why you're seeing this.

@oaksagelew

This comment has been minimized.

Show comment Hide comment
@oaksagelew

oaksagelew Nov 4, 2013

Same here - unable to compile anything for last 1/2 hour.

Same here - unable to compile anything for last 1/2 hour.

@k3mist

This comment has been minimized.

Show comment Hide comment
@k3mist

k3mist Nov 4, 2013

been trying for the past hour myself

k3mist commented Nov 4, 2013

been trying for the past hour myself

@occasl

This comment has been minimized.

Show comment Hide comment
@occasl

occasl Nov 4, 2013

I'm down too since 10:30...bummer, trying to deploy for production release.

occasl commented Nov 4, 2013

I'm down too since 10:30...bummer, trying to deploy for production release.

@ctumolosus

This comment has been minimized.

Show comment Hide comment
@ctumolosus

ctumolosus Nov 4, 2013

Same here, haven't been able to run npm install since 1:30 EST

Same here, haven't been able to run npm install since 1:30 EST

@janderson99

This comment has been minimized.

Show comment Hide comment
@janderson99

janderson99 Nov 4, 2013

+1, same here. unable to do installs since before lunch time.

+1, same here. unable to do installs since before lunch time.

@h0x91b

This comment has been minimized.

Show comment Hide comment
@h0x91b

h0x91b Nov 4, 2013

me too, random 500 error on npm install

npm http 500 https://registry.npmjs.org/insight
npm ERR! registry error parsing json

h0x91b commented Nov 4, 2013

me too, random 500 error on npm install

npm http 500 https://registry.npmjs.org/insight
npm ERR! registry error parsing json

@pandringa

This comment has been minimized.

Show comment Hide comment
@pandringa

pandringa Nov 4, 2013

+1, for me it seems to sporadically work sometimes, but not work others.

+1, for me it seems to sporadically work sometimes, but not work others.

@doberkofler

This comment has been minimized.

Show comment Hide comment
@doberkofler

doberkofler Nov 4, 2013

+1, for me over here in Europe

+1, for me over here in Europe

@my8bird

This comment has been minimized.

Show comment Hide comment
@my8bird

my8bird Nov 4, 2013

We have been fighting this all morning with our build system hanging/timing out trying to reach npm also.

my8bird commented Nov 4, 2013

We have been fighting this all morning with our build system hanging/timing out trying to reach npm also.

@my8bird

This comment has been minimized.

Show comment Hide comment
@my8bird

my8bird Nov 4, 2013

For what it is worth I tried doing npm search "woot" and after a little while this was the output.

C:\src\p5\taccs>npm search "woot"
npm WARN Building the local index for the first time, please be patient
npm http GET https://registry.npmjs.org/-/all
npm http GET https://registry.npmjs.org/-/all
npm http GET https://registry.npmjs.org/-/all
npm ERR! Error: socket hang up
npm ERR!     at createHangUpError (http.js:1445:15)
npm ERR!     at CleartextStream.socketCloseListener (http.js:1495:23)
npm ERR!     at CleartextStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at tls.js:677:10
npm ERR!     at process._tickCallback (node.js:415:13)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "search" "woot"
npm ERR! cwd C:\src\p5\taccs
npm ERR! node -v v0.10.10
npm ERR! npm -v 1.2.25
npm ERR! code ECONNRESET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\src\p5\taccs\npm-debug.log
npm ERR! not ok code 0

my8bird commented Nov 4, 2013

For what it is worth I tried doing npm search "woot" and after a little while this was the output.

C:\src\p5\taccs>npm search "woot"
npm WARN Building the local index for the first time, please be patient
npm http GET https://registry.npmjs.org/-/all
npm http GET https://registry.npmjs.org/-/all
npm http GET https://registry.npmjs.org/-/all
npm ERR! Error: socket hang up
npm ERR!     at createHangUpError (http.js:1445:15)
npm ERR!     at CleartextStream.socketCloseListener (http.js:1495:23)
npm ERR!     at CleartextStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at tls.js:677:10
npm ERR!     at process._tickCallback (node.js:415:13)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "search" "woot"
npm ERR! cwd C:\src\p5\taccs
npm ERR! node -v v0.10.10
npm ERR! npm -v 1.2.25
npm ERR! code ECONNRESET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\src\p5\taccs\npm-debug.log
npm ERR! not ok code 0
@MikeHuntington

This comment has been minimized.

Show comment Hide comment
@MikeHuntington

MikeHuntington Nov 4, 2013

+1 The problem seems to be an off and on issue.

+1 The problem seems to be an off and on issue.

@rsolomon

This comment has been minimized.

Show comment Hide comment
@rsolomon

rsolomon Nov 4, 2013

Looks like they are working on it. From their twitter:

having some sporadic internal routing latency problems affecting website and registry availability. @izs and @_jhs are on the case.

rsolomon commented Nov 4, 2013

Looks like they are working on it. From their twitter:

having some sporadic internal routing latency problems affecting website and registry availability. @izs and @_jhs are on the case.
@mteece

This comment has been minimized.

Show comment Hide comment
@mteece

mteece Nov 4, 2013

Same here on Windows and OS X. Sporadic and inconsistent.

mteece commented Nov 4, 2013

Same here on Windows and OS X. Sporadic and inconsistent.

@jewelsjacobs

This comment has been minimized.

Show comment Hide comment
@jewelsjacobs

jewelsjacobs Nov 4, 2013

👍 me too

👍 me too

This comment has been minimized.

Show comment Hide comment
@ghost

ghost Nov 4, 2013

Same here. On npm update as well (npm -g update is horribly slow and fails often, breaking installation scripts).

ghost commented Nov 4, 2013

Same here. On npm update as well (npm -g update is horribly slow and fails often, breaking installation scripts).

@grahamb

This comment has been minimized.

Show comment Hide comment
@grahamb

grahamb Nov 4, 2013

The Australian mirror appears to be working normally:

npm --registry http://npm.nodejs.org.au:5984/registry/_design/app/_rewrite install

grahamb commented Nov 4, 2013

The Australian mirror appears to be working normally:

npm --registry http://npm.nodejs.org.au:5984/registry/_design/app/_rewrite install

@kbaribeau

This comment has been minimized.

Show comment Hide comment
@kbaribeau

kbaribeau Nov 4, 2013

Thanks @grahamb, that's a huge help.

Thanks @grahamb, that's a huge help.

@fresheneesz

This comment has been minimized.

Show comment Hide comment
@fresheneesz

fresheneesz Nov 4, 2013

I am looking into using this cache server because of this issue: https://github.com/mixu/npm_lazy

I am looking into using this cache server because of this issue: https://github.com/mixu/npm_lazy

@fresheneesz

This comment has been minimized.

Show comment Hide comment
@fresheneesz

fresheneesz Nov 4, 2013

@grahamb thanks for the info, but I'm getting the error "Error: unauthorized Name or password is incorrect.: registry/_design/app/_rewrite/minimatch" - is this because I don't have an account on the austrailian mirror?

@grahamb thanks for the info, but I'm getting the error "Error: unauthorized Name or password is incorrect.: registry/_design/app/_rewrite/minimatch" - is this because I don't have an account on the austrailian mirror?

@kevinknoll

This comment has been minimized.

Show comment Hide comment
@kevinknoll

kevinknoll Nov 4, 2013

Same here. Super slow and sporadic 500s. @grahamb is the hero here with the Aussie mirror.

Same here. Super slow and sporadic 500s. @grahamb is the hero here with the Aussie mirror.

@grahamb

This comment has been minimized.

Show comment Hide comment
@grahamb

grahamb Nov 4, 2013

@fresheneesz sorry, no idea. It's working normally for me.

@kevinknoll thanks, but I can't take credit - I found it via twitter: https://twitter.com/mox4/status/397461681304907776

grahamb commented Nov 4, 2013

@fresheneesz sorry, no idea. It's working normally for me.

@kevinknoll thanks, but I can't take credit - I found it via twitter: https://twitter.com/mox4/status/397461681304907776

@jubis

This comment has been minimized.

Show comment Hide comment
@jubis

jubis Nov 4, 2013

Having the same problem too. I also tried to deploy to Heroku: unsuccessful

jubis commented Nov 4, 2013

Having the same problem too. I also tried to deploy to Heroku: unsuccessful

@yjukaku

This comment has been minimized.

Show comment Hide comment
@yjukaku

yjukaku Nov 4, 2013

Australian mirror is working for me too:

npm --registry http://npm.nodejs.org.au:5984/registry/_design/app/_rewrite install *package-name*

yjukaku commented Nov 4, 2013

Australian mirror is working for me too:

npm --registry http://npm.nodejs.org.au:5984/registry/_design/app/_rewrite install *package-name*
@mjw56

This comment has been minimized.

Show comment Hide comment
@mjw56

mjw56 Nov 5, 2013

Is it possible to have my app use a mirror when deploying to heroku?

mjw56 commented Nov 5, 2013

Is it possible to have my app use a mirror when deploying to heroku?

@dmourati

This comment has been minimized.

Show comment Hide comment
@dmourati

dmourati Nov 5, 2013

Someone finally figured out how to remove the dead node's DNS record.

$ host registry.npmjs.org
registry.npmjs.org has address 67.228.31.146

dmourati commented Nov 5, 2013

Someone finally figured out how to remove the dead node's DNS record.

$ host registry.npmjs.org
registry.npmjs.org has address 67.228.31.146

@mteece

This comment has been minimized.

Show comment Hide comment
@mteece

mteece Nov 5, 2013

Think that did it. 200 status codes all around.

mteece commented Nov 5, 2013

Think that did it. 200 status codes all around.

@dmourati

This comment has been minimized.

Show comment Hide comment
@dmourati

dmourati Nov 5, 2013

https://twitter.com/npmjs/status/397554551131090944 @npmjs 12m
econnrefused's should be over now, might have to wait as much as 300s for dns to propagate.

dmourati commented Nov 5, 2013

https://twitter.com/npmjs/status/397554551131090944 @npmjs 12m
econnrefused's should be over now, might have to wait as much as 300s for dns to propagate.

@darryl-snow

This comment has been minimized.

Show comment Hide comment
@darryl-snow

darryl-snow Nov 5, 2013

I'm still getting lots of npm ERR! fetch faileds and ERR! registry error parsing jsons :(

Tried flushing dns cache and clearing npm cache.

I'm still getting lots of npm ERR! fetch faileds and ERR! registry error parsing jsons :(

Tried flushing dns cache and clearing npm cache.

@othiym23

This comment has been minimized.

Show comment Hide comment
@othiym23

othiym23 Sep 16, 2014

Contributor

While we still have occasional issues with our CDN, in general we have had 99+% registry uptime over the last few months, and registry robustness is orders of magnitude better than it was. Closing!

Contributor

othiym23 commented Sep 16, 2014

While we still have occasional issues with our CDN, in general we have had 99+% registry uptime over the last few months, and registry robustness is orders of magnitude better than it was. Closing!

@othiym23 othiym23 closed this Sep 16, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment