From: Tero Tilus <tero@tilus.net>
To: anonymous <sup-bugs@masanjin.net>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [issue64] Crash on sup start
Date: Tue, 09 Feb 2010 09:16:34 +0200 [thread overview]
Message-ID: <1265699020-sup-3244@tilus.net> (raw)
In-Reply-To: <1265688194.03.0.035958787068.issue64@masanjin.net>
anonymous, 2010-02-09 06:03:
> sup crashed after I sent an email, and won't start anymore.
I expect the exception log is the failing start? Index seems to be in
inconsistent state.
Could you describe in more detail how exactly sup crashed after
sending mail. When exactly it crashed? What did it say?
You can try to get back on your feet by recreating your index. Try
creating sup-dump (back up index) first so that you can preserve
labels. If that doesn't work, you unfortunately can't preserve your
message states. But don't throw your old index away just yet, before
sup-sync do cd ~/.sup/; mv xapian xapian.bak . We might find another
way to recover.
Quoting from http://sup.rubyforge.org/FAQ.txt
Q: How do I back up my index?
A: Since the contents of the messages are recoverable from their
sources using sup-sync, all you need to back up is the message
state. To do this, simply run:
sup-dump > <dumpfile>
This will save all message state in a big text file, which you
should probably compress.
Q: How do I restore the message state I saved in my state dump?
A: Run:
sup-sync [<source>+] --restored --restore <dumpfile>
where <dumpfile> was created as above.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-02-09 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 4:03 anonymous
2010-02-09 7:16 ` Tero Tilus [this message]
2010-02-09 7:41 ` Tero Tilus
2010-08-24 21:21 ` Gaute Hope
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=1265699020-sup-3244@tilus.net \
--to=tero@tilus.net \
--cc=sup-bugs@masanjin.net \
--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