[CASSANDRA-1772] debian initscript sometimes mistakenly thinks it failed, gives extraneous output

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 0.7.0 rc 2
• Component/s: Packaging

Environment

Debian Squeeze with cassandra 0.7.0~rc1 on a slicehost VM

• Severity: Low
• Assignee: paul cannon
• Reporter: paul cannon

Authors

paul cannon

Reviewers

Eric Evans

• Created: 24/Nov/10 01:15
• Updated: 16/Apr/19 09:33
• Resolved: 24/Nov/10 23:11

Description

On my test systems, which are all relatively slow VMs, the Cassandra debian initscript usually thinks it fails to start, even though the startup was successful. It appears that jsvc forks the daemon process and exits, and the initscript check for the running Cassandra service occurs before the new daemon is able to initialize itself and create its pidfile.

On top of that, most invocations end up spitting out a small amount of garbage from /bin/ps, in addition to the typical "Stopping Cassandra: cassandra." log messages one sees if verbose=yes in /etc/default/rcS. This is not very flattering.

Finally, the initscript should provide the "status" command to meet current LSB spec. The functionality is mostly complete already anyway, and it can be quite useful.