Sign up ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Followed the instructions here:

Installed OpsCenter on m3.large. When launching an instance, I get this error:

Error: Start stage failed: Failed to start node [ip]: Timed out waiting for Cassandra to start.

The log on the individual server is: (line 235) Directory /mnt/cassandra/data doesn't exist (line 239) Has no permission to create /mnt/cassandra/data directory

What do I need to do to let it have the permission? I use a key/secret pair that have all rights on AWS to generate more nodes.

share|improve this question

closed as off-topic by mdpc, kasperd, Ward, MadHatter, HBruijn Aug 30 '14 at 9:30

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must demonstrate a minimal understanding of the problem being solved. Try including attempted solutions, why they didn't work, and the expected results. See How can I ask better questions on Server Fault? for further guidance." – kasperd, Ward, MadHatter, HBruijn
If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer 1

Perhaps if you create the directory /mnt/cassandra/data for it, as root, then chown it to the user that Cassandra is running as.

Alternatively, are you sure it's mounted correctly? (stuff in /mnt tends to be remote mounts)

share|improve this answer
Manually creating the directory+chown and restarting the service on each new node works, thanks. Any idea why I have to create it myself? Shouldn't it just have the permissions? – elado Aug 28 '14 at 16:40
I dunno. I didn't actually know the answer, just made an educated guess. ;) – Tom O'Connor Aug 29 '14 at 10:19

Not the answer you're looking for? Browse other questions tagged or ask your own question.