Medium / phantomjs

NPM wrapper for installing phantomjs
Other
1.42k stars 435 forks source link

Failed at the phantomjs@1.9.20 install script 'node install.js' #676

Closed cash1981 closed 7 years ago

cash1981 commented 7 years ago

I have the exact same problem as issue #644

However, npm set strict-ssl false did not work for me I still get the same problem when I run npm install

Here is the output from npm install

npm ERR! Linux 4.4.0-64-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" npm ERR! node v4.2.6 npm ERR! npm v3.5.2 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn

npm ERR! phantomjs@1.9.20 install: node install.js npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the phantomjs@1.9.20 install script 'node install.js'.

Here is the npm-debug.log file

9494 verbose stack Error: phantomjs@1.9.20 install: node install.js 9494 verbose stack spawn ENOENT 9494 verbose stack at ChildProcess. (/usr/share/npm/lib/utils/spawn.js:17:16) 9494 verbose stack at emitTwo (events.js:87:13) 9494 verbose stack at ChildProcess.emit (events.js:172:7) 9494 verbose stack at maybeClose (internal/child_process.js:821:16) 9494 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 9495 verbose pkgid phantomjs@1.9.20 9496 verbose cwd /home/shervin/workspace/civilization-boardgame-web 9497 error Linux 4.4.0-64-generic 9498 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install" 9499 error node v4.2.6 9500 error npm v3.5.2 9501 error file sh 9502 error code ELIFECYCLE 9503 error errno ENOENT 9504 error syscall spawn 9505 error phantomjs@1.9.20 install: node install.js 9505 error spawn ENOENT 9506 error Failed at the phantomjs@1.9.20 install script node install.js

jameswomack commented 7 years ago

I'm experiencing the same

gvinson commented 7 years ago

Same

jrdespai commented 7 years ago

I'm having this issue too, it looks like this actually might be related to an AWS outage (look at the bottom of this issue): #674

diegoconcha commented 7 years ago

I was able to get this working via: https://github.com/Medium/phantomjs/issues/674#issuecomment-283150753

sudhirpal commented 7 years ago

May I know when this issue gets resolved? I tried just now but still seeing the same problem.

cash1981 commented 7 years ago

Can anyone verify that this bug is still there? Perhaps it was the amazon aws outage

sudhirpal commented 7 years ago

After couple of hours it worked for me. And I'm not seeing this issue anymore. Thanks!

cash1981 commented 7 years ago

It still doesn't work for me

0308 verbose stack Error: phantomjs@1.9.20 install: node install.js 10308 verbose stack spawn ENOENT 10308 verbose stack at ChildProcess. (/usr/share/npm/lib/utils/spawn.js:17:16) 10308 verbose stack at emitTwo (events.js:87:13) 10308 verbose stack at ChildProcess.emit (events.js:172:7) 10308 verbose stack at maybeClose (internal/child_process.js:821:16) 10308 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) 10309 verbose pkgid phantomjs@1.9.20 10310 verbose cwd /home/shervin/workspace/civilization-boardgame-web 10311 error Linux 4.4.0-64-generic 10312 error argv "/usr/bin/nodejs" "/usr/bin/npm" "install" 10313 error node v4.2.6 10314 error npm v3.5.2 10315 error file sh 10316 error code ELIFECYCLE 10317 error errno ENOENT 10318 error syscall spawn 10319 error phantomjs@1.9.20 install: node install.js 10319 error spawn ENOENT 10320 error Failed at the phantomjs@1.9.20 install script 'node install.js'. 10320 error Make sure you have the latest version of node.js and npm installed. 10320 error If you do, this is most likely a problem with the phantomjs package, 10320 error not with npm itself. 10320 error Tell the author that this fails on your system: 10320 error node install.js 10320 error You can get information on how to open an issue for this project with: 10320 error npm bugs phantomjs 10320 error Or if that isn't available, you can get their info via: 10320 error npm owner ls phantomjs 10320 error There is likely additional logging output above.

cash1981 commented 7 years ago

I upgrade npm as it suggested, and now it worked

bashisha commented 7 years ago

how did you upgraded npm?