"sendalerts" dies on MySQL interruption about healthchecks HOT 5 CLOSED

Thanks for the kind words.

How are you running the sendalerts command?

I'm running it using supervisor. If the command exits, supervisor restarts it. It should be possible to set it up similarly with systemd, upstart etc. too.

from healthchecks.

Never tried supervisor before... I'll honestly have to look it up and see what it's all about.

Right now I have a script set in rc.local to launched a tmux window, then starts another bash script the opens and names new windows, then in each window runs the python, bash or other script/app that I'd like. That way I can connect into my boxes tmux a and see everything that's running with a decent bit of history.

Do have any tips/tutorial you can point me to for supervisor?

from healthchecks.

http://supervisord.org/running.html

from healthchecks.

Yup.... did some googling last night, I can't believe I've never seen this before. Getting anything newer than 3.0 running well on Ubuntu 14.04 is still a bit of a challenge, but the default repo version of 3.0 runs pretty well except the "tail -f" option seems to be giving me an error. I will however be putting this together on my DEV server ASAP.... it's AWESOME!

from healthchecks.

In summary I would recommend to run sendalerts command under a daemon which will respawn it when it dies. Supervisor is one option. Another interesting option is uwsgi. If you use uwsgi web server to serve the webapp, you can configure it to also run the sendalerts command. With uwsgi you can also run regular cron-style maintenance tasks, and do a lot of other things.

We can guard and work around specific runtime errors like "mysql has gone away" but in general with the different integrations there can be many kinds of exceptions and I don't think it would be good idea to just catch and ignore all of them.

from healthchecks.