Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Cc: Thorsten von Eicken <tve-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>
Subject: Re: HUP restart is delayed by 2 minutes
Date: Wed, 29 Jan 2014 08:31:47 +0000	[thread overview]
Message-ID: <20140129083147.GA26652@dcvr.yhbt.net> (raw)
In-Reply-To: <52E8AD1B.8090009-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>

Thorsten von Eicken <tve-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org> wrote:
> On 1/28/2014 11:02 PM, Eric Wong wrote:
> > Thorsten von Eicken <tve-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org> wrote:
> >> I'm having trouble getting the HUP restart to work properly (I do have
> >> preload_app=false). What happens is that on HUP the master reloads the
> >> config file, but it then always takes 2 minutes plus 1-2 seconds for the
> >> workers to be reaped. The servers is totally idle, so this is not due to
> >> some open connections. Here's how it looks in the log file with 2 worker
> >> processes:
> > Which concurrency option are you using and which version of Rainbows!,
> > unicorn and Ruby is this?
> root@vscale:/home/vscale-admin/current# bundle show rainbows
> /var/lib/gems/1.9.1/gems/rainbows-4.5.0
> root@vscale:/home/vscale-admin/current# bundle show unicorn
> /var/lib/gems/1.9.1/gems/unicorn-4.7.0
> root@vscale:/home/vscale-admin/current# bundle exec ruby -v
> ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
> root@vscale:/home/vscale-admin/current# bundle exec rainbows --version
> Rainbows! v4.5.0

This looks like a symptom of unicorn 4.8.0 interacting badly
with rainbows 4.5.0, not unicorn 4.7.0.  Can you give
rainbows 4.6.0 + unicorn 4.8.0 a try?  Unfortunately, I broke
rainbows 4.5.0 and earlier with unicorn 4.8.0 :x

I'll be pushing out unicorn 4.8.1 soon with a minor, unrelated bugfix.
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Do not quote signatures (like this one) or top post when replying

  parent reply	other threads:[~2014-01-29  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29  6:03 HUP restart is delayed by 2 minutes Thorsten von Eicken
     [not found] ` <52E89997.6020504-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>
2014-01-29  7:02   ` Eric Wong
     [not found]     ` <20140129070259.GA5938-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2014-01-29  7:26       ` Thorsten von Eicken
     [not found]         ` <52E8AD1B.8090009-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>
2014-01-29  7:32           ` Eric Wong
2014-01-29  8:31           ` Eric Wong [this message]
     [not found]             ` <20140129083147.GA26652-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2014-01-29 20:11               ` Thorsten von Eicken
     [not found]                 ` <52E9607A.60107-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>
2014-01-29 22:03                   ` Eric Wong
     [not found]                     ` <20140129220352.GA24393-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2014-01-29 22:41                       ` Thorsten von Eicken
2014-03-17 21:23                       ` Thorsten von Eicken
     [not found]                         ` <532767E2.70509-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org>
2014-03-17 21:27                           ` 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:

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140129083147.GA26652@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    --cc=tve-nkzjiHSqi6rZJqsBc5GL+g@public.gmane.org \


* 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).