incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Liangzhao Zeng <>
Subject Re: unable to start cassandra-0.7r2
Date Mon, 13 Dec 2010 22:01:49 GMT
log4j:WARN No appenders could be found for logger

log4j:WARN Please initialize the log4j system properly.

log4j:WARN See for
more info.

Bad configuration; unable to start server

That is the error msg.

The I used is

   # Licensed to the Apache Software Foundation (ASF) under one

# or more contributor license agreements.  See the NOTICE file

# distributed with this work for additional information

# regarding copyright ownership.  The ASF licenses this file

# to you under the Apache License, Version 2.0 (the

# "License"); you may not use this file except in compliance

# with the License.  You may obtain a copy of the License at




# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS,


# See the License for the specific language governing permissions and

# limitations under the License.


# output messages into a rolling log file as well as stdout

log4j.rootLogger=DEBUG, R, INFO, FINEST







# rolling log file ("system.log




log4j.appender.R.layout.ConversionPattern=%5p [%t] %d{ISO8601} %F (line %L)


# Specify the handlers to create in the root logger

# (all loggers are children of the root logger)

# The following creates two handlers

handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler

# Set the default logging level for the root logger

.level = ALL

# Set the default logging level for new ConsoleHandler instances

java.util.logging.ConsoleHandler.level = ALL

# Set the default logging level for new FileHandler instances

java.util.logging.FileHandler.level = ALL

# Set the default formatter for new ConsoleHandler instances

java.util.logging.ConsoleHandler.formatter =


On Mon, Dec 13, 2010 at 2:23 PM, Aaron Morton <>wrote:

> Can you provide the full log messages so we can see where they are logged
> from and if there are any other messages as well.
> It's probably a problem finding the config file or an invalid config file.
> Aaron
> On 14/12/2010, at 4:02 AM, Liangzhao Zeng <>
> wrote:
> I use VM argument to specify the configuration file
> -Dstorage-config=/Users/zlzhao/Documents/eclipse/MaaSWorkspace/cassandra-0.7r2/test/conf/
> -Dcassandra-foreground  -ea -Xmx1G
> By the way, I can run the 0.66 using by following the wikipage. Do we need
> more configuration in order to run 0.7?
> Cheers,
> Liangzhao
> On Mon, Dec 13, 2010 at 6:02 AM, shimi < <>
>> wrote:
>> I have seen this error in 0.6.x when I was missing the cash directory
>> configuration.
>> Maybe you are missing something in your configuration.
>> Shimi
>> On Mon, Dec 13, 2010 at 12:45 PM, aaron morton <<>
>>> wrote:
>>> I've seen that before when cassandra.yaml file cannot be found or is
>>> corrupted. It may be that eclipse is not starting cassandra with the current
>>> working directory set as you think it is. Sorry, cannot help much with
>>> eclipse.
>>> There are a couple of places where that message can be logged. One is
>>> from the AbstractCassandraDaemon and the other is from the
>>> DatabaseDescriptor. Where is your's coming from?
>>> Aaron
>>> On 13 Dec 2010, at 19:22, Liangzhao Zeng wrote:
>>> Bad configuration; unable to start server. Any idea

View raw message