Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

ERR! cb() never called! #3936

sjonnet19 opened this Issue Sep 26, 2013 · 13 comments


None yet
10 participants

npm http GET https://registry.npmjs.org/jade
npm http GET https://registry.npmjs.org/connect-redis
npm http GET https://registry.npmjs.org/express
npm http GET https://registry.npmjs.org/knox
npm http GET https://registry.npmjs.org/migrate
npm http GET https://registry.npmjs.org/mocha
npm http GET https://registry.npmjs.org/mongoose
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/spdy
npm http GET https://registry.npmjs.org/stylus
npm http GET https://registry.npmjs.org/redis
npm http GET https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/markdown
npm http GET https://registry.npmjs.org/nib
npm http GET https://registry.npmjs.org/aws-sdk
npm http 304 https://registry.npmjs.org/knox
npm http 304 https://registry.npmjs.org/connect-redis
npm http 304 https://registry.npmjs.org/express
npm http 304 https://registry.npmjs.org/migrate
npm http 304 https://registry.npmjs.org/mocha
npm http 200 https://registry.npmjs.org/socket.io
npm http 200 https://registry.npmjs.org/stylus
npm http GET https://registry.npmjs.org/socket.io/-/socket.io-0.9.16.tgz
npm http GET https://registry.npmjs.org/stylus/-/stylus-0.38.0.tgz
npm http 304 https://registry.npmjs.org/redis
npm http 200 https://registry.npmjs.org/spdy
npm http 304 https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/spdy/-/spdy-1.12.1.tgz
npm http 304 https://registry.npmjs.org/markdown
npm http 304 https://registry.npmjs.org/nib
npm http 304 https://registry.npmjs.org/aws-sdk
npm http 200 https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.0.tgz
npm http 200 https://registry.npmjs.org/socket.io/-/socket.io-0.9.16.tgz
npm http 200 https://registry.npmjs.org/stylus/-/stylus-0.38.0.tgz
npm http 200 https://registry.npmjs.org/spdy/-/spdy-1.12.1.tgz
npm http 200 https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.0.tgz
npm ERR! cb() never called!
npm ERR! not ok code 0

This is the error I had reported earlier on node and commented on a similar ticket it is still a issue and only has appeared since node went to v0.10.19.

Prior versions with NPM 1.3.11 this did not occur.

I have the exact same issue.

So it looks like this is a long-known about issue with many versions of npm. Solutions are:

a) Downgrade a release or two, see if it helps
b) Try cleaning your NPM cache
c) Retry a billion times. It will work eventually. Oh there's a package for that

You know something is wrong with a framework when it needs a package to reinstall packages since they fail intermittently...


luk- commented Sep 26, 2013

@bitgangsta if you're interested in helping npm maintainers track down the issue, feel free to post an error log and the platform you're having the issue on. If not, that's cool too, constructive feedback is also valuable.

hayeah commented Sep 26, 2013

@luk I am having this problem as well. How do I enable the debug log? I can't find the npm-debug.log.

hayeah commented Sep 26, 2013

@luk I installed npm (1.3.11) from ubuntu package. Do I need to reinstall it with debugging enabled or something?

I don't get a error log

Same issue. I get the error on osx 10.8. npm v1.3.11, node v0.10.19. start happening yesterday.

'npm install --production' causes this error for me (and also on heroku.)

Same problem here. I am able to reproduce this issue in a consistent manner when attempting to deploy to heroku, as well as on my Windows XP environment. It's a bit more intermittent, but but also flares up on OSX.

This started happening with node v0.10.19. Downgrading to node v0.10.17 seems to make the issue go away. It appears that using any version of npm, even going back to 1.2.30, still causes the issue when coupled with node 0.10.19, and the --production flag. In every case, going back to node 0.10.17 resolves the problem.

Note: This ONLY appears when adding the --production flag. When not using the flag, all modules download and install/build normally.

qubyte commented Sep 27, 2013

We're seeing this issue too on 1.3.11.

aaronyo commented Sep 29, 2013

Same issue when running npm install -g forever. Tried npm cache clean, and tried running half a dozen times but never worked. The number of successful http commands, before failure, varies a lot.

root@qa:~# node -v && npm -v && uname -a
Linux 3.2.0-31-virtual #50-Ubuntu SMP Fri Sep 7 16:36:36 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 12.04.1 LTS

It works when I step back to node v0.10.18.

This is a duplicate of #2907

Same here, npm install -g forever fails.

Ubuntu 12.04.1 LTS
Binary node.js installation tgz from node.js site

It works when using node.js 0.10.18


luk- commented Oct 1, 2013

Closing since duplicate. Please read the updates in #2907

@luk- luk- closed this Oct 1, 2013

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