[
https://issues.apache.org/jira/browse/OOZIE-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558660#comment-13558660
]
Arun Vasu commented on OOZIE-1165:
----------------------------------
Hi Jun,
One scenario I faced was given below.
When we set up Oozie for the first time, as per documentation we need to copy
all files in 'lib' folder of Hadoop home directory to 'libext' folder in
Oozie home directory. But doing this will not include
'hadoop-common-0.22.0.jar' file. Because it sits outside lib folder in Hadoop
home directory.
If we start Oozie, then user will not be aware that Oozie actually did not
start. He needs to go to logs folder to find it out.
> Displaying Oozie startup status
> -------------------------------
>
> Key: OOZIE-1165
> URL: https://issues.apache.org/jira/browse/OOZIE-1165
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Environment: Operating System: Centos 6
> Reporter: Arun Vasu
> Priority: Minor
> Labels: oozie
>
> It will be very useful if the proper start up message can be displayed after
> running the 'oozie-start.sh'. Currently, even if the oozie server is failed
> to start, it is difficult for the user to know whether it is started or not
> by looking into the console.
--
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
