From mboxrd@z Thu Jan 1 00:00:00 1970 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.0 required=3.0 tests=MSGID_FROM_MTA_HEADER, TVD_RCVD_IP shortcircuit=no autolearn=unavailable version=3.3.2 Path: news.gmane.org!not-for-mail From: Samuel Kadolph Newsgroups: gmane.comp.lang.ruby.rainbows.general Subject: Unicorn is killing our rainbows workers Date: Wed, 18 Jul 2012 14:52:50 -0400 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1342637580 4873 80.91.229.3 (18 Jul 2012 18:53:00 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 18 Jul 2012 18:53:00 +0000 (UTC) To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Original-X-From: rainbows-talk-bounces-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Wed Jul 18 20:52:58 2012 Return-path: Envelope-to: gclrrg-rainbows-talk@m.gmane.org X-Original-To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Delivered-To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=V3N83Y4tHGwRiSpo021RVTbrG3PpQROlwhoanjUfe+g=; b=N9TES/Vif8fQpnyEHEXzKuizHsCuiazUMSLTnBtj3JpxWhOPYhioGPHQ6s+Z9GDk6p ZTMotvIIDGXnzkexdM1UPX8V1RpocdJnJwmgJtQ6LIQh62PFdM+xAlNLxDOVq6Bi/KHK OQDc9ewYwlpf4OAFaruHl/jabX4EsJDVkX8cY46ZeboBTr3W64t3t47kw/gYx1jfAFd4 DHC659DtuKkb7vC1Yuo6zIptwfJJCVMfq5UilMBPfNulc8myRWcxhAi6mYy4Xhsi0qiM gi6LjEOrCyCdcbJUn5bRf0O19iUVnNAaOAE/1E9IQlarHRbX+RjkYFwEaGEy1I3pJXWw kdBA== X-Gm-Message-State: ALoCoQnlXJ6bUkkBTLQf/Wdj+cUy5CS7Q5L3aK2bxpaGrll9bXUc3YQ0G+cU6/3OE5VVLpf3oxNj X-BeenThere: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: rainbows-talk-bounces-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Errors-To: rainbows-talk-bounces-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Xref: news.gmane.org gmane.comp.lang.ruby.rainbows.general:370 Archived-At: Received: from 50-56-192-79.static.cloud-ips.com ([50.56.192.79] helo=rubyforge.org) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SrZMn-0000kA-Gd for gclrrg-rainbows-talk@m.gmane.org; Wed, 18 Jul 2012 20:52:57 +0200 Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 5ED5B2E068; Wed, 18 Jul 2012 18:52:55 +0000 (UTC) Received: from mail-pb0-f50.google.com (mail-pb0-f50.google.com [209.85.160.50]) by rubyforge.org (Postfix) with ESMTP id 7B0462E068 for ; Wed, 18 Jul 2012 18:52:50 +0000 (UTC) Received: by pbbrr4 with SMTP id rr4so3340866pbb.23 for ; Wed, 18 Jul 2012 11:52:50 -0700 (PDT) Received: by 10.68.223.35 with SMTP id qr3mr10068776pbc.83.1342637570037; Wed, 18 Jul 2012 11:52:50 -0700 (PDT) Received: by 10.66.217.225 with HTTP; Wed, 18 Jul 2012 11:52:50 -0700 (PDT) Hey rainbows-talk, We have 40 servers that each run rainbows with 2 workers with 100 threads using ThreadPool. We're having an issue where unicorn is killing the worker process. We use ThreadTimeout (set to 70 seconds) and originally had the unicorn timeout set to 150 seconds and we're seeing unicorn eventually killing each worker. So we bumped the timeout to 300 seconds and it took about 5 minutes but we started seeing unicorn starting to kill workers again. You can see our stderr log file (timeout at 300s) at https://gist.github.com/9ec96922e55a59753997. Any insight into why unicorn is killing our ThreadPool workers would help us greatly. If you require additional info I would be happy to provide it. Samuel Kadolph samuel.kadolph-BqItboTaHx1BDgjK7y7TUQ@public.gmane.org 16134043579 _______________________________________________ Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org http://rubyforge.org/mailman/listinfo/rainbows-talk Do not quote signatures (like this one) or top post when replying