Killing a bash script does not kill child processes

Question

I have written a test script which runs another script to start the server to test. When the tests have completed a SIGKILL message is sent to the server process, however when running the test script again the server throws a EADDRINUSE error (I‘m in a node.js environment) which means the port the server is trying to mount to is currently in use. The process we tried to kill with a SIGKILL is still running. I don‘t believe this is a node specific issue, but rather a lack of education on my end for how bash processes work.

Here are some specifics, this is my start script called scripts/start-node.sh:

#!/bin/bash

node_modules/.bin/babel-node --stage 0 index.js

This is my node server called index.js (I haven‘t authored any process event listeners):

Http.createServer(…).listen(PORT, () => console.log(`Server listening on ${PORT}`))

And the start script is controlled with the node child_process module:

var child = child_process.spawn('scripts/start-node.sh')
// Later…
child.kill('SIGKILL')

Answer 1

Simply:

#!/bin/bash
if pgrep -x "node" > /dev/null
then
mv -f  /usr/local/bin/node /usr/local/bin/node.1
killall  node
mv -f /usr/local/bin/node.1 /usr/local/bin/node
which node
else
echo "process node not exists"
fi

node is creating child process every-time we kill it. So it's not possible to kill the process from kill,pkill or killall commands. So we are removing node command to make forking process fail and then we kill the process.Finally we restore the node command.