From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS33070 50.56.128.0/17 X-Spam-Status: No, score=0.5 required=5.0 tests=AWL,RDNS_NONE shortcircuit=no autolearn=no version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (unknown [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 21F6B20E51 for ; Tue, 15 Apr 2014 08:43:36 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 05DBD2E1EE; Tue, 15 Apr 2014 08:43:34 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by rubyforge.org (Postfix) with ESMTP id BB6842E1F2 for ; Tue, 15 Apr 2014 08:43:28 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 81FA920E51; Tue, 15 Apr 2014 08:43:27 +0000 (UTC) Date: Tue, 15 Apr 2014 08:43:27 +0000 From: Eric Wong To: unicorn list Subject: Re: Workers reaped with SIGABRT - how to debug? Message-ID: <20140415084327.GA28899@dcvr.yhbt.net> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: Henrik Nyh X-BeenThere: mongrel-unicorn@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org Henrik Nyh 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 # 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? 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? Which OS/distribution is this? 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? Thanks in advance for any more info you can provide! (Btw, please keep everybody Cc:-ed since the mailing list is going in that direction, and rubyforge.org isn't very reliable in its final days. New ML announcement in a few days). _______________________________________________ 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