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: X-Spam-Status: No, score=-2.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 44B431FB36; Mon, 4 Aug 2014 18:39:23 +0000 (UTC) Date: Mon, 4 Aug 2014 18:39:23 +0000 From: Eric Wong To: Tony Devlin Cc: unicorn-public@bogomips.org Subject: Re: Weird Unicorn Timeout Issues (Hibernation problem?) Message-ID: <20140804183923.GA8732@dcvr.yhbt.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: Tony Devlin wrote: > We have an issue where if a site is not accessed for around (average) 30 > minutes the next query will timeout, and it will timeout on all the workers > opened. IE: If I have two workers, then both of those workers will > timeout, even if the first one, > after timeout, starts to work. As soon as the second worker is called upon > it will timeout. Then everything runs perfectly good and great until the > site is not accessed for 30 minutes or more. Then the timeout issue starts > all over again. This sounds like the idle timeout for MySQL (or similar) kicking in. What database(s) or other backends are you using? That said, we've had problems with hibernate/suspend in the past, so I'll double check.