From: Jonathan Lassoff <jof@thejof.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] sup Xapian crash
Date: Wed, 2 Jan 2013 12:26:15 -0800 [thread overview]
Message-ID: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com> (raw)
I'm having a sad day with sup. I'm crashing with a Xapian error I'll
have to dig into.
The exception is this:
--- IOError from thread: poll after loading inbox
DatabaseCorruptError: Expected another key with the same term name but
found a different one
/usr/lib/ruby/1.8/sup/index.rb:293:in `_dangerous_allterms_begin'
/usr/lib/ruby/1.8/sup/index.rb:293:in `each_prefixed_term'
/usr/lib/ruby/1.8/sup/index.rb:306:in `each_source_info'
/usr/lib/ruby/1.8/sup/maildir.rb:98:in `each'
/usr/lib/ruby/1.8/sup/maildir.rb:98:in `to_a'
/usr/lib/ruby/1.8/sup/maildir.rb:98:in `poll'
/usr/lib/ruby/1.8/sup/util.rb:229:in `call'
/usr/lib/ruby/1.8/sup/util.rb:229:in `benchmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/sup/util.rb:229:in `benchmark'
/usr/lib/ruby/1.8/sup/maildir.rb:98:in `poll'
/usr/lib/ruby/1.8/sup/maildir.rb:90:in `each'
/usr/lib/ruby/1.8/sup/maildir.rb:90:in `poll'
/usr/lib/ruby/1.8/sup/poll.rb:155:in `poll_from'
/usr/lib/ruby/1.8/sup/poll.rb:113:in `do_poll'
/usr/lib/ruby/1.8/sup/poll.rb:103:in `each'
/usr/lib/ruby/1.8/sup/poll.rb:103:in `do_poll'
/usr/lib/ruby/1.8/sup/poll.rb:102:in `synchronize'
/usr/lib/ruby/1.8/sup/poll.rb:102:in `do_poll'
/usr/lib/ruby/1.8/sup/util.rb:572:in `send'
/usr/lib/ruby/1.8/sup/util.rb:572:in `method_missing'
/usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll'
/usr/lib/ruby/1.8/sup/poll.rb:49:in `poll_with_sources'
/usr/lib/ruby/1.8/sup/poll.rb:68:in `poll'
/usr/lib/ruby/1.8/sup/util.rb:572:in `send'
/usr/lib/ruby/1.8/sup/util.rb:572:in `method_missing'
/usr/bin/sup-mail:223
/usr/lib/ruby/1.8/sup.rb:79:in `reporting_thread'
/usr/lib/ruby/1.8/sup.rb:77:in `initialize'
/usr/lib/ruby/1.8/sup.rb:77:in `new'
/usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread'
/usr/bin/sup-mail:223
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:699:in `call'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:699:in
`__unprotected_load_threads'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in `call'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in
`load_n_threads_background'
/usr/lib/ruby/1.8/sup.rb:79:in `reporting_thread'
/usr/lib/ruby/1.8/sup.rb:77:in `initialize'
/usr/lib/ruby/1.8/sup.rb:77:in `new'
/usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:638:in
`load_n_threads_background'
/usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:709:in
`__unprotected_load_threads'
(eval):12:in `load_threads'
/usr/bin/sup-mail:223
I can start sup, but it seems like it goes to add a new message from
pickup and crashes. Maybe something about the new message could be
causing this.
Anyone run into this before or have any ideas where I should start hacking away?
Cheers,
jof
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2013-01-02 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 20:26 Jonathan Lassoff [this message]
2013-01-02 21:33 ` Mark Alexander
2013-01-02 23:20 ` Jonathan Lassoff
2013-01-03 23:04 ` Mark Alexander
2013-01-04 9:49 ` Jim Cheetham
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='CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com' \
--to=jof@thejof.com \
--cc=sup-talk@rubyforge.org \
/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