Skip to content
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

Service does not keep running after being started, while node process does #73

Open
amberv0 opened this issue Sep 5, 2016 · 0 comments

Comments

@amberv0
Copy link

amberv0 commented Sep 5, 2016

The problem is following. I install the service:

sudo forever-service install appname --script app.js --scriptOptions " --prod --port 1338" --foreverOptions " -w" --start

This gives no error. But then when I check the status with
sudo service appname status
I get appname is not running. But the started app actually IS running, and so everything works as should. But if I try to start the service (since I do want watching on file changes and so on), I'll get the error because the port is already in use.
I don't know by what this is caused, but it looks like the service somehow starts the node script and then disconnects from it.
I'm using CentOS 6.8
forever-service version 0.5.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant