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

Monit doesn't start after machine reboot #14

Closed
pulkitsinghal opened this issue May 29, 2012 · 3 comments
Closed

Monit doesn't start after machine reboot #14

pulkitsinghal opened this issue May 29, 2012 · 3 comments

Comments

@pulkitsinghal
Copy link

It may be in your sight down the road but I just wanted to highlight the fact that monit doesn't come back up after a system stop/start on aws.

You may instead choose to start monit from init via /etc/inittab.
If the monit dæmon should stop due to an error, the init program
will re-spawn a new monit process. Init will also automatically
start monit at machine boot time. To learn more on how to set-up
monit to run from init, read the monit man file.

If I get to it before you do, I'll be sure to write back or if this is actually a bug, then well ... consider it filed :)

@karmi
Copy link
Contributor

karmi commented Oct 31, 2012

@pulkitsinghal That's a problem for the Monit cookbook, surely?

@pulkitsinghal
Copy link
Author

ok so no chance that this is a config issue in the recipe here?

@karmi
Copy link
Contributor

karmi commented Oct 31, 2012

The cookbook just uses Monit to keep tabs on the elasticsearch process -- nothing more.

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