From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.125.10 with SMTP id x10cs233356wfc; Tue, 14 Jun 2011 01:38:36 -0700 (PDT) Received: by 10.224.211.74 with SMTP id gn10mr4941980qab.288.1308040715143; Tue, 14 Jun 2011 01:38:35 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id h3si9957810qac.54.2011.06.14.01.38.34; Tue, 14 Jun 2011 01:38:35 -0700 (PDT) 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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id BA2FA1678328 for ; Tue, 14 Jun 2011 04:38:34 -0400 (EDT) Received: from mail-vw0-f50.google.com (mail-vw0-f50.google.com [209.85.212.50]) by rubyforge.org (Postfix) with ESMTP id 112391858367 for ; Tue, 14 Jun 2011 04:36:03 -0400 (EDT) Received: by vws14 with SMTP id 14so5720461vws.23 for ; Tue, 14 Jun 2011 01:36:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=BkxR0w7+IDLMKr5E1Mfogmd32FhNRyPTt5Cuoa6Y6fY=; b=pAJHg6YsZDcdoLc37LCVXk57CtvgEgPPyTrpHnn4Gjvhjft09G1oMSxFmApr+qyB5W 7J32aqbeasJU3pHxn0oj5qfTBAN8otk8baAlEGAGgMQlnmY6ABw2ejuHtJDnzdge8VMt 2t1zUmV5D2ru7qHmYKs724z1X7jJGPIcDwlGU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=WaA2pDc7Zkaln4XexEyucakhBYNyc1JKE3qGhy6GZDDzPFLG8RSToElIPN4ruIbomK 22HM5wP2CvzCL2BN+mowr8CIL8sqQUicq042xLw+ZjkSSrVVn6bTSDHhWqJSzPhiQkB+ IxQo8tRI7y+tB5eMraXdPki+lL08kmw9I6Rps= MIME-Version: 1.0 Received: by 10.52.0.228 with SMTP id 4mr1535145vdh.107.1308040562894; Tue, 14 Jun 2011 01:36:02 -0700 (PDT) Received: by 10.52.184.225 with HTTP; Tue, 14 Jun 2011 01:36:02 -0700 (PDT) Date: Tue, 14 Jun 2011 17:36:02 +0900 Message-ID: From: Horacio Sanson To: Sup developer discussion Subject: [sup-devel] Tokyo Cabinet fails with invalid record header 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Well I will retract what I said earlier... maybe is a good idea to replace TokyoCabinet with something else. Now the store.tch got corrupted again for some reason and the only error I get is "invalid record header". Some googling does not help and my previous fix (tchmgr optimiza -nl) does not fix this problem. What is interesting is that the store.tch file is at 76MB now that is exactly the same size it had when the previous corruption occured. =========== error ============ ; found 496204 new messages... ; found 496204 messages to scan ; requesting messages 79228..79327 from imap server /var/lib/gems/1.9.1/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/hash_database.rb:337:in `try': invalid record header (error code 6) (OklahomaMixer::Error::CabinetError) from /var/lib/gems/1.9.1/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/hash_database.rb:142:in `fetch' from /var/lib/gems/1.9.1/gems/oklahoma_mixer-0.4.0/lib/oklahoma_mixer/hash_database.rb:205:in `include?' from /media/DATA/Apps/heliotrope/lib/heliotrope/index.rb:633:in `contains_key?' from /media/DATA/Apps/heliotrope/lib/heliotrope/index.rb:165:in `contains_msgid?' from bin/heliotrope-add:139:in `
' regards, Horacio _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel