Subject: [sup-talk] Sup not working anymore after abrupt reboot

From: Carlos Garcia Campos <[email-masked]>
Date: Fri, 13 Nov 2009 10:11:38 +0100

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.
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Tero Tilus <[email-masked]>
Date: Fri, 13 Nov 2009 13:10:17 +0200

Carlos Garcia Campos, 2009-11-13 11:11:
> Error reading the segment infos.

I'm not familiar with the internals of ferret, but the error looks
pretty bad.  It might have lost part of index data files.  Do you
happen to have index or dump backups or find deleted files under
ferret/ with using undelete tools?

Lessons learned...

Always have regular (automatic, if possible) backups of your index
dump, ALWAYS!  I have sup-dump in my backup2l before-hook.

Hum.  I think for people who don't do cron backups it wouldn't be a
bad idea to create (optional) rotating sup-dumps on every start. (and
stop?)

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Carlos Garcia Campos <[email-masked]>
Date: Sat, 14 Nov 2009 14:22:50 +0100

Excerpts from Tero Tilus's message of vie nov 13 12:10:17 +0100 2009:
> pretty bad.  It might have lost part of index data files.

indeed, I have had to build a new index scratch. 

> Do you

No :-/

> dump, ALWAYS!  I have sup-dump in my backup2l before-hook.

Yes, I have a daily cron script for it now. 

> bad idea to create (optional) rotating sup-dumps on every start. (and

Thank you very much. 
-- 
Carlos Garcia Campos
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Gaute Hope <[email-masked]>
Date: Fri, 13 Nov 2009 12:57:05 +0100

> I don't know whether my ferret index is corrupt, this is the exception  I

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

- gaute