Subject: [sup-talk] sup dying with another ferret error

From: [email-masked] (jeff covey)
Date: Sat, 30 Jun 2007 05:29:07 -0400

i just started sup this morning, and it died as it was polling for new
messages.  now it does this whenever i try to start it:

[Sat Jun 30 05:10:24 -0400 2007] oh crap, an exception
[Sat Jun 30 05:10:24 -0400 2007] unlocking /home/jeff/.sup/lock...
----------------------------------------------------------------
I'm very sorry, but it seems that an error occurred in Sup.
Please accept my sincere apologies. If you don't mind, please
send the backtrace below 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
----------------------------------------------------------------

The problem was: '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

' (error type IOError)
A backtrace follows:
/var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `initialize': IO Error occured at <except.c>:93 in xraise (IOError)
Error occured in index.c:901 - sis_find_segments_file
        Error reading the segment infos. Store listing was

        from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `new'
        from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `ensure_reader_open'
        from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:733:in `ensure_searcher_open'
        from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:755:in `do_search'
        from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:334:in `search'
        from /usr/lib/ruby/1.8/monitor.rb:238:in `synchronize'
        from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:333:in `search'
        from ./lib/sup/index.rb:312:in `load_entry_for_id'
         ... 33 levels...
        from ./lib/sup.rb:66:in `reporting_thread'
        from ./lib/sup/modes/thread-index-mode.rb:343:in `load_n_threads_background'
        from ./lib/sup/modes/thread-index-mode.rb:393:in `load_threads'
        from bin/sup:171

thanks,

-- 
jeff covey
http://jeffcovey.net/

---

From: [email-masked] (William Morgan)
Date: Sat, 07 Jul 2007 06:17:23 -0700

> Error occured in index.c:901 - sis_find_segments_file

Do you have a really large index? Like, 4G?

-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (jeff covey)
Date: Sat, 07 Jul 2007 22:32:10 -0400

> Do you have a really large index? Like, 4G?

no, not very big:

$ du -hs ~/.sup/ferret/

14M	/home/jeff/.sup/ferret/

thanks,

-- 

jeff covey

http://jeffcovey.net/

---

From: [email-masked] (jeff covey)
Date: Sat, 07 Jul 2007 22:59:59 -0400

all of the messages i've sent with sup since the latest svn updates seem to

be including a lot of extra blank lines.  for example:

-- 

jeff covey

http://jeffcovey.net/

---

From: [email-masked] (William Morgan)
Date: Sun, 08 Jul 2007 08:14:45 -0700

Excerpts from jeff.covey's message of Sat Jul 07 19:59:59 -0700 2007:
> all of the messages i've sent with sup since the latest svn updates
> seem to be including a lot of extra blank lines.

If these two lines are together,
this problem should be fixed.

---

From: [email-masked] (jeff covey)
Date: Sun, 08 Jul 2007 14:59:51 -0400

> this problem should be fixed.

looks good to me!

-- 
jeff covey
http://jeffcovey.net/