cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3198) debian packaging installation problem when installing for the first time
Date Wed, 28 Sep 2011 17:16:45 GMT


Sylvain Lebresne updated CASSANDRA-3198:

    Attachment: 3198.patch

Yes, there is probably no reason for not fixing this. Attaching the simple patch that only
chown the directories on new installs.

I still don't really understand how previous install have worked so far with /var/lib/cassandra
being own by root but the cassandra process being run as the cassandra user, but it costs
nothing to be conservative: let's fix it for new install and do nothing for upgrade for now.

We can always keep debating on the best way to "fix" old installs, but let's have clean new
install right now. 
> debian packaging installation problem when installing for the first time
> ------------------------------------------------------------------------
>                 Key: CASSANDRA-3198
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 0.8.5
>            Reporter: Jérémy Sevellec
>            Assignee: Jérémy Sevellec
>             Fix For: 0.8.7
>         Attachments: 3198.patch, debian-postinst-fixperms.patch, trunk-3198-v1.patch
> when installing cassandra through the debian packaging for the first time, there is permission
problem when starting Cassandra.
> Normally, the postinst script change owner of /var/log/cassandra and /var/lib/cassandra
from root to cassandra user.
> there is a problem with the test which verify if threre is a need to change the owner
of these directory or not.
> On a new install, the $2 parameter is not set and the the test is false and the owner
is not changed.
> (simply, i think replace "&&" with "||" might work)

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