From: Gregor Hoffleit <gregor@hoffleit.de>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup 0.14: Encoding::UndefinedConversionError from thread: load threads for thread-index-mode
Date: Fri, 16 Aug 2013 17:15:17 +0200 [thread overview]
Message-ID: <1376658893-sup-8054@sam.mediasupervision.de> (raw)
In-Reply-To: <1376584400-sup-6242@qwerzila>
* Gaute Hope <eg@gaute.vetsj.com> [2013-08-15 18:39:45 +0200]
> did you have a lot of messages in your index added by Sup 0.13 or
> earlier? Do you get the same error if you move the old xapian folder out
> of the way and try to re-index your messages?
>
> It is possible to restore labels using sup-dump and sup-sync --restore.
Thanks for this explanation.
Yes, I was running with an index created with Sup < 0.13, and it's
pretty clear to me now that this was the cause of this crash.
Well, I moved away the old xapian folder and called sup-sync --restore,
but this crashed after ten minutes and 10.000 messages (of 500.000).
I just filled an issue #131 to github about this crash.
Gregor
prev parent reply other threads:[~2013-08-16 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 16:21 Gregor Hoffleit
2013-08-15 16:39 ` Gaute Hope
2013-08-15 16:49 ` Gaute Hope
2013-08-16 13:13 ` Gregor Hoffleit
2013-08-16 15:15 ` Gregor Hoffleit [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=1376658893-sup-8054@sam.mediasupervision.de \
--to=gregor@hoffleit.de \
--cc=eg@gaute.vetsj.com \
--cc=sup-devel@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