Bráulio Bhavamitra <[email protected]> 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.
