-
Notifications
You must be signed in to change notification settings - Fork 946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sudo forever start app.js loses running instances #88
Comments
@jamespwright What version of forever are you using? |
@jamespwright I can confirm the |
@jamespwright This is fixed in You will now get warnings to remind you: $ sudo forever start examples/server.js -p 8080
info: Running action: start
info: Forever processing file: examples/server.js
$ forever list
info: Running action: list
warn: Error contacting: /Users/Charlie/.forever/sock/forever.sock
info: No forever processes running
$ sudo forever list
info: Running action: list
info: Forever processes running
data: uid command script forever pid uptime logfile
data: [0] x_gw node examples/server.js -p 8080 43611 43612 0:0:0:3.659 /Users/Charlie/.forever/x_gw.log |
I'm running into this problem as well - when I run a node.js file with forever and then do |
Yep, I'm having the same problem... I'm not sure that this is fixed. The script continues to run, but forever doesn't list it. |
same here. not fixed. |
@indexzero @jamespwright Is this been fixed ? I'm struggling with the same reason right now. Jeezzz. :( |
Using an Amazon EC2 Micro instance to test right now and wanted to leave it running overnight to show a coworker of mine.
My app is using port 80 so I have to start it with 'sudo'
If I use 'sudo forever start app.js' forever launches it and tells me that it is running, then I do some things on the site (simple chat server for testing purposes right now, nothing spectacular) and run 'forever list' again and it tells me there are no running instances, even though I am currently using the site.
To make it worse, if you run 'sudo forever start app.js' again it goes through the same process, but it seems like the previous running process doesn't get stopped then either because the server progressively slows down at that point the more you launch new processes.
The text was updated successfully, but these errors were encountered: