From: Henrik Nyh <henrik@barsoom.se>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Cc: Eric Wong <normalperson@yhbt.net>
Subject: Re: Workers reaped with SIGABRT - how to debug?
Date: Mon, 28 Apr 2014 11:25:19 +0200 [thread overview]
Message-ID: <CADBUp+1R8Mfh2rNMa1hXr2XE06dD_869Sw=5YDffR-DSH7g+7w@mail.gmail.com> (raw)
In-Reply-To: <CADBUp+3v0za7qQDBPt4b15jiMA2GpXpxbMLw6CQY3dRkjv=UoQ@mail.gmail.com>
I think we have solved this issue.
It was simply that monit did a "kill -6" (SIBABRT) when the process
used too much memory, so we bumped that limit for now. D'oh. We've yet
to research why it used that much memory.
On Tue, Apr 15, 2014 at 10:00 AM, Henrik Nyh <henrik@barsoom.se> wrote:
> We get errors like this one a few times a day:
>
> Apr 13 12:16:31 app1 unicorn.log: E, [2014-04-13T12:16:31.302011
> #17269] ERROR -- : reaped #<Process::Status: pid 17300 SIGABRT (signal
> 6)> worker=2
>
> We use Unicorn 4.8.2, Ruby 2.1.1 and a Ruby on Rails app.
>
> It doesn't seem to happen at any obvious time, like during or just
> after deploys.
>
> We were previously on Ruby 1.9.3 with Unicorn 4.8.0. Then we had
> almost the same issue but with SIGIOT, I believe. Then we upgraded
> Ruby to 2.1.1. I believe that's when it changed to SIGABRT. Then we
> upgraded Unicorn to 4.8.2 with no improvement.
>
> We're not sure how to debug this - any suggestions on either what the
> problem could be, or how to debug it?
next prev parent reply other threads:[~2014-04-28 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 8:00 Workers reaped with SIGABRT - how to debug? Henrik Nyh
2014-04-15 8:43 ` Eric Wong
2014-04-15 9:05 ` Henrik Nyh
2014-04-15 10:34 ` Aaron Suggs
2014-04-16 7:08 ` Henrik Nyh
2014-04-28 9:25 ` Henrik Nyh [this message]
2014-04-28 10:41 ` 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:
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='CADBUp+1R8Mfh2rNMa1hXr2XE06dD_869Sw=5YDffR-DSH7g+7w@mail.gmail.com' \
--to=henrik@barsoom.se \
--cc=mongrel-unicorn@rubyforge.org \
--cc=normalperson@yhbt.net \
/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).