From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs148622ebc; Mon, 8 Feb 2010 23:20:58 -0800 (PST) Received: by 10.224.42.139 with SMTP id s11mr2958246qae.26.1265700057504; Mon, 08 Feb 2010 23:20:57 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 2si11352266qwi.25.2010.02.08.23.20.57; Mon, 08 Feb 2010 23:20:57 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 0232E3C8046; Tue, 9 Feb 2010 02:20:57 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 69BBB18582BF for ; Tue, 9 Feb 2010 02:16:35 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 959706011; Tue, 9 Feb 2010 09:16:34 +0200 (EET) From: Tero Tilus To: anonymous In-reply-to: <1265688194.03.0.035958787068.issue64@masanjin.net> References: <1265688194.03.0.035958787068.issue64@masanjin.net> Date: Tue, 09 Feb 2010 09:16:34 +0200 Message-Id: <1265699020-sup-3244@tilus.net> User-Agent: Sup/git Cc: sup-devel Subject: Re: [sup-devel] [issue64] Crash on sup start X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org 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 > 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 [+] --restored --restore where 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