unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Andrew Stewart <boss@airbladesoftware.com>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Problem restarting Unicorn
Date: Tue, 10 Apr 2012 10:52:57 +0200	[thread overview]
Message-ID: <6C172DB9-D159-48A5-AB7C-4F41C2190AF6@airbladesoftware.com> (raw)
In-Reply-To: <CAEn+1bcef4vZf18JmmiCNs_2=amACCiao8HUj3y4GQ3YOJZbAA@mail.gmail.com>


On 5 Apr 2012, at 13:34, Michael Guterl wrote:
> On Thu, Apr 5, 2012 at 3:21 AM, Andrew Stewart <boss@airbladesoftware.com> wrote:
>> I just had a problem where a bundled gem wasn't being seen by the Unicorn processes, even though app code I introduced at the same time was being served by the Unicorn processes.  I had restarted Unicorn numerous times using `bundle exec cap deploy:restart` (see the code below), which I thought was the right way to do zero-downtime restarts, but my problem was only solved by doing a hard restart of Unicorn with `bundle exec cap deploy:hard_restart`.
> 
> You probably want to check out the Sandbox documentation here:
> http://unicorn.bogomips.org/Sandbox.html

Thanks for the pointer to the Sandbox documentation, the one page on the Unicorn website I hadn't read.  The section on BUNDLE_GEMFILE for Capistrano users was what I needed.

Yours,
Andy Stewart
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

      reply	other threads:[~2012-04-10  8:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  7:21 Problem restarting Unicorn Andrew Stewart
2012-04-05 11:34 ` Michael Guterl
2012-04-10  8:52   ` Andrew Stewart [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=6C172DB9-D159-48A5-AB7C-4F41C2190AF6@airbladesoftware.com \
    --to=boss@airbladesoftware.com \
    --cc=mongrel-unicorn@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://yhbt.net/unicorn.git/

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).