[CASSANDRA-15770] stop and restart fail in Debian 10 buster

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.2.20, 3.0.21, 3.11.7, 4.0-beta1, 4.0
• Component/s: Packaging
• Labels: Debian easyfix patch
• Bug Category: Correctness
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: 2.2.19

Source Control Link

https://github.com/apache/cassandra/commit/469c6496ae8817975140e5d353ccdebedbea6c06

Test and Documentation Plan

none

• Assignee: Vicente Jimenez Aguilar
• Reporter: Vicente Jimenez Aguilar

Authors

Vicente Jimenez Aguilar

Reviewers

Brandon Williams

• Created: 29/Apr/20 10:03
• Updated: 16/Apr/21 13:15
• Resolved: 29/Apr/20 17:06

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

Issue Links

• duplicates: CASSANDRA-15099 Debian 10 buster: init file require PID file to be owned by root
• is duplicated by: CASSANDRA-16609 Debian init script for 2.2.19 mostly broken on Debian 10 with systemd