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

Cassandra doesn't start on Red Hat Linux due to hardcoded JAVA_HOME

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.8.4
    • Packaging
    • None
    • CentOS release 5.6

    • Low

    Description

      On CentOS /etc/init.d/cassandra has

      export JAVA_HOME=/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/

      While there is no such a directory on our server it was ok for 0.8.2, because /usr/sbin/cassandra checked the executable

      if [ -x $JAVA_HOME/bin/java ]; then
      JAVA=$JAVA_HOME/bin/java
      else
      JAVA=`which java`
      fi

      But 0.8.3 builds replaced the above code with one that doesn't check if JAVA_HOME is set correctly.

      if [ -n "$JAVA_HOME" ]; then
      JAVA="$JAVA_HOME/bin/java"
      else
      JAVA=java
      fi

      That's why cassandra doesn't start anymore.

      The correct fix would be to remove "export JAVA_HOME" from /etc/init.d/cassandra or set it only to correct path and only if it hasn't already been set.

      It would also be nice to revert to "[ -x $JAVA_HOME/bin/java ]" in /usr/sbin/cassandra

      Attachments

        Activity

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

          People

            thepaul paul cannon Assign to me
            tarasp Taras Puchko
            paul cannon
            Taras Puchko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment