From: Henrik Nyh <henrik@barsoom.se>
To: Eric Wong <normalperson@yhbt.net>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Workers reaped with SIGABRT - how to debug?
Date: Tue, 15 Apr 2014 11:05:45 +0200 [thread overview]
Message-ID: <CADBUp+2TcpzdLoUa3HAAyR_Yf2ufGG2RiO66nRy5ywRPWLtQYw@mail.gmail.com> (raw)
In-Reply-To: <20140415084327.GA28899@dcvr.yhbt.net>
On Tue, Apr 15, 2014 at 10:43 AM, Eric Wong <normalperson@yhbt.net> wrote:
> This is may be a bug in a C extension RubyGem or even Ruby itself.
> Do you get core dumps + backtraces or any other error messages in the logs?
You'd expect this to be in the Rails app's production.log, right? We
added that to our logging service this morning - we'll check it the
next time this error happens. Maybe we could also try to dig it up
from archived logs.
> Which OS/distribution is this?
Ubuntu 12.04.1 LTS
> Since you see SIGABRT/SIGIOT and not SIGSEGV, you might be crashing
> inside the SIGSEGV handler of Ruby itself.
>
> Can you also try --enable-debug-env when you ./configure Ruby?
I guess that would output more details to the Rails production.log in
the event of a crash? Will look into that.
> Thanks in advance for any more info you can provide!
Thanks so much for the help! Much appreciated.
_______________________________________________
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:[~2014-04-15 9:06 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 [this message]
2014-04-15 10:34 ` Aaron Suggs
2014-04-16 7:08 ` Henrik Nyh
2014-04-28 9:25 ` Henrik Nyh
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+2TcpzdLoUa3HAAyR_Yf2ufGG2RiO66nRy5ywRPWLtQYw@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).