-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Can't install pm2 at centos6 #232
Comments
I can't install pm2 on Centos6 either:
npm http 304 https://registry.npmjs.org/keypress The gyp install looked like this: ... npm http 304 https://registry.npmjs.org/hoek |
Same problem. Seems that problem with 'usage' module. You can track issue here: arunoda/node-usage/issues/19 |
Try to downgrade you system python to python2.6. It worked for me on ubuntu. |
For the |
There is a simple workaround to get pm2 working on CentOS 6.4 please see my final comment posted today at arunoda/node-usage#19 |
Did that, the problem remains. |
@workingmatt That worked for me. |
@Unitech is it possible to install pm2 globaly from this git repo? I mean, after cloning it into ~/npm/lib/node_modules and doing npm install and making a symlink to ~/npm/bin, what else should I do to make it work? This is a very annoying error from the gyp module. I have even tried re-installing the python gyp module, and still doesn't work. |
No idea if it works, but npm itself seems to be installable just fine this way (source). |
@MariusStuparu the -g flag @rlidwka suggests should work. Did you read my post I linked to 11 days ago above? It shows how I got pm2 to install globally and get over the node-gyp fault |
@rlidwka It doesn't, it stops at the same node-gyp error. |
How about this? 1.install rpm(my centos needs this) 2.rebuild node-gyp |
Something did the trick, because now it installed with --unsafe-perm, but only after I erased all traces of Node and Npm, and installed it again from source. Maybe the Yum packages are corrupt somehow. |
[email protected] installs fine, [email protected] fails... any update on this? |
this seem to be fixing it. |
I managed to fix this for my install. Few notes:
Relevant error: ...
make: Entering directory `/usr/lib/node_modules/pm2/node_modules/usage/build'
CXX(target) Release/obj.target/sysinfo/src/binding.o
SOLINK_MODULE(target) Release/obj.target/sysinfo.node
SOLINK_MODULE(target) Release/obj.target/sysinfo.node: Finished
COPY Release/sysinfo.node
make: Leaving directory `/usr/lib/node_modules/pm2/node_modules/usage/build'
/usr/bin/pm2 -> /usr/lib/node_modules/pm2/bin/pm2
npm WARN unmet dependency /usr/lib/node_modules/block-stream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
npm WARN unmet dependency which is version undefined
npm WARN unmet dependency /usr/lib/node_modules/fstream requires inherits@'~2.0.0' but will load
npm WARN unmet dependency undefined,
... What i discovered is that EPEL repo uses Here's what I had to do to fix this:
Running I imagine this breaks yum update in the future. |
As of 1bedf10 there is no C bindings anymore, this should work but I'd be glad to have a confirmation! Thanks. |
I have no idea about this , so how to fix this?
ty.
The text was updated successfully, but these errors were encountered: