sfeley at gmail.com
Tue Aug 31 16:29:56 EDT 2010
On Tue, Aug 31, 2010 at 4:08 PM, Jamie Wilkinson <jamie at tramchase.com> wrote:
> I should clarify... the above is exactly what I'm trying to avoid. i.e. how do you know if your new master failed to boot unless you are actively tailing the logs?
Well, first, you can specify a .pid file in your Unicorn configuration
file, then look at it before and a few seconds after the USR2 signal
to see if the process IDs are different. Unicorn's pretty smart about
maintaining that file, and copying the old one out until you kill the
Second... I'm confused as to why you think tailing the logs is
something to be avoided. Isn't finding out status what logs are
*for?* You could certainly automate the inspection and have some
process that emails you with an alarm if things don't look right.
Regardless of how you do it, if you're hoping to get away with
frequent automated deploys without *some* verification that requests
are working, you're taking big risks. Even if your unicorn process
runs, you could still have problems at the application level throwing
exceptions at every user.
Steve Eley (sfeley at gmail.com)
ESCAPE POD - The Science Fiction Podcast Magazine
More information about the mongrel-unicorn