From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS33070 50.56.128.0/17 X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,T_DKIM_INVALID shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 4A32F1F5B1 for ; Tue, 10 Apr 2012 08:53:07 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 7DA51263042; Tue, 10 Apr 2012 08:53:06 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by rubyforge.org (Postfix) with ESMTP id 129B4263033 for ; Tue, 10 Apr 2012 08:52:59 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A2CEA20EB0 for ; Tue, 10 Apr 2012 04:52:59 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 10 Apr 2012 04:52:59 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= airbladesoftware.com; h=content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id :references:to; s=mesmtp; bh=28kXVDju01axOvtbEikwUq0zvSI=; b=pkt SYsWAckFPL/3gS5a/cViN45ondTCrDt6613TGOlAagG6OgFzm8EvYj3RiLbOTsiX rdhoWqb94drZ0UMphHhjRPJPLioR5JLm0+vE7H5HM6PDteS4FQ0pPm79J0/KXKeD X84hx6145l3Nd8kIDn6cFirbpiL6tAI4Ygnlol3E= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id :references:to; s=smtpout; bh=28kXVDju01axOvtbEikwUq0zvSI=; b=El yzcddt/dEYLb4YW1jDghdMyAOPK64a7JPLKXElWPiWWTbFkuz6V0nkwhq62wK+SO 5d81AL61e7/Hhd0V2mGbTqtAUG3y7bb1N/Ot+U0vd5Yfc5OhFJDdGuk0mkutaulD ZHai/oGHrCnBmEp2a3aQ7EcDYZE2p1MT1RTGlx1Q8= X-Sasl-enc: JLwyc7qshsSQqiVnIwp8RL/Bxn3ckddtbfYfVwzulpk5 1334047979 Received: from [192.168.88.252] (firewall.rst.de [80.146.246.2]) by mail.messagingengine.com (Postfix) with ESMTPSA id 48D398E00F0 for ; Tue, 10 Apr 2012 04:52:59 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1084) Subject: Re: Problem restarting Unicorn From: Andrew Stewart In-Reply-To: Date: Tue, 10 Apr 2012 10:52:57 +0200 Message-Id: <6C172DB9-D159-48A5-AB7C-4F41C2190AF6@airbladesoftware.com> References: <1D1E83EF-886F-409D-B61E-22F7309C3690@airbladesoftware.com> To: unicorn list X-Mailer: Apple Mail (2.1084) X-BeenThere: mongrel-unicorn@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org On 5 Apr 2012, at 13:34, Michael Guterl wrote: > On Thu, Apr 5, 2012 at 3:21 AM, Andrew Stewart 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