From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.27.4 with SMTP id a4cs94222aga; Fri, 13 Nov 2009 03:26:36 -0800 (PST) Received: by 10.224.43.102 with SMTP id v38mr2571897qae.104.1258111596464; Fri, 13 Nov 2009 03:26:36 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 2si10385214qwi.52.2009.11.13.03.26.36; Fri, 13 Nov 2009 03:26:36 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-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-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 229341858300; Fri, 13 Nov 2009 06:26:36 -0500 (EST) X-Greylist: delayed 574 seconds by postgrey-1.31 at rubyforge.org; Fri, 13 Nov 2009 06:19:52 EST Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id 8B4B11858249 for ; Fri, 13 Nov 2009 06:19:52 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id 119BD6011; Fri, 13 Nov 2009 11:10:18 +0000 (GMT) From: Tero Tilus To: sup-talk In-reply-to: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com> References: <21063fcb0911130111h234098b5oabe77bfdd14a0dab@mail.gmail.com> Date: Fri, 13 Nov 2009 13:10:17 +0200 Message-Id: <1258109288-sup-5579@tilus.net> User-Agent: Sup/git Subject: Re: [sup-talk] Sup not working anymore after abrupt reboot X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup 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-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Carlos Garcia Campos, 2009-11-13 11:11: > I don't know whether my ferret index is corrupt, this is the exception I > get: > > ---------------------------------------------------------------- > Error occured in index.c:901 - sis_find_segments_file > Error reading the segment infos. I'm not familiar with the internals of ferret, but the error looks pretty bad. It might have lost part of index data files. Do you happen to have index or dump backups or find deleted files under ferret/ with using undelete tools? Lessons learned... Always have regular (automatic, if possible) backups of your index dump, ALWAYS! I have sup-dump in my backup2l before-hook. Hum. I think for people who don't do cron backups it wouldn't be a bad idea to create (optional) rotating sup-dumps on every start. (and stop?) -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk