From: Troex Nevelin <list@mrtech.ru>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Master repeatedly killing workers due to timeouts
Date: Sun, 11 Dec 2011 16:19:48 +0200 [thread overview]
Message-ID: <4EE4BC04.60609@mrtech.ru> (raw)
In-Reply-To: <CAF5DW8+BNqYEdxkfUuYj72jxpfsA1C3B8iPoFh9tkdSHkM--vA@mail.gmail.com>
Hello,
I have a simillar problem that started after update, 3 days ago we
moved from REE 1.8 / Rails 2 to Ruby 1.9.3 and Rails 3.1, also we
replaced memcached with redis so this is huge update and there are
many places where we can have an issue.
I also have checked my MySQL slow log and there are no requests which
take more than 5 seconds to complete.
My question is it possible to log the last request (URI) made to the
worker before killing it on timeout?
It's really hard to track this problem, usually unicorn start killing
workers when we got 1500-2000 rpms on 8 workers.
--
E, [2011-12-11T18:11:42.335656 #31736] ERROR -- : worker=1 PID:1632
timeout (61s > 60s), killing
E, [2011-12-11T18:11:42.364076 #31736] ERROR -- : reaped
#<Process::Status: pid 1632 SIGKILL (signal 9)> worker=1
I, [2011-12-11T18:11:42.364364 #31736] INFO -- : worker=1 spawning...
I, [2011-12-11T18:11:42.366721 #5869] INFO -- : worker=1 spawned pid=5869
I, [2011-12-11T18:11:42.366942 #5869] INFO -- : Refreshing Gem list
_______________________________________________
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
next prev parent reply other threads:[~2011-12-11 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 18:19 Master repeatedly killing workers due to timeouts Jonathan del Strother
2011-12-08 20:23 ` Eric Wong
2011-12-08 22:24 ` Jonathan del Strother
2011-12-11 14:19 ` Troex Nevelin [this message]
2011-12-11 20:13 ` Eric Wong
2011-12-15 20:29 ` Troex Nevelin
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=4EE4BC04.60609@mrtech.ru \
--to=list@mrtech.ru \
--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).