unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: SIGWINCH
Date: Mon, 12 Jul 2010 21:34:04 -0700	[thread overview]
Message-ID: <20100713043404.GC9716@dcvr.yhbt.net> (raw)
In-Reply-To: <4C3BEACF.7040301@gmail.com>

Lawrence Pit <lawrence.pit@gmail.com> wrote:
> Hi,
>
> I followed the procedure to replace a running unicorn. Works fine,  
> except for one thing: after I decide to back out, ie I send a HUP to the  
> old master followed by a QUIT to the new master, then:
>
> 1. the new master does die, and the old master does work again
>
> 2. the "old" master keeps running with a process name of "master (old)"
>
> 3. the "old" master keeps running with a pid file named unicorn.pid.oldbin
>
> Because the file is now named unicorn.pid.oldbin a later attempt to  
> deploy using scripts is made rather difficult as they assume a pid file  
> named unicorn.pid.
>
> How could I get unicorn to rename the pid file back to unicorn.pid ?  I  
> see some code in method +reap_all_workers+ that suggests it would rename  
> the pid file back to its original, but for some reason it doesn't for  
> me. Am I missing a step?

Hi Lawrence,

Are you using a config file to specify pid or --pid from the
command-line?  The config file should be more reliable.  I'll take a
deeper look at it in a bit.

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


  reply	other threads:[~2010-07-13  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-13  4:25 SIGWINCH Lawrence Pit
2010-07-13  4:34 ` Eric Wong [this message]
2010-07-13  4:48   ` SIGWINCH Lawrence Pit
2010-07-13  7:38   ` SIGWINCH Lawrence Pit
2010-07-13  8:24 ` SIGWINCH Eric Wong

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=20100713043404.GC9716@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).