From: johnbent@lanl.gov (John Bent)
Subject: [sup-talk] scary exception
Date: Sun, 26 Apr 2009 21:28:27 -0600 [thread overview]
Message-ID: <1240802707-sup-2069@tangerine.lanl.gov> (raw)
On Friday, sup stopped loading and crashed with an exception, I also
couldn't run sup-sync. At first I was a little scared, but then I
remembered that sup doesn't actually modify mail data so that I could
revert to pine, and then I got very, very scared.
I though I would have to do weird things at a ruby prompt but I just
waited two days and now it works again. Somewhat strange since I tried
about five times on Friday. Oh well, I'm running sup in screen so I'll
just never quit again. :)
Here's the error message in case there's something obvious to someone
else:
tangerine:~/mail>sup-sync
[Fri Apr 24 16:43:10 -0600 2009] using character set encoding "US-ASCII"
[Fri Apr 24 16:43:11 -0600 2009] crypto: no gpg binary detected
[Fri Apr 24 16:43:11 -0600 2009] locking /Users/johnbent/.sup/lock...
[Fri Apr 24 16:43:11 -0600 2009] loading index...
[Fri Apr 24 16:43:11 -0600 2009] loaded index of 79908 messages
Scanning mbox:/Users/johnbent/mail/mbox...
[Fri Apr 24 16:43:11 -0600 2009] unlocking /Users/johnbent/.sup/lock...
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:768:in
`search': IO Error occured at <except.c>:93 in xraise (IOError)
Error occured in fs_store.c:284 - fsi_read_i
couldn't read 1024 chars from : <Unknown error: 0>
from
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:768:in
`do_search'
from
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:339:in
`search'
from /opt/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
from
/opt/local/lib/ruby/gems/1.8/gems/ferret-0.11.6/lib/ferret/index.rb:338:in
`search'
from
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:422:in
`load_entry_for_id'
from /opt/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
from
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/index.rb:421:in
`load_entry_for_id'
from
/opt/local/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in `send'
... 10 levels...
from /opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:131:in
`each'
from /opt/local/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:131
from /opt/local/bin/sup-sync:16:in `load'
from /opt/local/bin/sup-sync:16
Thanks,
JOHn
next reply other threads:[~2009-04-27 3:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 3:28 John Bent [this message]
2009-04-27 17:25 ` William Morgan
2009-04-27 17:34 ` John Bent
2009-04-27 17:46 ` William Morgan
2009-05-24 5:54 ` John Bent
2009-05-27 16:03 ` William Morgan
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=1240802707-sup-2069@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
/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