[
https://issues.apache.org/jira/browse/OOZIE-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643441#comment-14643441
]
Ravi Prakash commented on OOZIE-1876:
-------------------------------------
I did notice that you added this section in
[oozie.sh|https://github.com/apache/oozie/blob/master/client/src/main/bin/oozie#L36]
(same as
[oozie-setup.sh|https://github.com/apache/oozie/blob/master/distro/src/main/bin/oozie-setup.sh#L136])
to unzip the jar files in oozie.war file into BASEDIR/lib directory . Usually
regular cluster users don't have write access to the Oozie installation
directory. So when I ran {{oozie jobs -jobtype coordinator}} for instance, I
saw these errors:
{code}
mkdir: cannot create directory `/opt/oozie/lib': Permission denied
checkdir: cannot create extraction directory: /opt/oozie/lib
Permission denied
mv: cannot stat `/opt/oozie/lib/WEB-INF/lib/*.jar': No such file or directory
rmdir: failed to remove `/opt/oozie/lib/WEB-INF/lib': No such file or directory
rmdir: failed to remove `/opt/oozie/lib/WEB-INF': No such file or directory
Error: Could not find or load main class org.apache.oozie.cli.OozieCLI
{code}
Could you please tell me what you were thinking of running on a
gateway/workbench/desktop machine (NOT the Oozie server, where oozie-setup.sh
has run) and as what user so that the lib directory gets generated? For now I
am thinking of simply running the client once as root (so that the jars are
unzipped into the BASEDIR/lib directory successfully) and then chowning the lib
directory to the oozie user.
> use pom properties rather than specific version numbers in the pom files of
> hbaselibs, hcataloglibs, sharelib, etc
> -------------------------------------------------------------------------------------------------------------------
>
> Key: OOZIE-1876
> URL: https://issues.apache.org/jira/browse/OOZIE-1876
> Project: Oozie
> Issue Type: Improvement
> Components: build
> Affects Versions: 4.0.1
> Reporter: Xiaoshuang LU
> Assignee: Shwetha G S
> Fix For: 4.2.0
>
> Attachments: OOZIE-1876-v10.patch, OOZIE-1876-v10.patch,
> OOZIE-1876-v12.patch, OOZIE-1876-v13.patch, OOZIE-1876-v2.patch,
> OOZIE-1876-v3.patch, OOZIE-1876-v4.patch, OOZIE-1876-v5.patch,
> OOZIE-1876-v5.patch, OOZIE-1876-v6.patch, OOZIE-1876-v7.patch,
> OOZIE-1876-v7.patch, OOZIE-1876-v8.patch, OOZIE-1876-v9.patch,
> OOZIE-1876.patch
>
>
> version numbers (hbase, hive, hcatalog, sqoop, etc) are hard coded in the pom
> files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
