From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs142892icb; Wed, 26 Jan 2011 18:14:08 -0800 (PST) Received: by 10.224.67.147 with SMTP id r19mr1088928qai.136.1296094448103; Wed, 26 Jan 2011 18:14:08 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id w3si18863477vbl.92.2011.01.26.18.14.07; Wed, 26 Jan 2011 18:14:08 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 23AFB18583CC; Wed, 26 Jan 2011 21:14:07 -0500 (EST) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 6A4D218583C3 for ; Wed, 26 Jan 2011 20:57:37 -0500 (EST) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1PiH7B-0007t8-5Q for sup-talk@rubyforge.org; Wed, 26 Jan 2011 20:57:37 -0500 From: William Morgan To: sup-talk In-reply-to: References: Date: Wed, 26 Jan 2011 20:57:36 -0500 Message-Id: <1296093042-sup-322@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] problem starting sup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Reformatted excerpts from Hamish D's message of 2011-01-26: > `method_missing': no Redwood::HookManager instance defined in method > call to run! (RuntimeError) > from /home/mish/dev/sup/sup-mainline/bin/sup:381 This is masking another exception. Something is breaking before HookManager is initialized, and in rescuing from it, we try and run the shutdown hook, which of course dies. Can you comment out that line? Or maybe try commenting out the three lines starting with rescue and ending with ensure at line 372 in bin/sup? This should at least unmask the exception. Initting the hookmanager happens very early on in Sup, so I'm guessing there's something wrong with your config file or the log file (the only two things that happen before the hookmanager is brought up). -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk