cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3198) debian packaging installation problem when installing for the first time
Date Thu, 15 Sep 2011 10:50:08 GMT


Sylvain Lebresne commented on CASSANDRA-3198:

bq. we didn't always create the cassandra user and chown in postinst

Yes, and to make it clear what my point is: while we do create the cassandra user since 0.6.4-2,
we *never* chown in the postinst _excepted_ for people that upgraded *all the way* since a
pre 0.6.4 release. That is, any current new installation (say of 0.8.5) *does not* chown in
the postint and /var/lib/cassandra and /var/log/cassandra (the directories) are owned by root,
not cassandra.

Now I'm perfectly fine saying that there is no point in changing things during upgrades and
to only fix the chown in the postinst for new installs, but just wanted to make it clear that
this has nothing to do with upgrades from some 0.6.x versions.

> 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.6
>         Attachments: 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.
For more information on JIRA, see:


View raw message