Problem solved.

Just for the record:

I now know that the inability to start due to out of memory was red herring.

It was most probably me upgrading my Ubuntu Desktop 13, and this somehow wrecked the permissions, there is a slight possibility it is the C* 1.2.5 upgrade (I just cannot correlate the sequence of events now). But yes, copying the missing config files helped me to pinpoint the permission issue - thank you Faraaz! Once the logging started I was able to see the inability to access the data directories.

I guess lesson learnt is in next time not using packages.

More specifics and where I found the correct fix is https://issues.apache.org/jira/browse/CASSANDRA-4058#comment-13662604


Regards,

Arthur



---- Original Message ----
From: Arthur Zubarev <arthur.zubarev@aol.com>
To: user <user@cassandra.apache.org>
Sent: Mon, May 20, 2013 9:46 pm
Subject: Re: Unable to start Cassandra

Copied the contents of the Conf directory to /etc/cassandra and now I am back to square one, it can't start due to:

HeapDumpOnOutOfMemoryError -Xss180k

in full the error is:

sudo service cassandra start
xss =  -ea -javaagent:/usr/share/cassandra/lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1841M -Xmx1841M -Xmn400M -XX:+HeapDumpOnOutOfMemoryError -Xss180k


Regards,

Arthur



---- Original Message ----
From: Arthur Zubarev <arthur.zubarev@aol.com>
To: user <user@cassandra.apache.org>
Sent: Mon, May 20, 2013 4:37 pm
Subject: Re: Unable to start Cassandra

I have no such evidence:

Start-Date: 2013-05-20  11:48:17
Commandline: apt-get install cassandra
Install: libjna-java:amd64 (3.2.7-4, automatic), jsvc:amd64 (1.0.10-3, automatic), libopts25:amd64 (5.17.1-1ubuntu2, automatic), java-common:amd64 (0.43ubuntu4, automatic), icedtea-6-jre-cacao:amd64 (6b27-1.12.5-1ubuntu1, automatic), openjdk-6-jre-lib:amd64 (6b27-1.12.5-1ubuntu1, automatic), openjdk-6-jre-headless:amd64 (6b27-1.12.5-1ubuntu1, automatic), icedtea-6-jre-jamvm:amd64 (6b27-1.12.5-1ubuntu1, automatic), tzdata-java:amd64 (2013b-1ubuntu1, automatic), cassandra:amd64 (1.2.5), ntp:amd64 (4.2.6.p5+dfsg-2ubuntu1, automatic), libcommons-daemon-java:amd64 (1.0.10-3, automatic), python-support:amd64 (1.0.15, automatic), ca-certificates-java:amd64 (20121112+nmu2, automatic)
End-Date: 2013-05-20  11:48:41

I have two Java distros - one OpenJava and another Oracle 1.7, I did not set #CASSANDRA_HOME env. var, may this helps.

Regards,

Arthur



---- Original Message ----
From: Faraaz Sareshwala <fsareshwala@quantcast.com>
To: user <user@cassandra.apache.org>
Sent: Mon, May 20, 2013 4:30 pm
Subject: Re: Unable to start Cassandra

There are no files in /etc/cassandra even though the package claims to have put
some there and own them? Hm... that's weird -- try looking in the dpkg logs to
find out if they were somehow removed. You might try reinstalling the package to
have it reinstall the files.

Faraaz

On Mon, May 20, 2013 at 01:15:05PM -0700, Arthur Zubarev wrote:
> Hi Faraaz,
> 
> yes, this time C* doesn't start due to inability to log I assume.
> 
> I get ii  cassandra  1.2.5 out of the 1st statement, the 2nd gave
> /usr/share/doc/cassandra/licenses/slf4j-log4j12-1.6.1.txt
> /usr/share/doc/cassandra/licenses/log4j-1.2.16.txt.gz
> /usr/share/cassandra/lib/log4j-1.2.16.jar
> /usr/share/cassandra/lib/slf4j-log4j12-1.7.2.jar
> /etc/cassandra/log4j-tools.properties
> /etc/cassandra/log4j-server.properties
> 
> There are no files in /etc/cassandra
> 
> 
> Regards,
> 
> Arthur
> 
> 
> 
> ---- Original Message ----
> From: Faraaz Sareshwala <fsareshwala@quantcast.com>
> To: user <user@cassandra.apache.org>
> Sent: Mon, May 20, 2013 3:09 pm
> Subject: Re: Unable to start Cassandra
> 
> 
> The logs don't seem to be talking about memory issues -- it can't find the 
log4j
> settings file in the correct location under where the CASSANDRA_HOME 
environment
> variable points to.
> 
> I have packaged cassandra myself so I'm not entirely familiar with the
> pre-packaged installations. Try doing the following (assuming a debian system
> because you mentioned ubuntu):
> 
> dpkg -l | grep cassandra # then find the package you want to look into
> dpkg -L cassandra_package | grep log4j
> 
> One of them should have the log4j configuration in it, I presume?
> 
> Faraaz
> 
> On Mon, May 20, 2013 at 09:17:11AM -0700, Arthur Zubarev wrote:
> >
> >
> > Hello All:
> >
> > I had Cassandra 1.2.4 running up until yesterday, then after I took an 
Ubuntu
> > update (may be related or may not), I suddenly wasn't able to connect any
> more.
> >
> > The error was related to lack of memory and suggested a modification to its
> > config, I kept increasing the memory (I have 8 Gb), but Cassandra would not
> > start.
> > I read a post that it might be OpenJava related and I added Oracle Java
> > 1.7.0_21, made it default, but the issue persisted.
> >
> > I have then decided to remove the Cassandra community package and get the
> > DataStax one. Alas, it failed to install citing unmet dependency 1.2.4 C*
> > package. I could not figure how I get it since the only valid option was
> deb12.
> >
> > I thus opted to re-get the one from Apache, made it installed no problem, 
but
> > to my dismay C* would NOT start!
> >
> > I can see the error when running sudo cassandra -f is
> >
> > Exception in thread "main" java.lang.ExceptionInInitializerError
> > Caused by: java.lang.RuntimeException: Couldn't figure out log4j
> configuration:
> > log4j-server.properties
> >     at org.apache.cassandra.service.CassandraDaemon.initLog4j
> > (CassandraDaemon.java:82)
> >     at org.apache.cassandra.service.CassandraDaemon.<clinit>
> > (CassandraDaemon.java:58)
> >
> > The posts I found tell me to modify the log4j-server.properties file.
> > But it is not present on my machine, in fact the directory
> > /etc/cassandra is empty.
> >
> > I am out of ideas. What is wrong?
> >
> > Regards,
> >
> > Arthur
>