Re: [sup-devel] [issue64] Crash on sup start

[Tero Tilus <tero@tilus.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