Uploaded image for project: 'Apache Cassandra'
  1. Apache Cassandra
  2. CASSANDRA-1772

debian initscript sometimes mistakenly thinks it failed, gives extraneous output

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 0.7.0 rc 2
    • Packaging
    • None
    • Debian Squeeze with cassandra 0.7.0~rc1 on a slicehost VM

    • Low

    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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            thepaul paul cannon Assign to me
            thepaul paul cannon
            paul cannon
            Eric Evans
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment