search

foreversd / forever

A simple CLI tool for ensuring that a given script runs continuously (i.e. forever)
http://github.com/foreverjs/forever
MIT License
13.88k stars 945 forks source link

forever stop didn`t kill the process, when restart throw an error listen EADDRINUSE #971

Open NextZeus opened 6 years ago

NextZeus commented 6 years ago
  1. forever stop xxx
  2. forever start -a -l xx.all.log -o xx.out.log -e xx.error.log -p /data/logs/ --uid xxx --id xxx app.js env=development
jmeyers91 commented 6 years ago

Any update on this? I'm using node-cleanup to close my webservers and database connection, but it appears forever isn't triggering any of the cleanup conditions, so now I can't restart my server without finding and killing the process with the associated port.

xh4010 commented 5 years ago

I also encountered this problem (Windows10, Nodejs 10.15, forever 0.15.3), is there any new development? Currently I use the command to manually kill the process:

netstat -ano | findstr 9002
taskkill /f /t /pid xxxx
dkladis commented 5 years ago

I have the same problem on Windows Server 2016 and Node 10.15.0 and Forever 0.15.3. Any suggestions?

solymosi commented 5 years ago

Looks like --killTree is not supported on Windows 😢
https://github.com/foreversd/forever-monitor/blob/master/lib/forever-monitor/common.js#L41