From: Rich Lane <rlane@club.cc.cmu.edu>
To: Guillaume Quintard <guillaume.quintard@gmail.com>
Cc: "Sup-talk@rubyforge.org" <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Crash, bad index, and ensuing misery
Date: Sat, 03 Oct 2009 18:25:19 -0400 [thread overview]
Message-ID: <1254607735-sup-864@zyrg.net> (raw)
In-Reply-To: <1e5fdab70910031304g255a9d13v4dc99400def375a5@mail.gmail.com>
Excerpts from Guillaume Quintard's message of Sat Oct 03 16:04:14 -0400 2009:
> --- RuntimeError from thread: load threads for thread-index-mode
> DocNotFoundError: Document 2461178145 not found.
> ./lib/sup/xapian_index.rb:132:in `document'
The relevant line:
docs = term_docids(mkterm(:thread, thread_id)).map { |x| @xapian.document x }
Basically expands to:
@xapian.postlist(term).map { |x| @xapian.document x.docid }
So, Xapian is giving us docids it can't turn into documents. At this
point I think you should just do a sup-dump (which might still work),
move the old xapian directory out of the way, and re-sync. You can try
running xapian-check on the corrupted version to see if it finds
anything interesting.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-10-03 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 20:04 Guillaume Quintard
2009-10-03 20:17 ` Rich Lane
2009-10-03 21:06 ` Guillaume Quintard
2009-10-03 21:39 ` Rich Lane
2009-10-03 21:54 ` Guillaume Quintard
2009-10-06 12:40 ` Olly Betts
2009-10-06 13:10 ` Guillaume Quintard
2009-10-03 22:25 ` Rich Lane [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=1254607735-sup-864@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=guillaume.quintard@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