unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Stephen Eley <sfeley@gmail.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: synchronous restart
Date: Tue, 31 Aug 2010 16:29:56 -0400	[thread overview]
Message-ID: <AANLkTikOiY9Dscz+tr1t1Powa8zPbHonawMzt2oFr_1F@mail.gmail.com> (raw)
In-Reply-To: <CC111CB2-3EBE-459D-81F7-71B273A4784F@tramchase.com>

On Tue, Aug 31, 2010 at 4:08 PM, Jamie Wilkinson <jamie@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
old process.

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.

Have Fun,
   Steve Eley (sfeley@gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  parent reply	other threads:[~2010-08-31 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 18:30 synchronous restart Jamie Wilkinson
2010-08-31 19:08 ` Clifton King
2010-08-31 20:08   ` Jamie Wilkinson
2010-08-31 20:15     ` Clifton King
2010-08-31 20:29     ` Stephen Eley [this message]
2010-08-31 23:59       ` Lawrence Pit
2010-08-31 20:58   ` Stephen Eley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikOiY9Dscz+tr1t1Powa8zPbHonawMzt2oFr_1F@mail.gmail.com \
    --to=sfeley@gmail.com \
    --cc=mongrel-unicorn@rubyforge.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).