[
https://issues.apache.org/jira/browse/CASSANDRA-15770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vicente Jimenez Aguilar updated CASSANDRA-15770:
------------------------------------------------
Description:
Debian 10 "buster" has an updated {{start-stop-daemon}} version that causes
init script to fail to stop or restart Cassandra daemon. Stop option do not
stops first launched instance and depending of previous operations, restart and
start could launch a second Cassandra daemon instance.
{{start-stop-daemon}} since version 1.19.3 fail to stop matching only a pidfile
that can be writen by an unprivileged (non-root) user because it is considered
a security risk.
Adding a second matching option (user) solved this.
This fix does not break compatibility with older versions and does not mess
with pidfile's mode or permissions.
Related: CASSANDRA-15099
https://github.com/vice/cassandra/tree/debian-buster
was:
Debian 10 "buster" has an updated {{start-stop-daemon}} version that causes
init script to fail to stop or restart Cassandra daemon.
{{start-stop-daemon}} since version 1.19.3 fail to stop matching only a pidfile
that can be writen by an unprivileged (non-root) user because it is considered
a security risk.
Adding a second matching option (user) solved this.
This fix does not break compatibility with older versions and does not mess
with pidfile's mode or permissions.
Related: CASSANDRA-15099
https://github.com/vice/cassandra/tree/debian-buster
> stop and restart fail in Debian 10 buster
> -----------------------------------------
>
> Key: CASSANDRA-15770
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15770
> Project: Cassandra
> Issue Type: Bug
> Reporter: Vicente Jimenez Aguilar
> Priority: Normal
> Labels: Debian, easyfix, patch
> Fix For: 3.11.6
>
> Attachments: 0001-Fix-init-script-for-debian-Buster.patch
>
>
> Debian 10 "buster" has an updated {{start-stop-daemon}} version that causes
> init script to fail to stop or restart Cassandra daemon. Stop option do not
> stops first launched instance and depending of previous operations, restart
> and start could launch a second Cassandra daemon instance.
> {{start-stop-daemon}} since version 1.19.3 fail to stop matching only a
> pidfile that can be writen by an unprivileged (non-root) user because it is
> considered a security risk.
> Adding a second matching option (user) solved this.
> This fix does not break compatibility with older versions and does not mess
> with pidfile's mode or permissions.
> Related: CASSANDRA-15099
> https://github.com/vice/cassandra/tree/debian-buster
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
