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

Monitor and automatically restart dead services #46

Open
nightsh opened this issue May 30, 2014 · 1 comment
Open

Monitor and automatically restart dead services #46

nightsh opened this issue May 30, 2014 · 1 comment

Comments

@nightsh
Copy link
Contributor

nightsh commented May 30, 2014

For example, right now the server throws a Nginx error, but the machine itself seems to be working (I received the daily notification, I guess it's a cron job).

A system monitoring components that are listening for connections would be nice. Of course, there are some privileges issues here, it must have some authority over processes on the server (at least the ones owned by the Intertwinkles user).

Disclaimer: though I'm not fully aware of how the whole platform operates, I tried to suggest things based on my very recent observations – server not serving over HTTP, yet other processes still moving in the backend.

(BTW, please restart the dead services now, so we can access the web frontend again)

@yourcelf
Copy link
Owner

yourcelf commented Jun 1, 2014

Apologies, as with most outages, this was due to multiple failures. The InterTwinkles process crashed; the supervisor daemon that is supposed to restart it failed to; I was off-grid for a few days and missed the monitoring server's notices; and the backup sysadmin who was watching the server failed to act on the monitoring server's notices.

We're re-evaluating the strategy for checking this in order to prevent future outages.

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