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 duncan.sands@gmail.com
 designates 74.125.82.169 as permitted sender)
Message-ID: <531DBF5E.9060200@gmail.com>
Date: Mon, 10 Mar 2014 14:34:22 +0100
From: Duncan Sands <duncan.sands@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Cassandra DSC 2.0.5 not starting - "* could not access pidfile
 for Cassandra"
References: 
 <CAFaNLCbjaPuz8B584HFYwFu1KxEtxA244STcJVui9W9Ks9UbqQ@mail.gmail.com>
In-Reply-To: 
 <CAFaNLCbjaPuz8B584HFYwFu1KxEtxA244STcJVui9W9Ks9UbqQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi user 01,

On 10/03/14 13:11, user 01 wrote:
> I installed DSC 2.0.5 on ubuntu 12.04 with Oracle JRE 7 but dsc 2.0.5 does not
> start after installation. When I check the running status..
>
>     *$ sudo service cassandra status*
>
>
> it says
>
>     ** could not access pidfile for Cassandra*
>
>
> & no other messages or anything in logs.
>
> This is happening with 2.0.5 but not with 2.0.4.
>
> Did anyone else came across this issue ? Any idea how to fix this ?

this probably means that the Cassandra process exited.  For example, if there is 
an incorrect value in cassandra.yaml then the process will start (so "sudo 
service cassandra start" will return a success code), but will then exit once it 
discovers the wrong value.  I suggest you start Cassandra in the foreground 
(with -f IIRC), so you get all error output directly on your console.

Ciao, Duncan.


>
>
>
>
>