* [sup-talk] Sup not working anymore after abrupt reboot
@ 2009-11-13 9:11 Carlos Garcia Campos
2009-11-13 11:10 ` Tero Tilus
2009-11-13 11:57 ` Gaute Hope
0 siblings, 2 replies; 4+ messages in thread
From: Carlos Garcia Campos @ 2009-11-13 9:11 UTC (permalink / raw)
To: sup-talk
[-- 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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] Sup not working anymore after abrupt reboot
2009-11-13 9:11 [sup-talk] Sup not working anymore after abrupt reboot Carlos Garcia Campos
@ 2009-11-13 11:10 ` Tero Tilus
2009-11-14 13:22 ` Carlos Garcia Campos
2009-11-13 11:57 ` Gaute Hope
1 sibling, 1 reply; 4+ messages in thread
From: Tero Tilus @ 2009-11-13 11:10 UTC (permalink / raw)
To: sup-talk
Carlos Garcia Campos, 2009-11-13 11:11:
> I don't know whether my ferret index is corrupt, this is the exception I
> get:
>
> ----------------------------------------------------------------
> Error occured in index.c:901 - sis_find_segments_file
> 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
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] Sup not working anymore after abrupt reboot
2009-11-13 11:10 ` Tero Tilus
@ 2009-11-14 13:22 ` Carlos Garcia Campos
0 siblings, 0 replies; 4+ messages in thread
From: Carlos Garcia Campos @ 2009-11-14 13:22 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 1147 bytes --]
Excerpts from Tero Tilus's message of vie nov 13 12:10:17 +0100 2009:
> Carlos Garcia Campos, 2009-11-13 11:11:
> > I don't know whether my ferret index is corrupt, this is the exception I
> > get:
> >
> > ----------------------------------------------------------------
> > Error occured in index.c:901 - sis_find_segments_file
> > 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.
indeed, I have had to build a new index scratch.
> Do you
> happen to have index or dump backups or find deleted files under
> ferret/ with using undelete tools?
No :-/
> Lessons learned...
>
> Always have regular (automatic, if possible) backups of your index
> dump, ALWAYS! I have sup-dump in my backup2l before-hook.
Yes, I have a daily cron script for it now.
> 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?)
>
Thank you very much.
--
Carlos Garcia Campos
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x523E6462
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [sup-talk] Sup not working anymore after abrupt reboot
2009-11-13 9:11 [sup-talk] Sup not working anymore after abrupt reboot Carlos Garcia Campos
2009-11-13 11:10 ` Tero Tilus
@ 2009-11-13 11:57 ` Gaute Hope
1 sibling, 0 replies; 4+ messages in thread
From: Gaute Hope @ 2009-11-13 11:57 UTC (permalink / raw)
To: sup-talk
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-11-14 13:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-13 9:11 [sup-talk] Sup not working anymore after abrupt reboot Carlos Garcia Campos
2009-11-13 11:10 ` Tero Tilus
2009-11-14 13:22 ` Carlos Garcia Campos
2009-11-13 11:57 ` Gaute Hope
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox