cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob Fenwick (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4058) Debian package does not create /var/lib/cassandra/data
Date Fri, 16 Mar 2012 22:06:44 GMT


Jacob Fenwick commented on CASSANDRA-4058:

If you take the position that the users are required to set up data_file_directories, commitlog_directory,
and saved_caches_directory manually, then yes it is a user caused problem as they didn't follow
the documentation.

However, my observation is that a lot of packages make their default install have a basic
working state that does not require additional system configuration.

If you look at a Debian package like MySQL, which also stores its data files in /var/lib by
default, they use these sorts of permissions:
drwxr-s--- 2 mysql adm

I don't think it's unreasonable to set up permissions like that for the user automatically,
but maybe there's something subtle about cassandra that I'm missing.
> Debian package does not create /var/lib/cassandra/data
> ------------------------------------------------------
>                 Key: CASSANDRA-4058
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Ubuntu 11.10
>            Reporter: Jacob Fenwick
> I installed Cassandra using the Debian packages as described here:
> When trying to start Cassandra using /etc/init.d/cassandra start I get this error: unable to mkdirs /var/lib/cassandra/data
> The directory /var/lib/cassandra exists, but the directory /var/lib/cassandra/data does
> I would assume the data directory should have been created with the correct permissions,
but it was not.
> However, I tried creating /var/lib/cassandra/data and setting it the permissions to 666
and setting the user/group to cassandra/cassandra, and now I get this error:
> java.lang.AssertionError: Directory /var/lib/cassandra/data is not accessible.
> So what could possibly be the problem here?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message