From: kapil.foss@gmail.com
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup: RangeError: value in posting list too large.
Date: Tue, 26 Apr 2011 16:11:24 -0400 [thread overview]
Message-ID: <1303848484-sup-3536@objectrealms.net> (raw)
In-Reply-To: <AANLkTimkgq4jiZJpPZpG2VM1RNgZck0e-RjRQSBOpLOA@mail.gmail.com>
Looks like an error from xapian, perhaps an old version of xapian?
http://lists.xapian.org/pipermail/xapian-tickets/2010-March/001552.html
cheers,
Kapil
Excerpts from Shadowfirebird's message of Fri Mar 18 05:50:45 -0400 2011:
> Got the above error while Sup was flushing indexes after an initial message
> polling on start. Ubuntu 9.04.
>
> Sup restarted okay afterwards, but it just crashes in the same way.
>
> Any ideas?
>
> --- IndexError from thread: poll after loading inbox
> RangeError: Value in posting list too large.
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/index.rb:272:in `_dangerous_allterms_begin'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/index.rb:272:in `each_prefixed_term'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/index.rb:285:in `each_source_info'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/maildir.rb:97:in `each'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/maildir.rb:97:in `to_a'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/maildir.rb:97:in `poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:204:in `call'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:204:in `benchmark'
> /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:204:in `benchmark'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/maildir.rb:97:in `poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/maildir.rb:89:in `each'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/maildir.rb:89:in `poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:154:in `poll_from'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:113:in `do_poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:103:in `each'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:103:in `do_poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:102:in `synchronize'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:102:in `do_poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:609:in `send'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:609:in `method_missing'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/poll-mode.rb:15:in `poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:49:in `poll_with_sources'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/poll.rb:68:in `poll'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:609:in `send'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/util.rb:609:in `method_missing'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/bin/sup:212
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:78:in `reporting_thread'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:76:in `initialize'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:76:in `new'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:76:in `reporting_thread'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/bin/sup:212
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/thread-index-mode.rb:684:in `call'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/thread-index-mode.rb:684:in `__unprotected_load_threads'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/thread-index-mode.rb:625:in `call'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/thread-index-mode.rb:625:in `load_n_threads_background'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:78:in `reporting_thread'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:76:in `initialize'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:76:in `new'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup.rb:76:in `reporting_thread'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/thread-index-mode.rb:623:in `load_n_threads_background'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/modes/thread-index-mode.rb:694:in `__unprotected_load_threads'
> (eval):12:in `load_threads'
> /usr/lib/ruby/gems/1.8/gems/sup-0.12/bin/sup:212
> /usr/bin/sup:19:in `load'
> /usr/bin/sup:19
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2011-04-26 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 9:50 Shadowfirebird
2011-04-26 20:11 ` kapil.foss [this message]
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=1303848484-sup-3536@objectrealms.net \
--to=kapil.foss@gmail.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