From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.142.217.3 with SMTP id p3cs49124wfg; Sun, 17 Jul 2011 13:54:11 -0700 (PDT) Received: by 10.52.31.1 with SMTP id w1mr5560321vdh.371.1310936050391; Sun, 17 Jul 2011 13:54:10 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id bz9si4696732vdc.138.2011.07.17.13.54.09; Sun, 17 Jul 2011 13:54:09 -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 Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id E35AA18583A5; Sun, 17 Jul 2011 16:54:08 -0400 (EDT) Received: from masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id A51821858367 for ; Sun, 17 Jul 2011 15:53:54 -0400 (EDT) Received: from w by masanjin.net with local (Exim 4.71) (envelope-from ) id 1QiXai-0001mG-LK for sup-devel@rubyforge.org; Sun, 17 Jul 2011 20:05:28 +0000 From: William Morgan To: sup-devel In-reply-to: References: Date: Sun, 17 Jul 2011 20:05:27 +0000 Message-Id: <1310933008-sup-9080@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-devel] error after leveldb-ruby upgrade 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 Reformatted excerpts from Hamish D's message of 2011-07-17: > $ heliotrope-server -d ~/.heliotrope > /var/lib/gems/1.9.1/gems/leveldb-ruby-0.7/lib/leveldb.rb:11:in `make': > Corruption: checksum mismatch (LevelDB::Error) That error gets thrown when LevelDB detects things are corrupted, but I'd be surprised if the upgrade to 0.7 caused this--the only change was one in how memory in the Ruby world is free'd. None of the actual LevelDB code changed. If you downgrade to 0.6, do you still get that error? Are you running out of disk space, or anything like that? -- William _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel