Hello, thanks for such a great tool!
i am trying to install pm2 on a server that is behind corporate firewall and it hangs on this stage:
Execute command npm i -g pm2:
fetchMetadata: sill resolveWithNewModule [email protected] checking installable status
Can you point me to right direction how to resolve this?
no proxies are setup:
npm config get registry
https://registry.npmjs.org/
npm config get https-proxy
undefined
md5-33270a144a07f44b52b30de65b44d871
npm config get https-proxy
null
md5-6f54e088194ed3c86e812c0fcde827f2
PM2 version: `N/A`
Node version: `v6.10.3`
RedHat 7
Thank you.
I thought it was an npm issue but it appears that other packages are installing fine. I tried npm i -g npm and npm i -g ionic. So for some reason only npm i -g pm2 is hanging.
@Unitech any chance you can point to right direction? Thanks a lot
Try adding verbose, we can't help you with no logs
I think this issue is on our side where firewall is blocking something
What was the issue?
Same issue, how did you solve it ?
@matthew-dean @samanmohamadi I had to preform an off line installation of PM2 using npmbox https://github.com/arei/npmbox/blob/master/README.md
same problem i have the latest version..cant install it :(
I had the same issue and solved it:
npm cache clean -f
npm config get registry. For me it was https://registry.npmjs.org/
npm set registry http://registry.npmjs.org/
So by changing it from httpS to http I solved the problem.
None of the solutions posted above have worked for me, turning off firewall doesn't work either.
Other packages install successfully.
Here is my verbose output:
npm install pm2 -g
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm http fetch GET 304 http://registry.npmjs.org/pm2 159ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/async 89ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/mkdirp 45ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/blessed 210ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/chokidar 210ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/cli-table-redemption 211ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/commander 210ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/eventemitter2 209ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/chalk 213ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/cron 211ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/debug 215ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/fclone 214ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/moment 91ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/needle 78ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/nssocket 90ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/pidusage 92ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/pm2-axon 98ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/pm2-axon-rpc 106ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/pm2-deploy 111ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/pm2-multimeter 133ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/promptly 134ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/semver 120ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/pmx 155ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/shelljs 85ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/source-map-support 76ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/sprintf-js 73ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/v8-compile-cache 72ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/vizion 67ms (from cache)
npm http fetch GET 304 http://registry.npmjs.org/yamljs 56ms (from cache)
[..................] | fetchMetadata: http fetch GET 304 http://registry.npmjs.org/yamljs 56ms (from cache)
ANY help appreciated!
OK, so my issue was basically #2700. npm install --g --no-optional pm2 worked.
npm install --g --no-optional pm2 Worked thanks @khrykin
FYI, rm -rf node_modules/ works for me.
Most helpful comment
OK, so my issue was basically #2700.
npm install --g --no-optional pm2worked.