cb() never called #3269

Closed
depl0y opened this Issue Mar 20, 2013 · 14 comments

Comments

Projects
None yet

depl0y commented Mar 20, 2013

I am currently having issues with installing a few different packages. I am running node on Arch Linux for my Raspberry Pi.

sqlite3 has been updated to support node 0.10.0, but still npm install gives an error when installing this (and other packages).

node --version : v0.10.0
npm --version : 1.2.14

[root@alarmpi xnodes]# npm install sqlite3
npm http GET https://registry.npmjs.org/sqlite3
npm http 200 https://registry.npmjs.org/sqlite3
npm http GET https://registry.npmjs.org/sqlite3/-/sqlite3-2.1.7.tgz
npm http 200 https://registry.npmjs.org/sqlite3/-/sqlite3-2.1.7.tgz
npm ERR! cb() never called!
npm ERR! not ok code 0

I tried cleaning my npm cache.

This is on a clean installed version of Arch Linux.

Getting the same problem when installing JSHint on Travis CI -- Node 0.6/0.8 are fine, but it fails with 0.9.12. On my machine the installation hangs in the last step for a few minutes, but eventually it succeeds. (Tried 0.9.12 and 0.10.0).

xmike commented Mar 20, 2013

Having this problem also when installing socket.io. After installing the socket.io dependencies step by step I found the problem is actually occuring when installing: zeparser@0.0.5

Here ist the debug output. Platform is ARM/Linux. Note that the problem is happening also right after the GET *.tgz as reported by depl0y.

npm info using npm@1.2.14
npm info using node@v0.10.0
npm verb read json /home/sr/package.json
npm verb read json /home/sr/node_modules/active-x-obfuscator/package.json
npm verb read json /home/sr/node_modules/base64id/package.json
npm verb read json /home/sr/node_modules/express/package.json
npm verb read json /home/sr/node_modules/node-gyp/package.json
npm verb read json /home/sr/node_modules/policyfile/package.json
npm verb read json /home/sr/node_modules/redis/package.json
npm verb read json /home/sr/node_modules/socket.io/package.json
npm verb read json /home/sr/node_modules/uglify-js/package.json
npm verb read json /home/sr/node_modules/ws/package.json
npm verb read json /home/sr/node_modules/xmlhttprequest/package.json
npm verb read json /home/sr/package.json
npm verb cache add [ 'zeparser@0.0.5', null ]
npm verb cache add name=undefined spec="zeparser@0.0.5" args=["zeparser@0.0.5",null]
npm verb parsed url { protocol: null,
npm verb parsed url slashes: null,
npm verb parsed url auth: null,
npm verb parsed url host: null,
npm verb parsed url port: null,
npm verb parsed url hostname: null,
npm verb parsed url hash: null,
npm verb parsed url search: null,
npm verb parsed url query: null,
npm verb parsed url pathname: 'zeparser@0.0.5',
npm verb parsed url path: 'zeparser@0.0.5',
npm verb parsed url href: 'zeparser@0.0.5' }
npm verb cache add name="zeparser" spec="0.0.5" args=["zeparser","0.0.5"]
npm verb parsed url { protocol: null,
npm verb parsed url slashes: null,
npm verb parsed url auth: null,
npm verb parsed url host: null,
npm verb parsed url port: null,
npm verb parsed url hostname: null,
npm verb parsed url hash: null,
npm verb parsed url search: null,
npm verb parsed url query: null,
npm verb parsed url pathname: '0.0.5',
npm verb parsed url path: '0.0.5',
npm verb parsed url href: '0.0.5' }
npm verb addNamed [ 'zeparser', '0.0.5' ]
npm verb addNamed [ '0.0.5', '0.0.5' ]
npm sill lockFile eb150454-zeparser-0-0-5 zeparser@0.0.5
npm verb lock zeparser@0.0.5 /home/sr/.npm/eb150454-zeparser-0-0-5.lock
npm verb url raw zeparser/0.0.5
npm verb url resolving [ 'https://registry.npmjs.org/', './zeparser/0.0.5' ]
npm verb url resolved https://registry.npmjs.org/zeparser/0.0.5
npm info trying registry request attempt 1 at 16:57:31
npm verb etag "47F8SOSIXTQE9MZS4WWJFMZL4"
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm sill registry.get cb [ 304,
npm sill registry.get { server: 'CouchDB/1.2.1 (Erlang OTP/R15B03)',
npm sill registry.get etag: '"47F8SOSIXTQE9MZS4WWJFMZL4"',
npm sill registry.get date: 'Wed, 20 Mar 2013 16:57:32 GMT',
npm sill registry.get 'content-length': '0' } ]
npm verb etag zeparser/0.0.5 from cache
npm sill lockFile 4061607b--org-zeparser-zeparser-0-0-5-tgz https://registry.npmjs.org/zeparser/-/zeparser-0.0.5.tgz
npm verb lock https://registry.npmjs.org/zeparser/-/zeparser-0.0.5.tgz /home/sr/.npm/4061607b--org-zeparser-zeparser-0-0-5-tgz.lock
npm verb addRemoteTarball [ 'https://registry.npmjs.org/zeparser/-/zeparser-0.0.5.tgz',
npm verb addRemoteTarball '03726561bc268f2e5444f54c665b7fd4a8c029e2' ]
npm info retry fetch attempt 1 at 16:57:32
npm verb fetch to= /home/sr/tmp/npm-3080/1363798652815-0.008550376631319523/tmp.tgz
npm http GET https://registry.npmjs.org/zeparser/-/zeparser-0.0.5.tgz
npm http 200 https://registry.npmjs.org/zeparser/-/zeparser-0.0.5.tgz
npm ERR! cb() never called!
npm ERR! not ok code 0

Contributor

luk- commented Mar 20, 2013

duplicate of #2907

@luk- luk- closed this Mar 20, 2013

@jgautier jgautier referenced this issue in ceejbot/recurring Apr 8, 2013

Merged

adding support for fetching all subscriptions #3

huyz commented Apr 29, 2013

Did this issue return?

$ npm install -g jshint
npm http GET https://registry.npmjs.org/jshint
npm http 200 https://registry.npmjs.org/jshint
npm http GET https://registry.npmjs.org/jshint/-/jshint-1.1.0.tgz
npm http 200 https://registry.npmjs.org/jshint/-/jshint-1.1.0.tgz
npm ERR! cb() never called!
npm ERR! not ok code 0

I tried with v0.10.4 and v.0.10.5

arush commented Apr 29, 2013

yes we are experiencing this issue too on v0.8.19

We're also seeing this now with node 0.8.22, trying to npm install from a github repo (a fork of an NPM module) that isn't itself in NPM. (Using the tarball syntax: npm install https://github.com/USER/MODULE/archive/master.tar.gz) When I switch the github username in the fork URL to the original creator's, it works.

Contributor

luk- commented Apr 30, 2013

@newleafdigital that could be related to npm's caching. can you try npm cache clean then your npm install again?

barnabyc commented Jun 4, 2013

@st-luke - we're seeing this on perhaps 30% of our npm install runs. Tried adding npm cache clean immediately prior but still see the problem. (Should npm install still then contain 'npm verb from cache ...' messages?) Running v0.8.17 - after reading a few of these bug threads about cb() never called we're not seeing any definitive solutions.

@isaacs - does upgrading to the latest v0.10.x actually resolve this issue, or at least provide more detail? Unclear what to try...

Contributor

luk- commented Jun 4, 2013

@barnabyc do you have the same issue on v0.10.9? If you haven't upgraded and tried, then definitely do so. We can reopen this if the problem keeps happening.

I have this very same problem sporadically and I can't find any better solution than this one:

https://github.com/jfromaniello/npm-install-retry

@st-luke we were able to work around it. Tracked it down to an issue potentially when installing https://npmjs.org/package/lodash and were able to to factor that out of our shrinkwrap dependencies - zero failures since doing so

Hi,
I had this problem to install express with npm but when I use -g switch, the problem has been solved.

I think it better check your permission to installing node packages because -g just say install the package globally.

Regards,

I ran out of disk space while attempting an npm install and after clearing up some space was met with this error. For me, npm cache clean worked likely because it got rid of a partially downloaded/installed dependency that was cached.

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