From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] sup dying with another ferret error
Date: Sat, 30 Jun 2007 05:29:07 -0400 [thread overview]
Message-ID: <20070630092906.GA16008@mona.jeffcovey.net> (raw)
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/
next reply other threads:[~2007-06-30 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-30 9:29 jeff covey [this message]
2007-07-07 13:17 ` William Morgan
2007-07-08 2:32 ` jeff covey
2007-07-08 2:59 ` [sup-talk] extra blank lines jeff covey
2007-07-08 15:14 ` William Morgan
2007-07-08 18:59 ` jeff covey
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=20070630092906.GA16008@mona.jeffcovey.net \
--to=jeff.covey@pobox.com \
/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