question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Stopping npm proccesses

See original GitHub issue

Following up from the comments left in #540 after it was closed, I’m having problems killing npm daemons.

# forever --version
v0.15.1
# forever start -a -l /logs/forever.log -o /logs/out.log -e /logs/error.log -c "npm start" ./
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: ./
# forever list
info:    Forever processes running
data:        uid  command   script forever pid   id logfile      uptime
data:    [0] MGr8 npm start        16231   16240    /forever.log 0:0:0:3.175
# forever stop 0
info:    Forever stopped process:
    uid  command   script forever pid   id logfile      uptime
[0] MGr8 npm start        16231   16240    /forever.log 0:0:0:22.487
# forever list
info:    No forever processes running
# ps aux | grep node
root     16251  0.0  0.0   4444   660 ?        S    10:46   0:00 sh -c node --harmony --harmony_destructuring scripts/start "/root/..."
root     16252  1.4  0.1 909448 30756 ?        Sl   10:46   0:00 node --harmony --harmony_destructuring scripts/start /root/...
# kill 16252
# ps aux | grep node
#

Issue Analytics

  • State:open
  • Created 8 years ago
  • Reactions:2
  • Comments:5

github_iconTop GitHub Comments

2reactions
aprilmintacpinedacommented, Dec 11, 2019

I just encountered this today while developing with create-react-app. Did not find any solution.

1reaction
darrennolancommented, Apr 25, 2017

Hey, did anyone here have a work around for this issue? I’m on v0.15.3 and I’ve just encountered this issue.

Cheers,

Read more comments on GitHub >

github_iconTop Results From Across the Web

Stop Node Server: How to kill a node process
Stop Node Server How to kill a node process · npm run react-scripts start. or · sls offline start --port 3001. When you...
Read more >
How to stop app that node.js express 'npm start' - Stack Overflow
Yes, npm provides for a stop script too: npm help npm-scripts. prestop, stop, poststop: Run by the npm stop command.
Read more >
npm-stop
Description. This runs a predefined command specified in the "stop" property of a package's "scripts" object. Unlike with npm start, there is no...
Read more >
How to exit a process in Node.js? - Tutorialspoint
Method 1: Using the Ctrl+C key. I hope everyone knows this shortcut to exit any Node.js process from outside. This shortcut can be...
Read more >
How to exit process in Node.js ? - GeeksforGeeks
Method 2: Using process.exit() Function: This function tells Node.js to end the process which is running at the same time with an exit...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found