From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: [ANN] unicorn 1.0.1 and 1.1.2 - fix rollbacks
Date: Wed, 14 Jul 2010 02:34:09 +0000 [thread overview]
Message-ID: <20100714023409.GB31092@dcvr.yhbt.net> (raw)
In-Reply-To: <4C3D1D7C.6010200@gmail.com>
Lawrence Pit <lawrence.pit@gmail.com> wrote:
> Hi Eric,
>
> At the top of my pastie http://pastie.org/1043347.txt you can see that
> when I request of list of gems it mentions only unicorn v1.1.2
>
> I also added the suggested logging to the before_fork block and I also
> logged the unicorn version. Interesting output. First it runs the master
> with Unicorn v1.1.2. But when I send a USR2 it exec'ed with a Unicorn
> v1.1.1 for the new master. So yes, I still had a version lying around,
> namely in the $APP_ROOT/vendor/bundler_gems dir.
>
> See also: http://pastie.org/1043487.txt
>
> It does do this though after a USR2:
>
> executing ["/usr/local/rvm/gems/ree-1.8.7-2010.02/bin/unicorn_rails",
> "-D", "-E", "staging", "-c",
> "/var/www/staging/current/config/unicorn/staging.rb"]
>
> I.e., it tries to exec exactly how I start unicorn. That unicorn_rails
> binary in that path is definitely v1.1.2. So I don't quite understand
> why the reexeced one is picking the version from the vendor/bundler_gems
> dir.
It's probably loading 1.1.1 because of GEM_HOME/GEM_PATH being set. The
"unicorn_rails"/"unicorn" wrappers just activates whatever gems it sees,
and GEM_HOME/GEM_PATH can influence the wrapper.
Managing RubyGems installations is still tricky :<
> I need to play a bit more with this.. I'll probably have to change my
> /etc/init.d/unicorn script so that it starts with the
> vendor/bundler_gems version instead of a system-wide version :o I'll
> get back to you..
Take a look at http://unicorn.bogomips.org/Sandbox.html According to
Jamie, using "bundle exec unicorn_rails" is the correct way to go.
--
Eric Wong
_______________________________________________
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
next prev parent reply other threads:[~2010-07-14 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:19 [ANN] unicorn 1.0.1 and 1.1.2 - fix rollbacks Eric Wong
2010-07-14 0:13 ` Lawrence Pit
2010-07-14 0:38 ` Eric Wong
2010-07-14 2:14 ` Lawrence Pit
2010-07-14 2:34 ` Eric Wong [this message]
2010-07-14 7:00 ` Lawrence Pit
2010-07-15 18:07 ` Jamie Wilkinson
2010-07-16 0:47 ` Lawrence Pit
2010-07-16 1:11 ` Lawrence Pit
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=20100714023409.GB31092@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--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).