[
https://issues.apache.org/jira/browse/BIGTOP-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644965#comment-13644965
]
Wing Yew Poon commented on BIGTOP-888:
--------------------------------------
Sean, I'm guessing the reason oozie start didn't work for you but works for
some folks is that oozie was using /usr/bin/java and you did not have
/usr/bin/java pointing to your JAVA_HOME/bin/java.
> Oozie losing value of JAVA_HOME when spawning sub-shell
> -------------------------------------------------------
>
> Key: BIGTOP-888
> URL: https://issues.apache.org/jira/browse/BIGTOP-888
> Project: Bigtop
> Issue Type: Bug
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Fix For: 0.6.0
>
> Attachments: BIGTOP-888.1.patch
>
>
> When starting Oozie server, it fails, despite Oracle JDK 6 being installed
> and configured in /etc/default/bigtop-utils:
> {noformat}
> Neither the JAVA_HOME nor the JRE_HOME environment variable is defined
> At least one of these environment variable is needed to run this program
> {noformat}
> This appears to be happening when a new instance of the shell is invoked for
> the subprocess of the init script. This is easy to fix, but I'm suspicious as
> this seems like a problem we would have seen long before now.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
