Did you drop a keyspace not too long before the upgrade, or did you mess up with your system tables in the process ?
-- Sylvain On Wed, Mar 23, 2011 at 11:47 AM, Sébastien Druon <sdr...@spotuse.com> wrote: > Hello > After having updgraded from 0.7.0 to 0.7.4, cassandra does not start > anymore. > I have the following errot stack: > INFO 11:47:04,112 Finished reading > /var/lib/cassandra/commitlog/CommitLog-1296815168287.log > ERROR 11:47:04,114 Exception encountered during startup. > java.lang.NullPointerException > at org.apache.cassandra.db.Table.createReplicationStrategy(Table.java:275) > at org.apache.cassandra.db.Table.<init>(Table.java:221) > at org.apache.cassandra.db.Table.open(Table.java:110) > at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:273) > at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:156) > at > org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:173) > at > org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:314) > at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:79) > Exception encountered during startup. > java.lang.NullPointerException > at org.apache.cassandra.db.Table.createReplicationStrategy(Table.java:275) > at org.apache.cassandra.db.Table.<init>(Table.java:221) > at org.apache.cassandra.db.Table.open(Table.java:110) > at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:273) > at org.apache.cassandra.db.commitlog.CommitLog.recover(CommitLog.java:156) > at > org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:173) > at > org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassandraDaemon.java:314) > at org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:79) > Does someone know what is happening and how to fix the problem? > Thanks a lot in advance > Sébastien
