how to stop node.js server

Question

I run the node server by typing

node server.js

from a putty terminal to get it running. Now i want to stop the server how should i do it? I tried pressing the pause break button on the keyboard. But it is not stopping it.

score 16 · Accepted Answer · answered Apr 06 '11 at 12:39

16

Try using ctrl+c, usually does the trick.

answered Apr 06 '11 at 12:39

clmarquart

436
3
5

1

programmatically, you can use `app.close()` if `var app = require('http').createServer()`. – Lance Apr 12 '12 at 21:19

score 14 · Answer 2 · edited Nov 07 '20 at 19:45

14

Try from another terminal

killall node

Works in OS X and Linux. It may also prevent respawning node processes. For instance if a node some_server.js is running it may that any normal kill command (even kill -9 <PID_of_that_process> will simply result in a respawn node some_server.js process with a different PID. In that situation the only way to kill it is: killall node. I solved this issue on Redhat Linux RHEL7 but it should work the same for most Linux OS.

edited Nov 07 '20 at 19:45

Edwin Hendriks

3
2

answered Oct 01 '15 at 12:17

zag2art

241
3
6

1

only thing that worked. – George Katsanos Nov 05 '17 at 09:41
`killall node` maybe more than you want when you are running MERN apps, since you will have separate instances of node running the backend Express JS app and the frontend React JS app. You can use `ps -ef` to identify which specific node processes should be killed off. – Lazor Jan 12 '21 at 21:35

score 8 · Answer 3 · answered May 22 '11 at 20:19

If you are going to use the 'top' command to kill a process, you should try sending the '2' signal first, not '9'. Sending '9' is kind of like pulling the plug on your computer instead of issuing a shutdown command. It can sometimes have some undesirable consequences. Sending '2' has the same effect as ctrl+c.

For reference, here are the different signals you can send to stop a process and what they mean: (from kill man page)

 1       HUP (hang up)
 2       INT (interrupt)
 3       QUIT (quit)
 6       ABRT (abort)
 9       KILL (non-catchable, non-ignorable kill)
 14      ALRM (alarm clock)
 15      TERM (software termination signal)

score 5 · Answer 4 · answered Apr 06 '11 at 12:50

Enter 'top' at command line and find the process ID of the process you want to kill. Press 'K', it will prompt you to enter the process id that you want to kill, enter it, and press enter. It will then ask what signal you want to transmit to the process, enter '9' and press enter. The process will be killed.

score 0 · Answer 5 · answered Apr 15 '18 at 06:07

0

On windows os in command prompt, Press CTRL + C wait till it stops if it does not then Press the CTRL + C 2 times this will definitely work.

answered Apr 15 '18 at 06:07

Jasminder Pal

1

score 0 · Answer 6 · answered Jun 25 '18 at 14:11

0

ctrl + shift + c does the trick in ubuntu terminal

answered Jun 25 '18 at 14:11

xxddd

1

1

A Terminal shouldn't remap keys like this. – chicks Jun 25 '18 at 18:40

score 0 · Answer 7 · answered Jan 05 '20 at 17:10

I had the same problem while running npm from Babun and then i tried to use Windows CMD instead (because i had similar problem running git commands from Babun) and that showed different results.
When i run npm from CMD, i had to click Enter so that the script gets executed and then i was asked to click w to show more details.
I clicked w and that showed :

Watch Usage
› Press f to run only failed tests.
› Press o to only run tests related to changed files.
› Press p to filter by a filename regex pattern.
› Press t to filter by a test name regex pattern.
› Press q to quit watch mode.
› Press Enter to trigger a test run.

I clicked w and npm was stopped and returned control to CMD.

how to stop node.js server

7 Answers7