Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Carlos Garcia Campos <carlosgc@gnome.org>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Sup not working anymore after abrupt reboot
Date: Fri, 13 Nov 2009 10:11:38 +0100	[thread overview]
Message-ID: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1095 bytes --]

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

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

Thanks in advance.

[-- Attachment #1.2: Type: text/html, Size: 1545 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

             reply	other threads:[~2009-11-13  9:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  9:11 Carlos Garcia Campos [this message]
2009-11-13 11:10 ` Tero Tilus
2009-11-14 13:22   ` Carlos Garcia Campos
2009-11-13 11:57 ` Gaute Hope

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com \
    --to=carlosgc@gnome.org \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox