You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Michael Shuler (JIRA)" <ji...@apache.org> on 2017/01/04 16:06:58 UTC

[jira] [Resolved] (CASSANDRA-13046) Missing PID file directory when installing from RPM

     [ https://issues.apache.org/jira/browse/CASSANDRA-13046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Shuler resolved CASSANDRA-13046.
----------------------------------------
    Resolution: Fixed

Committed to 2.2 and merged up. Thanks!

https://github.com/apache/cassandra/commit/3d90bb0cc74ca52fc6a9947a746695630ca7fc2a

> Missing PID file directory when installing from RPM
> ---------------------------------------------------
>
>                 Key: CASSANDRA-13046
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13046
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: CentOS 7.3
>            Reporter: Marcel Dopita
>            Assignee: Michael Shuler
>            Priority: Minor
>             Fix For: 2.2.9, 3.0.11, 3.10
>
>
> As already reported in CASSANDRA-10920, changes to /var/run/cassandra folder are not persistent across reboots and therefore saving pid file to that location fails. This causes trouble when managing the status of the cassandra service.
> The linked issue mentions good enough (and working) workaround (compared to writing new service file for systemd). 
> Trunk now contains files necessary to produce RHEL compatible RPM in the /redhat folder.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)