error: Forever cannot find process with id
See original GitHub issueMy app is currently running, let’s say its name is name.js.
If I run forever list
, it shows name.js related entry.
But if I run forever stop name.js
it throws
error: Forever cannot find process with id: name.js
If I look at ps aux
output, it shows one entry for the currently running name.js app, and one entry for the monitor process.
Versions: node: 0.10.33 npm: 1.4.28 forever: 0.13.0
Issue Analytics
- State:
- Created 9 years ago
- Comments:17 (4 by maintainers)
Top Results From Across the Web
node.js - How to stop a forever process knowing the name
If you close it while it's not running, it will throw an error. Forever cannot find process with id. The first line looks...
Read more >Forever cannot find process with id - Bountysource
Cannot stop the mydomoathome: Forever cannot find process with id.
Read more >forever - npm
A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever). Latest version: 4.0.3, last published: a year ago....
Read more >Why does my node app process keep getting stopped when I ...
If the process is stopped after disconnecting from ssh, then try running nohup first. nohup forever start app.js. Or you can use forever...
Read more >Running Node.js scripts continuously using forever
Even if some error occurs, forever will restart the script for us. ... of the index id , script name, the uid ,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you have a directory like
/User/bitliner/Node/app
, and the entry isname.js
,forever stop
only works in following manners: Start it like these:or
or
If you wanna stop it, try to pass a relative or absolute path, like:
or
or
or
+1 This is a real problem . version 0.15.3