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: AS14383 205.234.109.0/24 X-Spam-Status: No, score=-0.6 required=5.0 tests=AWL,MSGID_FROM_MTA_HEADER, NORMAL_HTTP_TO_IP,RP_MATCHES_RCVD,WEIRD_PORT shortcircuit=no autolearn=unavailable version=3.3.2 Path: news.gmane.org!not-for-mail From: John-Paul Bader Newsgroups: gmane.comp.lang.ruby.unicorn.general Subject: "upstream timed out" after upgrades Date: Thu, 4 Feb 2010 09:16:35 +0100 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1265271762 18698 80.91.229.12 (4 Feb 2010 08:22:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 4 Feb 2010 08:22:42 +0000 (UTC) To: unicorn list Original-X-From: mongrel-unicorn-bounces@rubyforge.org Thu Feb 04 09:22:34 2010 Return-path: Envelope-to: gclrug-mongrel-unicorn@m.gmane.org X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org X-Mailer: Apple Mail (2.1077) 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: , Original-Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org Xref: news.gmane.org gmane.comp.lang.ruby.unicorn.general:383 Archived-At: Received: from rubyforge.org ([205.234.109.19]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ncwyw-0000WW-Fx for gclrug-mongrel-unicorn@m.gmane.org; Thu, 04 Feb 2010 09:22:34 +0100 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id BD03C18582E1; Thu, 4 Feb 2010 03:22:33 -0500 (EST) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) by rubyforge.org (Postfix) with ESMTP id 6B00F18582D5 for ; Thu, 4 Feb 2010 03:16:38 -0500 (EST) Received: (qmail 62658 invoked from network); 4 Feb 2010 08:16:36 -0000 Received: from mail.h3q.com (HELO mail.h3q.com) (hukl) by mail.h3q.com with AES128-SHA encrypted SMTP; 4 Feb 2010 08:16:36 -0000 Hey guys, i recently updated several components of my website setup: = varnish 2.0.5 -> 2.0.6 nginx 7.4.2 -> 7.4.5 unicorn 0.95.3 -> 0.96 ruby18 to the latest patch level = and rails from 2.3.2 It all seemed to work great but recently I noticed that the website hangs l= oading. The weird thing is that it hangs because 2 or 3 javascript files ta= ke about a minute to finish and when they do they are incomplete as in cut = of in the middle of the content. The nginx error log gives the following ou= tput every few seconds: 2010/02/04 08:58:41 [error] 29389#0: *471 upstream timed out (60: Operation= timed out) while reading upstream, client: 213.73.89.122, server: www.ccc.= de, request: "GET /javascripts/jquery-1.3.2.min.js?1246657683 HTTP/1.1", up= stream: "http://unix:/var/run/unicorn.sock:/javascripts/jquery-1.3.2.min.js= ?1246657683", host: "www.ccc.de" I don't think its varnishs fault because i get Internal Server Errors (500)= if I run curl on the machine against nginx, not at first though - several = requests for that jquery file run just fine and then suddenly i get a 500 o= n a request with the content being cut of in the middle. Next thing I did was configuring unicorn to listen on 213.73.89.122:9090 ra= ther than on a socket so i could run curl directly against it and even afte= r a fresh start of unicorn gives me: curl http://213.73.89.122:9090/javascripts/jquery-1.3.2.min.js (lots of javascript)=85,rowspan:"rowSpan",tabindex:"tabIndHTTP/1.1 500 Inte= rnal Server Error curl: (18) transfer closed with 16256 bytes remaining to read I also downgraded back to 0.95.3 but that didn't change anything. So now af= ter 8h of try and error I'm out of ideas and would be happy to hear some su= ggestions. Kind regards, John _______________________________________________ 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