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

Using node-startup in AWS EC2 - reboot does not start the service #29

Open
funmu opened this issue Feb 5, 2016 · 1 comment
Open

Using node-startup in AWS EC2 - reboot does not start the service #29

funmu opened this issue Feb 5, 2016 · 1 comment

Comments

@funmu
Copy link

funmu commented Feb 5, 2016

node-startup is real simple and cool. I tried to use it for setting up an app on AWS EC2 instance. Initially I had a few failures from
a) Needing to add "sudo" to all the commands including "rm pid file", "mkdir", "chown", etc. Why would this be required? ... this was required when I was running this from the bash shell directly to test out the script.
b) Even after setting this script up in /etc/init.d and setting up the chkconfig --add node-startup
, I noticed that the app does not start up after a reboot automatically. What might be wrong?
c) One of the reason that at reboot the node-startup does not work is, the old pid file is still around. Hence the start command fails. How can i ensure that the node-startup app is shutdown or pid file is ignored only at the reboot and initial startup?

Thanks for your help. Again, this script is nice and simple!

@jsonpoindexter
Copy link

jsonpoindexter commented Apr 25, 2017

You can force an override / remove old pid file on every start by changing the variable FORCE_OP on line 36 from false to true .

So line 36 should look like this: FORCE_OP=true

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

2 participants