Virag,
Can you add documentation for this change since the current build and setup of 
oozie doesn't cover this?
Bowen




________________________________
 From: Virag Kothari <vi...@yahoo-inc.com>
To: bowen zhang <bowenzhang...@yahoo.com>; "dev@oozie.apache.org" 
<dev@oozie.apache.org>; Robert Kanter <rkan...@cloudera.com> 
Sent: Monday, September 16, 2013 2:58 PM
Subject: Re: issue after OOZIE-1461
 

Hi Robert/Bowen,

The hadoop configs need to be there in class path (hadoop-conf dir or 
oozie-server/lib). So the HadoopAccessorService can create the appropriate 
filesystem object. This will fix your current issue.
But there is one more problem you might face while running a job where 
permissions are not recursively applied. This fix is in OOZIE-1528 and will be 
checked in shortly.

Thanks,
Virag

From: bowen zhang <bowenzhang...@yahoo.com<mailto:bowenzhang...@yahoo.com>>
Reply-To: bowen zhang <bowenzhang...@yahoo.com<mailto:bowenzhang...@yahoo.com>>
Date: Monday, September 16, 2013 2:49 PM
To: "dev@oozie.apache.org<mailto:dev@oozie.apache.org>" 
<dev@oozie.apache.org<mailto:dev@oozie.apache.org>>, Virag Kothari 
<vi...@yahoo-inc.com<mailto:vi...@yahoo-inc.com>>
Subject: Re: Fwd: issue after OOZIE-1461

what I found is the variable uri from tmpShareLibPath has authority of "null".


________________________________
From: Robert Kanter <rkan...@cloudera.com<mailto:rkan...@cloudera.com>>
To: Virag Kothari <vi...@yahoo-inc.com<mailto:vi...@yahoo-inc.com>>; 
"dev@oozie.apache.org<mailto:dev@oozie.apache.org>" 
<dev@oozie.apache.org<mailto:dev@oozie.apache.org>>
Sent: Monday, September 16, 2013 2:39 PM
Subject: Fwd: issue after OOZIE-1461

Hi Virag,

After OOZIE-1461, Bowen (and I too) have run into this exception when
starting Oozie, so it fails and won't start.  I checked, and for me at
least, the share/lib/ dir looks like it has the correct permissions.
Any thoughts?

thanks
- Robert


On Mon, Sep 16, 2013 at 2:26 PM, Bowen Zhang 
<bzh...@hortonworks.com<mailto:bzh...@hortonworks.com>> wrote:

> Hi Robert,
> After rebasing to the trunk, I hit this error when trying to bring up
> oozie.
> org.apache.oozie.service.ServiceException: E0100: Could not initialize
> service [org.apache.oozie.service.ShareLibService], Failed to set
> permissions of path: /user/bzhang/share/lib/tmp-20130916135406/oozie to 0755
>        at
> org.apache.oozie.service.ShareLibService.init(ShareLibService.java:81)
>        at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:368)
>        at org.apache.oozie.service.Services.setService(Services.java:354)
>        at
> org.apache.oozie.service.Services.loadServices(Services.java:287)
>        at org.apache.oozie.service.Services.init(Services.java:208)
>        at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:45)
>        at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
>        at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
>        at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
>        at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
>        at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
>        at
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
>        at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
>        at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
>        at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
>        at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
>        at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
>        at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
>        at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
>        at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
>        at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
>        at
> org.apache.catalina.core.StandardService.start(StandardService.java:525)
>        at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
>        at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
>        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> Caused by: java.io.IOException: Failed to set permissions of path:
> /user/bzhang/share/lib/tmp-20130916135406/oozie to 0755
>        at
> org.apache.hadoop.fs.FileUtil.checkReturnValue(FileUtil.java:689)
>        at org.apache.hadoop.fs.FileUtil.setPermission(FileUtil.java:662)
>        at
> org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:509)
>        at
> org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:286)
>        at
> org.apache.oozie.service.ShareLibService.copyJarContainingClasses(ShareLibService.java:109)
>        at
> org.apache.oozie.service.ShareLibService.copyLauncherJarsToShareLib(ShareLibService.java:90)
>        at
> org.apache.oozie.service.ShareLibService.init(ShareLibService.java:76)
>        ... 29 more
>
>
> It might have sth to do with the version of hadoop that hadoopAccessor
> cannot change file permission. Do you see this problem?
>
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

Reply via email to