From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.179.196 with SMTP id br4cs287047icb; Thu, 2 Dec 2010 05:42:52 -0800 (PST) Received: by 10.224.37.141 with SMTP id x13mr72443qad.76.1291297371989; Thu, 02 Dec 2010 05:42:51 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id r3si1274407qcs.198.2010.12.02.05.42.50; Thu, 02 Dec 2010 05:42:50 -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; DomainKey-Status: no key 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; domainkeys=neutral (no key) header.From=david@rysdam.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 94CEB19783BF; Thu, 2 Dec 2010 08:42:50 -0500 (EST) X-Greylist: delayed 441 seconds by postgrey-1.31 at rubyforge.org; Thu, 02 Dec 2010 08:21:09 EST Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by rubyforge.org (Postfix) with SMTP id 327951858385 for ; Thu, 2 Dec 2010 08:20:46 -0500 (EST) Received: (qmail 10644 invoked by uid 0); 2 Dec 2010 12:20:22 -0000 Received: from unknown (HELO host378.hostmonster.com) (66.147.240.178) by oproxy1.bluehost.com.bluehost.com with SMTP; 2 Dec 2010 12:20:22 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=rysdam.org; h=Received:Content-Type:Subject:From:To:In-reply-to:References:Date:Message-Id:User-Agent:Content-Transfer-Encoding:X-Identified-User; b=ROwyhV63xgwMCdrJFB9TFqSDuj2SB0svMZ1sXRL9s/wFBaNfcTiTfLt8PuHuKnvATKOE52+vXUblHQWgZMFHvBdTdCSdZwYKd8bh/d7b7ttmwAP7lK4kWluWKJmWaSMH; Received: from pool-71-161-86-116.cncdnh.east.myfairpoint.net ([71.161.86.116] helo=rysdam.org) by host378.hostmonster.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1PO8yf-00044V-Bf for sup-talk@rubyforge.org; Thu, 02 Dec 2010 06:13:37 -0700 From: David Rysdam To: sup-talk In-reply-to: References: Date: Thu, 02 Dec 2010 08:13:35 -0500 Message-Id: <1291295519-sup-2688@hero> User-Agent: Sup/0.10.2 X-Identified-User: {1333:host378.hostmonster.com:kristenv:rysdam.org} {sentby:smtp auth 71.161.86.116 authed with david@rysdam.org} Subject: Re: [sup-talk] Can't start Sup, allegedly because of a locked index. 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 An agent or agents purporting to be Shadowfirebird said: > Anyone got any ideas how I get out of this? > > >>>> > $ sup > Error: the index is locked by another process! User '' on > host '' is running with pid . > The process was alive as of at least 4216 minutes ago. > Should I ask that process to kill itself (y/n)? n > Sorry, couldn't unlock the index. I don't have this exact problem, but I have had problems where sup has claimed to be unable to kill another instance because of a lock problem. I get a different message, but I'm running an old version. I find that sometimes Xapian has left a lockfile. If I delete .sup/xapian/flintlock then I can start sup just fine. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk