From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from localhost (c143A4BC1.dhcp.bluecom.no [193.75.58.20])
        by mx.google.com with ESMTPS id 7sm543562eyb.0.2009.11.13.03.57.09
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Fri, 13 Nov 2009 03:57:10 -0800 (PST)
Content-Type: text/plain; charset=UTF-8
Subject: Re: [sup-talk] Sup not working anymore after abrupt reboot
From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>
In-reply-to: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com>
References: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com>
Date: Fri, 13 Nov 2009 12:57:05 +0100
Message-Id: <1258113332-sup-7090@dolk>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Carlos Garcia Campos's message of fr. nov. 13 10:11:38 +0100 2009:
> Hi all,
> 
> my laptop ran out of battery while sup was polling new mail and now sup
> always fails to start.
> I don't know whether my ferret index is corrupt, this is the exception  I
> get:
> 
> ----------------------------------------------------------------
> --- IOError from thread: main
> IO Error occured at <except.c>:93 in xraise
> Error occured in index.c:901 - sis_find_segments_file
> Error reading the segment infos. Store listing was
> 
> 
> /usr/lib/ruby/1.8/ferret/index.rb:736:in `initialize'
> /usr/lib/ruby/1.8/ferret/index.rb:736:in `new'
> /usr/lib/ruby/1.8/ferret/index.rb:736:in `ensure_reader_open'
> /usr/lib/ruby/1.8/ferret/index.rb:591:in `size'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /usr/lib/ruby/1.8/ferret/index.rb:590:in `size'
> ./lib/sup/ferret_index.rb:31:in `load_index'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> ./lib/sup/ferret_index.rb:29:in `load_index'
> ./lib/sup/index.rb:67:in `load'
> ./lib/sup/util.rb:520:in `send'
> ./lib/sup/util.rb:520:in `method_missing'
> bin/sup:144

Also, the xapian backend works better (doesn't help you now thou, im
afraid).

- gaute