unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Carlos Peñas" <theistian@gmx.com>
To: mongrel-unicorn@rubyforge.org
Subject: Confused about restart/upgrade w. bundler and symlinks
Date: Wed, 23 Oct 2013 10:35:19 +0200	[thread overview]
Message-ID: <20131023083519.GA5536@tydirium.the-staging.com> (raw)

Hi.

I'm having an issue using unicorn with bundler on a rails ap deployed by
capistrano

Im using bundler 1.3.5 (tried 1.4rc0 also) I'm deploying with
capistrano, version is irrelevant, the issue hit me when keep releases
is reached and 'current' symlink where "bundle unicorn" process was
initially started.

Im using also unicorn 4.6.3 and ruby 2.0.0, it is a Rails 4 app runing
on linux 3.2 64

I'm restarting with a init.d script which sends a HUP to master (restart) or USR2 (upgrade)

bundled gems are vendorized and stored in a shared location between
deploys. pids and logs also.

In the config have lines for:

Unicorn::HttpServer::START_CTX[0] pointing to the binary in the bundle

and ENV["BUNDLE_GEMFILE"] pointing to "current" path of the gemfile

When a capistrano deploy reach the :keep_releases and deletes a release
directory where unicorn was previously started the master kills all the
workers an the new worker get in a death loop telling that they can not
locate 'rack/builder'.

I traced the process and the diying worker threads are looking for files
in the deleted release directory.

Problem is crystal clear to me. Unix dereferences 'current' directory
and store it in the proc environment so when the referenced directory
dissapear unicorn workers aren't able to locate cwd. But I can't find a
workarround which let me use a deploy tool and bundle to keep project
gems.

So What i'm missing? is there a best practice I'm not following?.

Thanks

-- 
Carlos Peñas San José
carlos@adoptales.es

_______________________________________________
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:[~2013-10-23  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  8:35 Carlos Peñas [this message]
2013-10-23 16:02 ` Confused about restart/upgrade w. bundler and symlinks Eric Wong
2013-10-23 17:18   ` Daniel Condomitti

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=20131023083519.GA5536@tydirium.the-staging.com \
    --to=theistian@gmx.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).