I have a droplet with Ubuntu 12.04 where i have installed node and npm. But no matter what i try, npm works a little and the gets “killed”. It happens if i try “npm update” or “npm install”.
Anyone know what causes this and if there is a solution?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×I found a solution that seems to work. I upgraded my swap-file to 1gb from 500mb ca.
Then i could install modules again.
It worked! I had exactly the same problem, and it seems that I had no swap file at all. After creating a 1GB swap file, npm kept installing all the packages till the end. Thanks a lot for sharing this!
To solve this issue on 14.04 and 16.04:
sudo fallocate -l 1G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
sudo swapon --show
sudo cp /etc/fstab /etc/fstab.bak
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
sudo sysctl vm.swappiness=10
echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf
sudo sysctl vm.vfs_cache_pressure=50
echo 'vm.vfs_cache_pressure=50' | sudo tee -a /etc/sysctl.conf
This will create a swap file of 1GB
Thanks for taking the time to post this. It worked for me!
Anyone Still struggling with this problem should try this first. I’d wager that this saved me a few hours.
Try running npm in verbose-mode, and post the results if you still can’t figure out what happened.
npm --verbose install <package>
npm http GET https://registry.npmjs.org/lodash._isnative
npm verb request where is /lodash.isobject
npm verb request registry https://registry.npmjs.org/
npm verb url raw /lodash.isobject
npm verb url resolving [ 'https://registry.npmjs.org/', './lodash.isobject' ]
npm verb url resolved https://registry.npmjs.org/lodash.isobject
npm verb request where is https://registry.npmjs.org/lodash.isobject
npm info trying registry request attempt 1 at 08:22:30
npm verb etag "CPWRI1IP3U8NTU89SB3AHKA9H"
npm http GET https://registry.npmjs.org/lodash.isobject
npm verb request where is /lodash._shimkeys
npm verb request registry https://registry.npmjs.org/
npm verb url raw /lodash._shimkeys
npm verb url resolving [ 'https://registry.npmjs.org/', './lodash._shimkeys' ]
npm verb url resolved https://registry.npmjs.org/lodash._shimkeys
npm verb request where is https://registry.npmjs.org/lodash._shimkeys
npm info trying registry request attempt 1 at 08:22:30
npm verb etag "DZ6P032FLD78S0R91BMU2WH7"
npm http GET https://registry.npmjs.org/lodash._shimkeys
npm verb registry.get https://registry.npmjs.org/lodash.keys not expired, no request
npm verb registry.get https://registry.npmjs.org/lodash.keys not expired, no request
npm verb request where is /lodash._escapehtmlchar
npm verb request registry https://registry.npmjs.org/
npm verb url raw /lodash._escapehtmlchar
npm verb url resolving [ 'https://registry.npmjs.org/', './lodash._escapehtmlchar' ]
npm verb url resolved https://registry.npmjs.org/lodash._escapehtmlchar
npm verb request where is https://registry.npmjs.org/lodash._escapehtmlchar
npm info trying registry request attempt 1 at 08:22:30
npm verb etag "3ILFQWIDQTJSRWFEDZ8ZQ3I"
npm http GET https://registry.npmjs.org/lodash._escapehtmlchar
npm verb request where is /lodash._reunescapedhtml
npm verb request registry https://registry.npmjs.org/
Killed
This is the last lines, it gets a little bit farther every time, so i’m guessing it runs out of memory or something.
I have a droplet with 512mb of ram.
Try install through the script:
https://gist.github.com/SuperPaintman/851b330c08b2363aea1c870f0cc1ea5a
npm-f3-install all
npm-f3-install production
npm-f3-install development
I know this thread is old but maybe a simple detail helps.
I have 512mb RAM with no root access and had the same issue. I was receiving “killed” message even running npm-f3-install script (all, production or development).
The sollution was simple, just run “npm-f3-install all -s” or “npm-f3-install all –silent”.
It’s a silent mode, without those outputs that consume memory.
Worked for me.
By the way, thanks for the script, SuperPaintmanDe.
I am having this issue too. MEAN.JS droplet. 512 MB.
Did you have any success with resolving this issue? I am running into the same problem.
Hey, yes i did, take a look at my answer below.
I had to increase my memory (swap).
Same here, doing a “flexible increase” in droplet size from 512 MB to 1 GB fixed this for me. Working with keystone.js / node / express.
Had the same issue, upgrading to 1GB of memory and reinstalling node modules a bunch of times worked.
Cheapest solution is to create a swap file, it only takes 5 minutes and you don’t need to pay anything extra.
https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04
If you however need speed, you should increase the droplet.
Thanks! This works.
Above article really works.