From: Eric Wong <email@example.com>
To: unicorn list <firstname.lastname@example.org>
Date: Tue, 17 Aug 2010 18:14:44 -0700 [thread overview]
Message-ID: <20100818011444.GA14052@dcvr.yhbt.net> (raw)
Jimmy Soho <email@example.com> wrote:
> Hi All,
> When I deploy new code I always go through the USR2 - QUIT process.
> missing. I've experienced this a few times now. We use rails 2.3.8,
> and have something like this in our layouts file:
> 'jquery.url_utils', 'jquery.form', 'jquery.hotkeys',
> 'jquery.livequery', 'application', :cache => 'base' %>
> When it's missing it doesn't matter how often I kill with USR2 / QUIT,
> it won't appear. If I stop the unicorn master process completely and
> then start again, then it does create the base.js file again.
> Anyone experienced this as well? Anyone know what could be the reason
> for this?
Hi Jimmy, Are you deploying with Capistrano and you originally started
Unicorn in a working_directory that no longer exists on the filesystem?
Under Linux, you can check the working directory of any process
with `ls -l /proc/$PID/cwd`
That's the only thing I can think of at the moment.
In your other email:
> I get the feeling that memory from the previous master/workers somehow
> isn't released and is used by the new unicorn master and/or worker
Shouldn't be possible unless your OS is broken. A more likely
explanation is that Unicorn process is pinned to the working
directory of an old deploy.
Unicorn mailing list - firstname.lastname@example.org
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2010-08-18 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 0:02 ` Jimmy Soho
2010-08-18 1:14 ` Eric Wong [this message]
2010-08-18 2:23 ` Jimmy Soho
2010-08-18 2:45 ` Eric Wong
2010-08-18 3:39 ` Jimmy Soho
2010-08-18 7:14 ` Eric Wong
2010-08-18 13:20 ` Jimmy Soho
2010-08-18 23:34 ` Eric Wong
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 \
* 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).