[ https://issues.apache.org/jira/browse/CASSANDRA-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4013. --------------------------------------- Resolution: Fixed Fix Version/s: (was: 1.1.0) "Cannot locate cassandra.yaml" was fixed in CASSANDRA-3986. In the meantime if you run it from one directory up ({{bin\cassandra-cli}}) that should work. The user mailing list is the right place to address questions like "where is keyspace config." > WARN No appenders could be found for logger (org.apache.cassandra.confi > ----------------------------------------------------------------------- > > Key: CASSANDRA-4013 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4013 > Project: Cassandra > Issue Type: Bug > Components: Documentation & website, Hadoop > Affects Versions: 1.1.0 > Environment: win7 > apacheTomcat6.0 > JDK1.6 > Reporter: Emotion > Labels: patch > Original Estimate: 72h > Remaining Estimate: 72h > > i'm installed apache-cassandra-1.1.0-beta1 version. > so, modify window7Config to Basic Linux Config > and i play cmd mode.... > write "cassandra-cli" and entered. > so i write "create keyspace keyspace1;" > but not created. output is error.... > what the... help...me... > and.. where is keyspace config? > different 0.6.8version to 1.1.0version > xml....to yaml? > please send to mail .. > xyz...@nate.com... > C:\apache-cassandra-1.1.0-beta1\bin>cassandra-cli > Starting Cassandra Client > Connected to: "Test Cluster" on 127.0.0.1/9160 > Welcome to Cassandra CLI version 1.1.0-beta1 > Type 'help;' or '?' for help. > Type 'quit;' or 'exit;' to quit. > [default@unknown] create keyspace keyspace1; > log4j:WARN No appenders could be found for logger (org.apache.cassandra.confi > atabaseDescriptor). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more > fo. > Cannot locate cassandra.yaml > Fatal configuration error; unable to start serv -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira