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 14AE444C004 for ; Tue, 20 Aug 2013 17:40:39 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 7B2C02E1ED; Tue, 20 Aug 2013 17:40:38 +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 C44262E17D for ; Tue, 20 Aug 2013 17:40:20 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 22DAE1F6BD; Tue, 20 Aug 2013 17:40:19 +0000 (UTC) Date: Tue, 20 Aug 2013 17:40:18 +0000 From: Eric Wong To: unicorn list Subject: Re: A barrage of unexplained timeouts Message-ID: <20130820174018.GA25675@dcvr.yhbt.net> References: <1377010076.87748476@apps.rackspace.com> <20130820163745.GA22586@dcvr.yhbt.net> <1377019663.33997248@apps.rackspace.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1377019663.33997248@apps.rackspace.com> User-Agent: Mutt/1.5.21 (2010-09-15) 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 nick@auger.net wrote: > "Eric Wong" said: > > Can you take a look at the nginx error and access logs? From what > > you're saying, there's a chance a request never even got to the Rails > > layer. However, nginx should be logging failed/long-running requests to > > unicorn. > > The nginx access logs show frequent 499 responses. The error logs are filled with: > > connect() failed (110: Connection timed out) while connecting to upstream > upstream timed out (110: Connection timed out) while reading response header from upstream > > What specific pieces of information should I be looking for in the logs? Do you have any other requests in your logs which could be taking a long time and hogging workers, but not high enough to trigger the unicorn kill timeout. (enable $request_time in nginx access logs if you haven't already) Is this with Unix or TCP sockets? If it's over a LAN, maybe there's still a bad switch/port/cable somewhere (that happens often to me). With Unix sockets, I don't recall encountering recent problems under Linux. Which OS are you running? I hit several TCP bugs in the early 3.7 Linux kernels, too... _______________________________________________ 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