From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.27.4 with SMTP id a4cs89285aga; Fri, 13 Nov 2009 01:37:34 -0800 (PST) Received: by 10.224.105.26 with SMTP id r26mr2494658qao.0.1258105054551; Fri, 13 Nov 2009 01:37:34 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 7si9864620qwb.55.2009.11.13.01.37.34; Fri, 13 Nov 2009 01:37:34 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id D6B701858302; Fri, 13 Nov 2009 04:37:33 -0500 (EST) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by rubyforge.org (Postfix) with ESMTP id 1608A18582BC for ; Fri, 13 Nov 2009 04:16:40 -0500 (EST) Received: by fg-out-1718.google.com with SMTP id 22so109481fge.5 for ; Fri, 13 Nov 2009 01:16:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=z/pgXg+xl98JS//8aPrwqgz+QHbXm5swyolU7nxPCIg=; b=vvQ2fEcuTXPHBpJFT2uz1RDa0DQHYMPgDBAXVXrMYd6NM/bHrv2T8nzaVhlCBwJI3r tlMS/br3gEUS/2HkjgxRWw6b1+nzPSBPsv9k1jmnJZM6xJpedN7CsB4JVNGIQredOVSh vcXwcOP59n2KVd2il0U7bG8o2VwuFe7w4UOEc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=FypH7vErOYULcN+UtV0/6r54gB4hJStj2MPE/wQtTISmIW1iMhYKwhjhlUwSDjXQ2/ fIY43CyuIZP32g6/ktp0WJ/qcZItk2PlOz6EEMRbnc50LJQaGgh1WJKcK6WghiM0CBG3 6c0AkctjLgETxGNxtl7Lhnlsg3s7I7zEUJvHY= MIME-Version: 1.0 Received: by 10.216.89.73 with SMTP id b51mr1325135wef.125.1258103498208; Fri, 13 Nov 2009 01:11:38 -0800 (PST) Date: Fri, 13 Nov 2009 10:11:38 +0100 X-Google-Sender-Auth: a625d98b1e1b2aad Message-ID: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com> From: Carlos Garcia Campos To: sup-talk@rubyforge.org Subject: [sup-talk] Sup not working anymore after abrupt reboot 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: , Content-Type: multipart/mixed; boundary="===============0693820757==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============0693820757== Content-Type: multipart/alternative; boundary=0016e6d6448619f68904783d0c90 --0016e6d6448619f68904783d0c90 Content-Type: text/plain; charset=ISO-8859-1 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 :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 is there any way to recover it? (if possible without losing mi index . . . ) Thanks in advance. --0016e6d6448619f68904783d0c90 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,=A0

my laptop ran out of battery while sup was po= lling new mail and now sup always fails to start.=A0
I don't = know whether my ferret index is corrupt, this is the exception =A0I get:

--------------------------------------------------= --------------
--- IOError from thread: main
IO Error o= ccured 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'
<= div> /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/su= p/ferret_index.rb:31:in `load_index'
/usr/lib/ruby/1.8/monito= r.rb:242:in `synchronize'
./lib/sup/ferret_index.rb:29:in `lo= ad_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

is there any way to recover it? (if= possible without losing mi index . . . )

Thanks in advance.=A0
--0016e6d6448619f68904783d0c90-- --===============0693820757== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============0693820757==--