unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Bráulio Bhavamitra" <braulio@eita.org.br>
To: Eric Wong <e@80x24.org>
Cc: unicorn-public <unicorn-public@bogomips.org>
Subject: Re: Show request details on timeout killing
Date: Fri, 5 Dec 2014 18:58:47 -0300	[thread overview]
Message-ID: <CAJri6_vPrzo32oyKpE86LT5NkMy8RfMiDhq9xvYgJkr2H4q7hQ@mail.gmail.com> (raw)
In-Reply-To: <20141205010614.GB1104@dcvr.yhbt.net>

Ok Eric, the problem is that some requests are in a infinite loop,
consuming a lot of resources.

Rails/nginx already log many request on production.log/access.log, but
I can't know which of them timeouted.


On Thu, Dec 4, 2014 at 10:06 PM, Eric Wong <e@80x24.org> wrote:
> Bráulio Bhavamitra <braulio@eita.org.br> wrote:
>> Hello all,
>> Currently, unicorn kills a worker that reached timeout with the
>> following message:
>> E, [2014-12-04T19:12:23.646053 #32612] ERROR -- : worker=4 PID:11911
>> timeout (61s > 60s), killing
>> How can I see which URL was being processed by that worker?
> I suggest adding better logging to your app, perhaps to log when
> requests start.
>> I need to identify the problematic request.
> And to use application-level timeouts, see:
>         http://unicorn.bogomips.org/Application_Timeouts.html
> The SIGKILL timeout in unicorn is only a last resort when the Ruby VM
> is broken beyond repair and cannot respond to any signals[1].
> [1] SIGKILL and SIGSTOP are special signals which the kernel
>     enforces, Ruby has no chance to block/catch/ignore them.

  reply	other threads:[~2014-12-05 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 21:15 Show request details on timeout killing Bráulio Bhavamitra
2014-12-05  1:06 ` Eric Wong
2014-12-05 21:58   ` Bráulio Bhavamitra [this message]
2014-12-05 22:16     ` 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/unicorn/

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

  git send-email \
    --in-reply-to=CAJri6_vPrzo32oyKpE86LT5NkMy8RfMiDhq9xvYgJkr2H4q7hQ@mail.gmail.com \
    --to=braulio@eita.org.br \
    --cc=e@80x24.org \
    --cc=unicorn-public@bogomips.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).