Uploaded image for project: 'Flume'
  1. Flume
  2. FLUME-767

The bin/flume script assumes that Java exists in the $PATH variable despite the existence of $JAVA_HOME

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • 0.9.2, 0.9.4
    • 0.9.5
    • Shell
    • None
    • RHEL6, OS X

    Description

      I am creating a set of scripts that will automatically install Flume and all of its dependencies. These scripts end up installing Java from a tar archive and do not place Java on the environment's PATH. I am encountering a problem in the bin/flume script with the following line:

      exec $NODE_WATCHDOG java $JOPTS $UOPTS com.cloudera.flume.agent.FlumeNode "$@"

      This command assumes that Java is set in the $PATH variable despite the existence of $JAVA_HOME. The bin/flume script should be updated to not rely on Java being placed in the PATH environment variable:

      exec $NODE_WATCHDOG $JAVA_HOME/bin/java $JOPTS $UOPTS com.cloudera.flume.agent.FlumeNode "$@"

      Attachments

        Activity

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

          People

            alo.alt Alexander Alten-Lorenz
            jryding John Ryding
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment