[
https://issues.apache.org/jira/browse/CASSANDRA-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Yeschenko resolved CASSANDRA-5196.
------------------------------------------
Resolution: Cannot Reproduce
Pretty sure this particular issue was caused by not having enough permissions
to create the directories. Please reopen if that's not the case and you can
reproduce.
> IllegalStateException thrown when running new installation with old data
> directories
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-5196
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5196
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.1
> Environment: CentOS 5.5
> Reporter: Robbie Strickland
> Assignee: Aleksey Yeschenko
> Priority: Minor
>
> If you install 1.2.1 when there are existing data directories, the scrub
> operation fails, throwing this exception:
> ERROR [main] 2013-01-29 15:05:06,564 FileUtils.java (line 373) Stopping the
> gossiper and the RPC server
> ERROR [main] 2013-01-29 15:05:06,564 CassandraDaemon.java (line 387)
> Exception encountered during startup
> java.lang.IllegalStateException: No configured daemon
> at
> org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:314)
> at
> org.apache.cassandra.io.util.FileUtils.handleFSError(FileUtils.java:375)
> at org.apache.cassandra.db.Directories.<init>(Directories.java:113)
> at org.apache.cassandra.db.Directories.create(Directories.java:91)
> at
> org.apache.cassandra.db.ColumnFamilyStore.scrubDataDirectories(ColumnFamilyStore.java:403)
> at
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:174)
> at
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:370)
> at
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:413)
> This condition should produce a more reasonable exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
