Menu
If your node scripts end with just a "killed" message, it is likely that your system is out of memory. Clear as day, an out of memory error letting me know that node was killed. Doh. At this point I have two options, upgrade the VPS or reduce the memory usage on this VPS.
Problems occurring in Node. js application deployments can have a range of symptoms, but can generally be categorized into the following: Uncaught exception or error event in JavaScript code. Excessive memory usage, which may result in an out-of-memory error.
exit() Function: This function tells Node. js to end the process which is running at the same time with an exit code. By calling this function Node. js will force the current process that's running to exit as soon as possible.
kill() Method. The process. kill( pid[,signal] ) is an inbuilt method of node. js which sends a signal to the process, pid (which is the process id) and signal is in the string format that is the signal to send.
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.
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).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With