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: unicorn-public <unicorn-public@bogomips.org>
Subject: Show request details on timeout killing
Date: Thu, 4 Dec 2014 18:15:57 -0300	[thread overview]
Message-ID: <CAJri6_ti2Agk56q9ePj5hgWhmm-Gz1uS0xNp7zO_JRDZpYz3Xw@mail.gmail.com> (raw)

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 need to identify the problematic request.


             reply	other threads:[~2014-12-04 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 21:15 Bráulio Bhavamitra [this message]
2014-12-05  1:06 ` Show request details on timeout killing Eric Wong
2014-12-05 21:58   ` Bráulio Bhavamitra
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_ti2Agk56q9ePj5hgWhmm-Gz1uS0xNp7zO_JRDZpYz3Xw@mail.gmail.com \
    --to=braulio@eita.org.br \
    --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).