Question

Why my npm run build command gets "killed"?

Posted on March 17, 2023
Load Balancing Node.js
Asked by aashaytrivedi1

I have been running this website for last 2 years and yesterday when I ran npm run build, it was killed. So, I logged out and when I logged in, digital ocean says cannot show system information because system load is more than 1.

My question is,

Why it is showing system load is more then 1 when I have not installed any new packages or page infact I have deleted around 10 pages and reduced the size of my project. My project requires around 697 MB memory and I have 1 GB server.
I tired to update node.js and npm but the issue remains the same

So, what’s the reason behind this issue?

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.

KFSys

Site Moderator

• March 17, 2023

Accepted Answer

Hey @aashaytrivedi1,

Well, you might be receiving more traffic thus generating more load to your application? Additionally, some resources might require more Memory if they have been updated.

This seems like it’s just resources missing. What you can do before upgrading though is to add SWAP and see how would that go:

Add SWAP

https://www.digitalocean.com/community/tutorial_collections/how-to-add-swap-space

Swap is a portion of hard drive storage that has been set aside for the operating system to temporarily store data that it can no longer hold in RAM. This lets you increase the amount of information that your server can keep in its working memory, with some caveats. The swap space on the hard drive will be used mainly when there is no longer sufficient space in RAM to hold in-use application data.