Error installing socketio using npm #3965

Closed
jeyaganesh opened this Issue Oct 3, 2013 · 8 comments

Comments

Projects
None yet
2 participants
@jeyaganesh

npm ERR! Error: shasum check failed for /root/tmp/npm-10944-NcWGw2aW/1380826993465-0.2645562016405165/tmp.tgz
npm ERR! Expected: 03726561bc268f2e5444f54c665b7fd4a8c029e2
npm ERR! Actual: 69b631001618206591d3e27080bf4e5bbf1b1e07
npm ERR! at /usr/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR! at ReadStream. (/usr/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR! at ReadStream.EventEmitter.emit (events.js:125:20)
npm ERR! at _stream_readable.js:896:16
npm ERR! at process._tickCallback (node.js:316:11)
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 Linux 3.4.62-53.42.amzn1.x86_64
npm ERR! command "node" "/usr/bin/npm" "install" "socket.io"
npm ERR! cwd /home/ec2-user
npm ERR! node -v v0.11.8-pre
npm ERR! npm -v 1.3.11
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/ec2-user/npm-debug.log
npm ERR! not ok code 0

@jeyaganesh

This comment has been minimized.

Show comment Hide comment
@jeyaganesh

jeyaganesh Oct 3, 2013

clean cache doesn't work

clean cache doesn't work

@robertkowalski

This comment has been minimized.

Show comment Hide comment
@robertkowalski

robertkowalski Oct 3, 2013

Member

you are using an unstable node release, have you tried the latest stable?

2013/10/3 jeyaganesh notifications@github.com

clean cache doesn't work


Reply to this email directly or view it on GitHubhttps://github.com/isaacs/npm/issues/3965#issuecomment-25648687
.

Member

robertkowalski commented Oct 3, 2013

you are using an unstable node release, have you tried the latest stable?

2013/10/3 jeyaganesh notifications@github.com

clean cache doesn't work


Reply to this email directly or view it on GitHubhttps://github.com/isaacs/npm/issues/3965#issuecomment-25648687
.

@robertkowalski

This comment has been minimized.

Show comment Hide comment
@robertkowalski

robertkowalski Oct 3, 2013

Member

with cleaning the cache before retrying it.

Member

robertkowalski commented Oct 3, 2013

with cleaning the cache before retrying it.

@jeyaganesh

This comment has been minimized.

Show comment Hide comment
@jeyaganesh

jeyaganesh Oct 4, 2013

v0.11.8-pre is the version I am using.

v0.11.8-pre is the version I am using.

@robertkowalski

This comment has been minimized.

Show comment Hide comment
@robertkowalski

robertkowalski Oct 4, 2013

Member

does using node 0.10.20 (stable), npm cache clean after installing 0.10.20 and retrying it solve the problem for you?

Member

robertkowalski commented Oct 4, 2013

does using node 0.10.20 (stable), npm cache clean after installing 0.10.20 and retrying it solve the problem for you?

@jeyaganesh

This comment has been minimized.

Show comment Hide comment
@jeyaganesh

jeyaganesh Oct 4, 2013

how to downgrade? is there any command or i should delete and start over?
Thanks

how to downgrade? is there any command or i should delete and start over?
Thanks

@robertkowalski

This comment has been minimized.

Show comment Hide comment
@robertkowalski

robertkowalski Oct 4, 2013

Member

That depends on how you installed node. If you installed it from source then

sudo make uninstall

will do the job.

Member

robertkowalski commented Oct 4, 2013

That depends on how you installed node. If you installed it from source then

sudo make uninstall

will do the job.

@jeyaganesh

This comment has been minimized.

Show comment Hide comment
@jeyaganesh

jeyaganesh Oct 4, 2013

Thanks very much.That worked

Thanks very much.That worked

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