Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of maescool@gmail.com designates
 209.85.215.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=A74MBKk79q59bb+M2s2nRMbzwCxJo+O0j0xeeCiW5JXH3m17qywukWIeyUX/t4VsNe
         7klnUYB4uAhkoSVUXOFFo6f5rH0HjBoYhPoe/X/R2nwLel1O1x3aadteCAQyyuuPxECX
         kzJdIuwC69NqfuHGHChlwDwcBMr8V8FFuxbv8=
Message-ID: <4C4CBE88.1070102@gmail.com>
Date: Mon, 26 Jul 2010 00:45:28 +0200
From: Pieter Maes <maescool@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; nl;
 rv:1.9.2.7) Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Cassandra crashes after reboot
References: <4C4C9BC9.5050807@gmail.com>
 <AANLkTimKBRv9AwnvHMX1zJLubBgWKnLBfHj43WtTsaav@mail.gmail.com>
In-Reply-To: <AANLkTimKBRv9AwnvHMX1zJLubBgWKnLBfHj43WtTsaav@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

 Hi,

I'm sorry for the lack of information
I'm using 0.6.3.
The move was moving the data dir and the commitlog dir
But i now removed them and let the system bootstrap from the ring.
i know i'm lacking in information here.. but i thought i needed to be
mentioned overhere this could happen.

Pieter Maes

Op 26/07/10 00:21, Peter Schuller schreef:
>> I've moved my cassandra to another machine, started it up again, but got
>> this error
> Which version of Cassandra exactly? (So that one can look at matching
> source code)
>
> Also, were you running the exact same version of Cassandra on both
> servers (i.e., both the "source" and the "destination")?
>
> Was the "source" node completely turned off before you began copying
> files to the "destination" node? (Though even if this were not the
> case checksumming should prevent this particular problem from
> happening, at least based on current trunk's CommitLog.)
>
> The closest thing I found by quick googling, in terms of reported
> cassandra bugs, was this:
>
>    https://issues.apache.org/jira/browse/CASSANDRA-370
>
> But presumably you're using a newer version than 0.4?
>