You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Liangzhao Zeng <li...@gmail.com> on 2010/12/13 07:22:06 UTC
unable to start cassandra-0.7r2
I am trying to run cassandra-0.7r2 in eclipse by following
http://wiki.apache.org/cassandra/RunningCassandraInEclipse. there is
not compiling errors however, got error message: Bad configuration; unable
to start server. Any idea?
Liangzhao
Re: unable to start cassandra-0.7r2
Posted by Edward Capriolo <ed...@gmail.com>.
On Mon, Dec 13, 2010 at 5:45 PM, Eric Evans <ee...@rackspace.com> wrote:
> On Mon, 2010-12-13 at 17:27 -0500, Liangzhao Zeng wrote:
>> I can run the 0.66 using same logging setup without any problem. Not
>> sure what's the difference when starting up the 0.7 in eclipse. Can
>> someone share the logging setup?
>
> Make sure that you have -Dlog4j.configuration=log4j-server.properties
> among your VM arguments and that conf/ (assuming that's where you have
> it) has been added to the classpath. Since you say this worked with
> 0.6.6 and doesn't with 0.7, I'm guessing the latter is already in place
> and the former is the problem.
>
> --
> Eric Evans
> eevans@rackspace.com
>
>
I am not sure about the logging but cassandra.config should now be a
URI to your cassandra.yaml not your storage-dir. Mine looks like this.
-Dcom.sun.management.jmxremote.port=8888
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcassandra-foreground
-Dcassandra.config=file:///home/edward/idea/conf/cassandra.yaml -ea
-Xmx1G
Re: unable to start cassandra-0.7r2
Posted by Eric Evans <ee...@rackspace.com>.
On Mon, 2010-12-13 at 17:27 -0500, Liangzhao Zeng wrote:
> I can run the 0.66 using same logging setup without any problem. Not
> sure what's the difference when starting up the 0.7 in eclipse. Can
> someone share the logging setup?
Make sure that you have -Dlog4j.configuration=log4j-server.properties
among your VM arguments and that conf/ (assuming that's where you have
it) has been added to the classpath. Since you say this worked with
0.6.6 and doesn't with 0.7, I'm guessing the latter is already in place
and the former is the problem.
--
Eric Evans
eevans@rackspace.com
Re: unable to start cassandra-0.7r2
Posted by Liangzhao Zeng <li...@gmail.com>.
I can run the 0.66 using same logging setup without any problem. Not sure
what's the difference when starting up the 0.7 in eclipse. Can someone share
the logging setup?
Cheers,
Liangzhao
On Mon, Dec 13, 2010 at 5:12 PM, Aaron Morton <aa...@thelastpickle.com>wrote:
> Given that log4j could not find it's configuration file I'm guessing it's a
> problem with the current working directory when eclipse starts cassandra.
>
> Can you start cassandra manually from where you have the source code?
>
> I do not use eclipse so may not be much more help.
>
> Aaron
>
>
> On 14 Dec, 2010,at 11:01 AM, Liangzhao Zeng <li...@gmail.com>
> wrote:
>
> log4j:WARN No appenders could be found for logger
> (org.apache.cassandra.service.AbstractCassandraDaemon).
>
> log4j:WARN Please initialize the log4j system properly.
>
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
> more info.
>
> Bad configuration; unable to start server
>
>
> That is the error msg.
>
>
> The log4j-server.properties 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
>
> #
>
> # http://www.apache.org/licenses/LICENSE-2.0
>
> #
>
> # Unless required by applicable law or agreed to in writing, software
>
> # distributed under the License is distributed on an "AS IS" BASIS,
>
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>
> # See the License for the specific language governing permissions and
>
> # limitations under the License.
>
>
>
> #log4j.rootLogger=DEBUG,R
>
>
> # output messages into a rolling log file as well as stdout
>
> log4j.rootLogger=DEBUG, R, INFO, FINEST
>
>
> log4j.appender.DEBUG=org.apache.log4j.ConsoleAppender
>
> log4j.appender.DEBUG.layout=org.apache.log4j.SimpleLayout
>
>
>
> log4j.appender.FINEST=org.apache.log4j.ConsoleAppender
>
> log4jappender.FINEST.layout=org.apache.log4j.SimpleLayout
>
>
> log4j.appender.INFO=org.apache.log4j.ConsoleAppender
>
> log4j.appender.INFO.layout=org.apache.log4j.SimpleLayout
>
>
>
> # rolling log file ("system.log
>
> log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
>
> log4j.appender.R.DatePattern='.'yyyy-MM-dd-HH
>
> log4j.appender.R.layout=org.apache.log4j.PatternLayout
>
> log4j.appender.R.layout.ConversionPattern=%5p [%t] %d{ISO8601} %F (line
> %L) %m%n
>
> log4j.appender.R.File=build/test/logs/system.log
>
>
>
>
>
> # 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 =
> java.util.logging.SimpleFormatter
>
>
>
> Thanks
>
> On Mon, Dec 13, 2010 at 2:23 PM, Aaron Morton <aa...@thelastpickle.com>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 <li...@gmail.com>
>> 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 < <sh...@gmail.com>
>> shimi.k@gmail.com> 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 <<a...@thelastpickle.com>
>>> aaron@thelastpickle.com> 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
>>>>
>>>>
>>>>
>>>
>>
>
Re: unable to start cassandra-0.7r2
Posted by Aaron Morton <aa...@thelastpickle.com>.
Given that log4j could not find it's configuration file I'm guessing it's a problem with the current working directory when eclipse starts cassandra
Can you start cassandra manually from where you have the source code?
I do not use eclipse so may not be much more help.
Aaron
On 14 Dec, 2010,at 11:01 AM, Liangzhao Zeng <li...@gmail.com> wrote:
log4j:WARN No appenders could be found for logger (org.apache.cassandra.service.AbstractCassandraDaemon).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Bad configuration; unable to start server
That is the error msg.
The log4j-server.properties 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
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#log4j.rootLogger=DEBUG,R
# output messages into a rolling log file as well as stdout
log4j.rootLogger=DEBUG, R, INFO, FINEST
log4j.appender.DEBUG=org.apache.log4j.ConsoleAppender
log4j.appender.DEBUG.layout=org.apache.log4j.SimpleLayout
log4j.appender.FINEST=org.apache.log4j.ConsoleAppender
log4j.appender.FINEST.layout=org.apache.log4j.SimpleLayout
log4j.appender.INFO=org.apache.log4j.ConsoleAppender
log4j.appender.INFO.layout=org.apache.log4j.SimpleLayout
# rolling log file ("system.log
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.R.layout=org.apache.log4jPatternLayout
log4j.appender.R.layout.ConversionPattern=%5p [%t] %d{ISO8601} %F (line %L) %m%n
log4j.appender.R.File=build/test/logs/systemlog
# 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 = java.util.logging.SimpleFormatter
Thanks
On Mon, Dec 13, 2010 at 2:23 PM, Aaron Morton <aa...@thelastpickle.com> 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 <li...@gmail.com> 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 <sh...@gmail.com> 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 <aa...@thelastpickle.com> 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
Re: unable to start cassandra-0.7r2
Posted by Liangzhao Zeng <li...@gmail.com>.
log4j:WARN No appenders could be found for logger
(org.apache.cassandra.service.AbstractCassandraDaemon).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for
more info.
Bad configuration; unable to start server
That is the error msg.
The log4j-server.properties 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
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#log4j.rootLogger=DEBUG,R
# output messages into a rolling log file as well as stdout
log4j.rootLogger=DEBUG, R, INFO, FINEST
log4j.appender.DEBUG=org.apache.log4j.ConsoleAppender
log4j.appender.DEBUG.layout=org.apache.log4j.SimpleLayout
log4j.appender.FINEST=org.apache.log4j.ConsoleAppender
log4j.appender.FINEST.layout=org.apache.log4j.SimpleLayout
log4j.appender.INFO=org.apache.log4j.ConsoleAppender
log4j.appender.INFO.layout=org.apache.log4j.SimpleLayout
# rolling log file ("system.log
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R.DatePattern='.'yyyy-MM-dd-HH
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%5p [%t] %d{ISO8601} %F (line %L)
%m%n
log4j.appender.R.File=build/test/logs/system.log
# 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 =
java.util.logging.SimpleFormatter
Thanks
On Mon, Dec 13, 2010 at 2:23 PM, Aaron Morton <aa...@thelastpickle.com>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 <li...@gmail.com>
> 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 < <sh...@gmail.com>
> shimi.k@gmail.com> 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 <<a...@thelastpickle.com>
>> aaron@thelastpickle.com> 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
>>>
>>>
>>>
>>
>
Re: unable to start cassandra-0.7r2
Posted by Aaron Morton <aa...@thelastpickle.com>.
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 <li...@gmail.com> 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 <sh...@gmail.com> 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 <aa...@thelastpickle.com> 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
>
>
>
Re: unable to start cassandra-0.7r2
Posted by Liangzhao Zeng <li...@gmail.com>.
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 <sh...@gmail.com> 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 <aa...@thelastpickle.com>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
>>
>>
>>
>
Re: unable to start cassandra-0.7r2
Posted by shimi <sh...@gmail.com>.
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 <aa...@thelastpickle.com>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
>
>
>
Re: unable to start cassandra-0.7r2
Posted by aaron morton <aa...@thelastpickle.com>.
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