what can cause node.js to print Killed and exit?

node.js

node.js Problem Overview

I have a Node.js app that loads some data from Mysql into Redis when the app starts. It has been working fine up until we modified the data in Mysql.

Now it is just exiting with a Killed message.

I am trying to pinpoint the problem but is is hard to debug using the node-inspector as the problem doesn't appear when running in --debug.

I don't think my problem is in the data itself because it works on my local machine but doesn't work on my production box.

My question is, what causes the Killed message? Is it Node.js or is it in the Mysql driver or elsewhere?

node.js Solutions

Solution 1 - node.js

Check your system logs for messages about Node being killed. Your Node application might be using excessive memory and getting killed by the Out-Of-Memory killer.

Solution 2 - node.js

Not sure if Redis is what causes the Killed message but that was the cause of my problem.

I was sending to much data to multi because I originally thought that was the way to use pipelining (which is automatic).

Categories
Recommended node.js Solutions

Previous Solution:

NPM private git module on Heroku

node.jsHerokuNpm

Next Solution:

Should HTML meta charset be lowercase or uppercase?

Html

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionTimView Question on Stackoverflow
Solution 1 - node.jslanzzView Answer on Stackoverflow
Solution 2 - node.jsTimView Answer on Stackoverflow