You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "John Ryding (Created) (JIRA)" <ji...@apache.org> on 2011/09/27 16:37:11 UTC

[jira] [Created] (FLUME-767) The bin/flume script assumes that Java exists in the $PATH variable despite the existence of $JAVA_HOME

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

                 Key: FLUME-767
                 URL: https://issues.apache.org/jira/browse/FLUME-767
             Project: Flume
          Issue Type: Bug
          Components: Shell
    Affects Versions: v0.9.4, v0.9.2
         Environment: RHEL6, OS X
            Reporter: John Ryding
            Priority: Minor


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 "$@"


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLUME-767) The bin/flume script assumes that Java exists in the $PATH variable despite the existence of $JAVA_HOME

Posted by "John Ryding (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115541#comment-13115541 ] 

John Ryding commented on FLUME-767:
-----------------------------------

The workaround for this problem is to explicitly add $JAVA_HOME/bin to the $PATH variable before running the bin/flume script.

Although it's a simple fix, it may not be an obvious one for new users or novice Java users.
                
> The bin/flume script assumes that Java exists in the $PATH variable despite the existence of $JAVA_HOME
> -------------------------------------------------------------------------------------------------------
>
>                 Key: FLUME-767
>                 URL: https://issues.apache.org/jira/browse/FLUME-767
>             Project: Flume
>          Issue Type: Bug
>          Components: Shell
>    Affects Versions: v0.9.2, v0.9.4
>         Environment: RHEL6, OS X
>            Reporter: John Ryding
>            Priority: Minor
>
> 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 "$@"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (FLUME-767) The bin/flume script assumes that Java exists in the $PATH variable despite the existence of $JAVA_HOME

Posted by "Alexander Lorenz-Alten (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lorenz-Alten reassigned FLUME-767:
--------------------------------------------

    Assignee: Alexander Lorenz-Alten
    
> The bin/flume script assumes that Java exists in the $PATH variable despite the existence of $JAVA_HOME
> -------------------------------------------------------------------------------------------------------
>
>                 Key: FLUME-767
>                 URL: https://issues.apache.org/jira/browse/FLUME-767
>             Project: Flume
>          Issue Type: Bug
>          Components: Shell
>    Affects Versions: v0.9.2, v0.9.4
>         Environment: RHEL6, OS X
>            Reporter: John Ryding
>            Assignee: Alexander Lorenz-Alten
>            Priority: Minor
>
> 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 "$@"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira