New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socket.io npm install failed #456

Closed
soggie opened this Issue Aug 10, 2011 · 9 comments

Comments

Projects
None yet
8 participants
@soggie
Copy link

soggie commented Aug 10, 2011

I tried installing socket.io in my webfaction server and it failed:

$ npm install socket.io

Error message:

npm ERR! Error: Failed tar "-mvxpf" "-" "-o" "-C" "/tmp/npm-1312969392201/1312969392202-0.274373595835641/contents/___package.npm"
npm ERR! exited with 2
npm ERR!     at ChildProcess.<anonymous> (/home/rtan/lib/node_modules/npm/lib/utils/exec.js:85:8)
npm ERR!     at ChildProcess.emit (events.js:67:17)
npm ERR!     at ChildProcess.onexit (child_process.js:192:12)
npm ERR! Report this *entire* log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>
npm ERR! 
npm ERR! System Linux 2.6.18-238.9.1.el5PAE
npm ERR! command "node" "/home/rtan/bin/npm" "install" "socket.io"
npm ERR! cwd /home/rtan/webapps/wwt_node
npm ERR! node -v v0.4.10
npm ERR! npm -v 1.0.23
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/rtan/webapps/wwt_node/npm-debug.log

Thing is, other modules (express, ejs, vows) seem to work fine.

I've opened an issue in npm, so I'm creating an issue here as well just in case it's something to do with package.json settings.

@denisu

This comment has been minimized.

Copy link

denisu commented Aug 10, 2011

Got this one on one of my servers too, but only on CentOS. Fedora worked fine.

Removing the tmp files and the clearing the npm cache didn't help.

@soggie

This comment has been minimized.

Copy link

soggie commented Aug 10, 2011

Damn. I'm stuck with manually copying all my npm modules into webfaction. I actually wrote a deployment script and now it doesn't work because of this. Hope this gets fixed soon!

@MRandhava

This comment has been minimized.

Copy link

MRandhava commented Aug 11, 2011

'npm install socket.io' is failing for me as well.

We are at a critical stage of development and we need socket.io and thus we need this command to work. The operation seems to hang.

I have run 'npm install socket.io -dd' and the ouput appears below where it hangs on the last line:

root@sling:~# npm install socket.io -dd
npm info it worked if it ends with ok
npm verb cli [ 'node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'install',
npm verb cli 'socket.io',
npm verb cli '-dd' ]
npm info using npm@1.0.24
npm info using node@v0.5.4-pre
npm verb config file /root/.npmrc
npm verb config file /usr/local/etc/npmrc
npm verb into /root [ 'socket.io' ]
npm verb cache add socket.io
npm verb cache add [ 'socket.io', null ]
npm verb parsed url { pathname: 'socket.io',
npm verb parsed url href: 'socket.io' }
npm verb caching socket.io/package.json
npm verb loadDefaults socket.io@0.7.8
npm verb pack /root/socket.io /tmp/npm-1313106186511/1313106186511-0.9317451866809279/tmp.tgz
npm verb caching /root/socket.io/examples/chat/package.json
npm verb loadDefaults chat.io@0.0.1
npm verb caching /root/socket.io/support/node-websocket-client/package.json
npm verb loadDefaults websocket-client@1.0.0
npm verb caching /root/socket.io/examples/irc-output/package.json
npm verb loadDefaults socket.io-irc@0.0.1
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511'
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511/1313106186511-0.9317451866809279'
npm verb mkdir done: /tmp/npm-1313106186511/1313106186511-0.9317451866809279 755
npm verb mkdir'ed /tmp/npm-1313106186511/1313106186511-0.9317451866809279
npm verb tar about to write tar and gzip it.
npm verb success tar -cvf -
npm verb success gzip "--stdout"
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents'
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/___package.npm'
npm verb mkdir done: /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/__package.npm 755
npm verb unpack
uid, gid [ 0, 0 ]
npm verb unpackTarget /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package
npm verb success gzip "--decompress" "--stdout" "/tmp/npm-1313106186511/1313106186511-0.9317451866809279/tmp.tgz"
npm verb success tar "-mvxpf" "-" "-o" "-C" "/tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/___package.npm"
npm verb gunzed /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/___package.npm/socket.io
npm verb rm'ed /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package
npm verb renamed [ '/tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/___package.npm/socket.io',
npm verb renamed '/tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package' ]
npm verb caching /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package/package.json
npm verb loadDefaults socket.io@0.7.8
npm verb tarball contents [ 'package' ]
npm verb from cache /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package/package.json
npm verb pack /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package /root/.npm/socket.io/0.7.8/package.tgz
npm verb caching /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package/examples/chat/package.json
npm verb loadDefaults chat.io@0.0.1
npm verb caching /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package/examples/irc-output/package.json
npm verb loadDefaults socket.io-irc@0.0.1
npm verb caching /tmp/npm-1313106186511/1313106186511-0.9317451866809279/contents/package/support/node-websocket-client/package.json
npm verb loadDefaults websocket-client@1.0.0
npm verb mkdir'ed /root/.npm/socket.io/0.7.8
npm verb tar about to write tar and gzip it.
npm verb success tar -cvf -
npm verb success gzip "--stdout"
npm verb mkdir (expected) error ENOENT, No such file or directory '/root/.npm/socket.io/0.7.8/___package.npm'
npm verb mkdir done: /root/.npm/socket.io/0.7.8/__package.npm 755
npm verb unpack
uid, gid [ 0, 0 ]
npm verb unpackTarget /root/.npm/socket.io/0.7.8/package
npm verb success gzip "--decompress" "--stdout" "/root/.npm/socket.io/0.7.8/package.tgz"
npm verb success tar "-mvxpf" "-" "-o" "-C" "/root/.npm/socket.io/0.7.8/___package.npm"
npm verb gunzed /root/.npm/socket.io/0.7.8/___package.npm/package
npm verb rm'ed /root/.npm/socket.io/0.7.8/package
npm verb renamed [ '/root/.npm/socket.io/0.7.8/___package.npm/package',
npm verb renamed '/root/.npm/socket.io/0.7.8/package' ]
npm verb caching /root/.npm/socket.io/0.7.8/package/package.json
npm verb loadDefaults socket.io@0.7.8
npm info shasum 2d8256e51c17ea7087f5900e11c7a857bd59e41b
npm info shasum /root/.npm/socket.io/0.7.8/package.tgz
npm verb from cache /root/.npm/socket.io/0.7.8/package/package.json
npm verb chmod /root/.npm/socket.io/0.7.8/package.tgz 644
npm info into /root socket.io@0.7.8
npm info installOne socket.io@0.7.8
npm info unbuild /root/node_modules/socket.io
npm verb caching /root/node_modules/socket.io/package.json
npm verb loadDefaults socket.io@0.7.8
npm info preuninstall socket.io@0.7.8
npm info uninstall socket.io@0.7.8
npm verb unbuild socket.io@0.7.8 [ false,
npm verb unbuild socket.io@0.7.8 '/usr/local/lib/node_modules',
npm verb unbuild socket.io@0.7.8 '/root/node_modules' ]
npm info postuninstall socket.io@0.7.8
npm verb from cache /root/.npm/socket.io/0.7.8/package/package.json
npm verb mkdir (expected) error ENOENT, No such file or directory '/root/node_modules/___socket.io.npm'
npm verb mkdir done: /root/node_modules/__socket.io.npm 755
npm verb unpack
uid, gid [ 0, 0 ]
npm verb unpackTarget /root/node_modules/socket.io
npm verb success gzip "--decompress" "--stdout" "/root/.npm/socket.io/0.7.8/package.tgz"
npm verb success tar "-mvxpf" "-" "-o" "-C" "/root/node_modules/___socket.io.npm"
npm verb gunzed /root/node_modules/___socket.io.npm/package
npm verb rm'ed /root/node_modules/socket.io
npm verb renamed [ '/root/node_modules/___socket.io.npm/package',
npm verb renamed '/root/node_modules/socket.io' ]
npm verb from cache /root/node_modules/socket.io/package.json
npm info preinstall socket.io@0.7.8
npm verb from cache /root/node_modules/socket.io/package.json
npm verb into /root/node_modules/socket.io [ 'socket.io-client@0.7.5',
npm verb into /root/node_modules/socket.io 'policyfile@0.0.4',
npm verb into /root/node_modules/socket.io 'redis@0.6.6' ]
npm verb cache add socket.io-client@0.7.5
npm verb cache add [ 'socket.io-client@0.7.5', null ]
npm verb parsed url { pathname: 'socket.io-client',
npm verb parsed url href: 'socket.io-client' }
npm info addNamed [ 'socket.io-client', '0.7.5' ]
npm verb addNamed [ '0.7.5', '0.7.5' ]
npm verb cache add policyfile@0.0.4
npm verb cache add [ 'policyfile@0.0.4', null ]
npm verb parsed url { pathname: 'policyfile',
npm verb parsed url href: 'policyfile' }
npm info addNamed [ 'policyfile', '0.0.4' ]
npm verb addNamed [ '0.0.4', '0.0.4' ]
npm verb cache add redis@0.6.6
npm verb cache add [ 'redis@0.6.6', null ]
npm verb parsed url { pathname: 'redis',
npm verb parsed url href: 'redis' }
npm info addNamed [ 'redis', '0.6.6' ]
npm verb addNamed [ '0.6.6', '0.6.6' ]
npm verb GET socket.io-client/0.7.5
npm verb raw, before any munging socket.io-client/0.7.5
npm verb url resolving [ 'https://registry.npmjs.org/',
npm verb url resolving './socket.io-client/0.7.5' ]
npm verb url resolved https://registry.npmjs.org/socket.io-client/0.7.5
npm verb url parsed { protocol: 'https:',
npm verb url parsed slashes: true,
npm verb url parsed host: 'registry.npmjs.org',
npm verb url parsed hostname: 'registry.npmjs.org',
npm verb url parsed href: 'https://registry.npmjs.org/socket.io-client/0.7.5',
npm verb url parsed pathname: '/socket.io-client/0.7.5' }
npm verb etag "D3TTLN97CA16RPB6HCMNWGJV3"
npm verb GET policyfile/0.0.4
npm verb raw, before any munging policyfile/0.0.4
npm verb url resolving [ 'https://registry.npmjs.org/',
npm verb url resolving './policyfile/0.0.4' ]
npm verb url resolved https://registry.npmjs.org/policyfile/0.0.4
npm verb url parsed { protocol: 'https:',
npm verb url parsed slashes: true,
npm verb url parsed host: 'registry.npmjs.org',
npm verb url parsed hostname: 'registry.npmjs.org',
npm verb url parsed href: 'https://registry.npmjs.org/policyfile/0.0.4',
npm verb url parsed pathname: '/policyfile/0.0.4' }
npm verb etag "6ZLVEGQEC2UQBN2FIDYCJPUQG"
npm verb GET redis/0.6.6
npm verb raw, before any munging redis/0.6.6
npm verb url resolving [ 'https://registry.npmjs.org/',
npm verb url resolving './redis/0.6.6' ]
npm verb url resolved https://registry.npmjs.org/redis/0.6.6
npm verb url parsed { protocol: 'https:',
npm verb url parsed slashes: true,
npm verb url parsed host: 'registry.npmjs.org',
npm verb url parsed hostname: 'registry.npmjs.org',
npm verb url parsed href: 'https://registry.npmjs.org/redis/0.6.6',
npm verb url parsed pathname: '/redis/0.6.6' }
npm verb etag "5U5I8MAEK1UKLUZTHPT35E3PB"
npm verb response https://registry.npmjs.org/socket.io-client/0.7.5
npm verb etag socket.io-client/0.7.5 from cache
npm verb response https://registry.npmjs.org/policyfile/0.0.4
npm verb etag policyfile/0.0.4 from cache
npm verb bin dist [ null,
npm verb bin dist { shasum: 'b3b2420088016ddced1ff20c3bc999272ba6b1bf',
npm verb bin dist tarball: 'http://registry.npmjs.org/socket.io-client/-/socket.io-client-0.7.5.tgz' } ]
npm verb bin dist [ null,
npm verb bin dist { shasum: 'd6b82ead98ae79ebe228e2daf5903311ec982e4d',
npm verb bin dist tarball: 'http://registry.npmjs.org/policyfile/-/policyfile-0.0.4.tgz' } ]
npm verb addRemoteTarball [ 'https://registry.npmjs.org/socket.io-client/-/socket.io-client-0.7.5.tgz',
npm verb addRemoteTarball 'b3b2420088016ddced1ff20c3bc999272ba6b1bf' ]
npm verb addRemoteTarball [ 'https://registry.npmjs.org/policyfile/-/policyfile-0.0.4.tgz',
npm verb addRemoteTarball 'd6b82ead98ae79ebe228e2daf5903311ec982e4d' ]
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511/1313106190089-0.5455700387246907'
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511/1313106190090-0.2837571285199374'
npm verb mkdir done: /tmp/npm-1313106186511/1313106190089-0.5455700387246907 755
npm verb mkdir done: /tmp/npm-1313106186511/1313106190090-0.2837571285199374 755
npm info fetch https://registry.npmjs.org/socket.io-client/-/socket.io-client-0.7.5.tgz
npm verb fetch to /tmp/npm-1313106186511/1313106190089-0.5455700387246907/tmp.tgz
npm info fetch https://registry.npmjs.org/policyfile/-/policyfile-0.0.4.tgz
npm verb fetch to /tmp/npm-1313106186511/1313106190090-0.2837571285199374/tmp.tgz
npm verb response https://registry.npmjs.org/redis/0.6.6
npm verb etag redis/0.6.6 from cache
npm verb bin dist [ null,
npm verb bin dist { shasum: 'cd77d6baa61d3be89032fb21263d172277ac1348',
npm verb bin dist tarball: 'http://registry.npmjs.org/redis/-/redis-0.6.6.tgz' } ]
npm verb addRemoteTarball [ 'https://registry.npmjs.org/redis/-/redis-0.6.6.tgz',
npm verb addRemoteTarball 'cd77d6baa61d3be89032fb21263d172277ac1348' ]
npm verb mkdir (expected) error ENOENT, No such file or directory '/tmp/npm-1313106186511/1313106190127-0.8407989738043398'
npm verb mkdir done: /tmp/npm-1313106186511/1313106190127-0.8407989738043398 755
npm info fetch https://registry.npmjs.org/redis/-/redis-0.6.6.tgz
npm verb fetch to /tmp/npm-1313106186511/1313106190127-0.8407989738043398/tmp.tgz

When I enter the url "https://registry.npmjs.org/redis/-/redis-0.6.6.tgz" into the browser I end up with certificate issues. Please help ASAP.

@ghost

This comment has been minimized.

Copy link

ghost commented Aug 15, 2011

i just ran into this exact error too on Centos 5.5.
i fixed it by erasing yum's older tar and installing the latest tar.
wget ftp://mirrors.kernel.org/gnu/tar/tar-1.26.tar.gz
obviously untar before remove tar to upgrade it!
rpm -e --no-deps tar
then configure make etc...

@selosindis

This comment has been minimized.

Copy link

selosindis commented Aug 16, 2011

@korch You, sir, are a genius! I was pulling my hair out trying to get this to work. Thanks for posting! It worked perfect on Centos 5.5.

~Selosindis

@KensakuKOMATSU

This comment has been minimized.

Copy link

KensakuKOMATSU commented Aug 16, 2011

Great work!! All my trouble has disappeared :)

@joevennix

This comment has been minimized.

Copy link

joevennix commented Aug 26, 2011

Perfect! On my Centos 5.5, I had to run:

rpm -e --nodeps tar

instead of:

rpm -e --no-deps tar

@rauchg

This comment has been minimized.

Copy link
Contributor

rauchg commented Sep 3, 2011

Thanks for the feedback on how to resolve it.

@rauchg rauchg closed this Sep 3, 2011

@samuelclay

This comment has been minimized.

Copy link

samuelclay commented Nov 6, 2011

Just want to mention for any Mac OS X users who check this issue and have the same problem, make sure you are running the latest version of npm. Upgrading fixed this for me.

curl http://npmjs.org/install.sh | sudo sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment