[
https://issues.apache.org/jira/browse/CASSANDRA-13330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999896#comment-16999896
]
Nicolas Chauvet commented on CASSANDRA-13330:
---------------------------------------------
For information, I've submitted a PR with a tmpfile as part of the systemd
service introduction:
https://issues.apache.org/jira/browse/CASSANDRA-13148
> /var/run/cassandra directory not created on Centos7
> ---------------------------------------------------
>
> Key: CASSANDRA-13330
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13330
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Environment: CentOS Linux release 7.3.1611 (Core) (x86_64)
> datastax-ddc.noarch 3.9.0-1
> datastax-ddc-tools.noarch 3.9.0-1
> java-1.8.0-openjdk.x86_64 1:1.8.0.121-0.b13.el7_3
> java-1.8.0-openjdk-headless.x86_64 1:1.8.0.121-0.b13.el7_3
> Reporter: Tobi
> Priority: Low
>
> After updating cassandra from 3.4 to 3.9 via the datastax repo the startup
> script /etc/init.d/cassandra was unable to stop cassandra. After checking the
> startscript we found that it's tried to read pid file from
> /var/run/cassandra/cassandra.pid
> But as this path does not exist, the cassandra process could not be stopped.
> As a fix we created /usr/lib/tmpfiles.d/cassandra.conf with this content
> d /var/run/cassandra 0750 cassandra cassandra -
> -
> After that the directory was created on boot and the pid file could we
> written in it
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
