Subject: [sup-talk] Can't even run sup anymore

From: [email-masked] (Guillaume Quintard)
Date: Sat, 21 Jun 2008 15:05:58 -0700

Here's the trace:

shivan at altis:~/sup$ sup
[Sat Jun 21 15:05:12 -0700 2008] using character set encoding "UTF-8"
[Sat Jun 21 15:05:12 -0700 2008] locking /home/shivan/.sup/lock...
[Sat Jun 21 15:05:12 -0700 2008] crypto: detected gpg binary in /usr/bin/gpg
[Sat Jun 21 15:05:12 -0700 2008] loading index...
[Sat Jun 21 15:05:12 -0700 2008] stopped cursing
[Sat Jun 21 15:05:12 -0700 2008] oh crap, an exception
[Sat Jun 21 15:05:12 -0700 2008] unlocking /home/shivan/.sup/lock...
----------------------------------------------------------------
I'm very sorry. It seems that an error occurred in Sup. Please
accept my sincere apologies. If you don't mind, please send the
contents of ~/.sup/exception-log.txt and a brief report of the
circumstances to sup-talk at rubyforge dot orgs so that I might
address this problem. Thank you!

Sincerely,
William
----------------------------------------------------------------
--- 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

/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:736:in `initialize'
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:736:in `new'
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:736:in
`ensure_reader_open'
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:591:in `size'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/var/lib/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:590:in `size'
./lib/sup/index.rb:140:in `load_index'
./lib/sup/index.rb:109:in `load'
./lib/sup/util.rb:499:in `send'
./lib/sup/util.rb:499:in `method_missing'
bin/sup:122

-- 
Guillaume

---

From: [email-masked] (William Morgan)
Date: Sat, 21 Jun 2008 19:36:18 -0700

>     Error reading the segment infos. Store listing was

This is the classic Sup+ferret error. No one really knows what the heck
is going on, although there's a guess it has to do with open files:
  http://ferret.davebalmain.com/trac/ticket/279

I've had success before with sup-sync --optimize. You can try that.
Otherwise, it's rebuild the index and bug Dave Balmain...

I am working on something where flags are backed up to a BDB store on
disk, which is yet more disk space consumed by Su, but at least means
that if Ferret barfs you don't lose all your message flags. Of course,
that doesn't help you right now.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Guillaume Quintard)
Date: Sun, 22 Jun 2008 11:16:19 -0700

On Sat, Jun 21, 2008 at 7:36 PM, William Morgan
> that doesn't help you right now.

grrrrr, bad ferret, bad.

Thank you.

-- 
Guillaume