-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unable to install on CentOS or Redhat via NPM #671
Comments
Is this really a connect issue? I'm not sure. Do you need |
hmm yeah sounds more like some npm issues. try updating npm first and do an |
yes, I have tried it without the -g flag and with the g flag. I have tried on multiple CentOS 5.8 and Redhat 5.8 Servers. The only version of Connect I can currently install is 0.5.0. I am running npm version 1.0.106. I can install other modules via npm. This is the only module that I cannot seem to install. I get a error when trying to run npm cache clear. -bash-3.2# npm cache clear |
@blaztoff which version of node? |
I am using v0.4.9 |
Oh, it's outdated.. for me :-) |
I am unable to install node-v0.8.11. It always errors out. I installed by node via curl https://npmjs.org/install.sh | sh |
What system do you use? |
CentOS 5.8 and Redhat 5.8 |
Yeah, you mentioned it above.. Do you wish to download or |
I am not limited at all. I have been unable to install a higher node and installing connect always fails except for 0.5.0. I am open to any suggestions on how to install either a higher node or any version of connect. |
Thank you so much for helping on this. I will have to pick this up later though. |
It's platform issue, correct? |
Yes, I tried it on Ubuntu no problem. I have not tried it on Redhat 6.0 yet. Our environment is all Redhat so am trying to get it to work on Redhat. |
Okay, node has minimum external deprendecies, i'm unhappy that this essential package is not working on enterprise system. |
Unfortunately I cannot work on this now - i have other meeting to go to. I would be happy to help later though. Thanks for your help. |
@blaztoff Ask later if you wish, but you should close this because I thing this is not connect related; may be node+npm version related. |
yup agreed, node core guys are solid and I know they all want node to run on pretty much everything so I'm sure they'll help you out, closing for now |
I have been unable to get Connect to install via npm. I error out.
-bash-3.2# npm install -g connect
npm ERR! Failed unpacking /tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz
npm ERR! couldn't unpack /tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz to /tmp/npm-1350079512855/1350079512855-0.08907291875220835/contents
npm ERR! error installing connect@1.9.2 Error:
tar "-zmvxpf" "/tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz" "-o"
npm ERR! error installing connect@1.9.2 failed with 2
npm ERR! error installing connect@1.9.2 at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR! error installing connect@1.9.2 at ChildProcess.emit (events.js:67:17)
npm ERR! error installing connect@1.9.2 at Socket. (child_process.js:172:12)
npm ERR! error installing connect@1.9.2 at Socket.emit (events.js:64:17)
npm ERR! error installing connect@1.9.2 at Array.0 (net.js:831:12)
npm ERR! error installing connect@1.9.2 at EventEmitter._tickCallback (node.js:126:26)
npm ERR! Error:
tar "-zmvxpf" "/tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz" "-o"
npm ERR! failed with 2
npm ERR! at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR! at ChildProcess.emit (events.js:67:17)
npm ERR! at Socket. (child_process.js:172:12)
npm ERR! at Socket.emit (events.js:64:17)
npm ERR! at Array.0 (net.js:831:12)
npm ERR! at EventEmitter._tickCallback (node.js:126:26)
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-274.12.1.el5
npm ERR! command "node" "/usr/local/bin/npm" "install" "-g" "connect"
npm ERR! cwd /tmp/connect
npm ERR! node -v v0.4.9
npm ERR! npm -v 1.0.106
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /tmp/connect/npm-debug.log
npm not ok
Looking at the NPM log I see it is erroring out here.
verbose unpackTarget /tmp/npm-1350079512855/1350079512855-0.08907291875220835/contents/package
silly gunzTarPerm modes [ '755', '644' ]
silly spawning [ 'tar',
silly spawning [ '-zmvxpf',
silly spawning '/tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz',
silly spawning '-o' ],
silly spawning '/tmp/npm-1350079512855/1350079512855-0.08907291875220835/contents/___package.npm' ]
silly tar err tar: Ignoring unknown extended header keyword
NODETAR.depth' silly tar err tar: Ignoring unknown extended header keyword
NODETAR.follow'...
ERR! Failed unpacking /tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz
ERR! couldn't unpack /tmp/npm-1350079512855/1350079512855-0.08907291875220835/tmp.tgz to /tmp/npm-1350079512855/1350079512855-0.08907291875220835/contents
verbose about to build /usr/local/lib/node_modules/connect
Is there another way to install connect?
The text was updated successfully, but these errors were encountered: