<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode=&amp;quot;/user/yarn/.staging&amp;quot;:yarn:supergroup:drwx------ in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100406#M13313</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/504/kkulkarni.html" nodeid="504"&gt;@Kuldeep Kulkarni&lt;/A&gt; has this been resolved? Can you post your solution or accept best answer?&lt;/P&gt;</description>
    <pubDate>Tue, 02 Feb 2016 22:32:38 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2016-02-02T22:32:38Z</dc:date>
    <item>
      <title>Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100401#M13308</link>
      <description>&lt;P&gt;I have a shell action defined in my workflow which moves data from one hdfs location to another, my action is failing because of below error&lt;/P&gt;&lt;PRE&gt;Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------&lt;/PRE&gt;&lt;P&gt;Below are some useful configurations (got these from application log)&lt;/P&gt;&lt;PRE&gt;yarn.app.mapreduce.am.staging-dir=/user
user.name=yarn
mapreduce.job.user.name=xyz
&lt;/PRE&gt;&lt;P&gt;I also have added below variable in my workflow.xml file under shell action&lt;/P&gt;&lt;PRE&gt;&amp;lt;env-var&amp;gt;HADOOP_USER_NAME=${wf:user()}&amp;lt;/env-var&amp;gt;&lt;/PRE&gt;&lt;P&gt;I'm not sure why user "xyz" is trying to read/write at /user/yarn/.staging location. &lt;/P&gt;&lt;P&gt;Oozie experts, any idea whats going on here ?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2015 15:35:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100401#M13308</guid>
      <dc:creator>KuldeepK</dc:creator>
      <dc:date>2015-12-22T15:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100402#M13309</link>
      <description>&lt;P&gt;EDIT: oops - just read the end bit of your post... still try to do it in the shell action itself and see?&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;I believe this is a known limitation in non-secure clusters, whereby the containers are running as YARN user and not running as user xyz. &lt;/P&gt;&lt;P&gt;Try to pass in the HADOOP_USER_NAME variable as illustrated below: &lt;/P&gt;&lt;PRE&gt;$ `export HADOOP_USER_NAME=xyz ; hive -hiveconf hive.execution.engine=mr -e 'show databases' `&lt;/PRE&gt;</description>
      <pubDate>Wed, 23 Dec 2015 02:06:17 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100402#M13309</guid>
      <dc:creator>agillan</dc:creator>
      <dc:date>2015-12-23T02:06:17Z</dc:date>
    </item>
    <item>
      <title>Re: Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100403#M13310</link>
      <description>&lt;P&gt;here's an example of a shell action executed as another user &lt;A href="https://github.com/dbist/oozie/tree/master/apps/sqoopshell" target="_blank"&gt;https://github.com/dbist/oozie/tree/master/apps/sqoopshell&lt;/A&gt;, it is not the best approach but it works. User xyz executes the oozie workflow, the shell action executes as yarn user, thus you get xyz cannot access yarn.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Dec 2015 22:21:33 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100403#M13310</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2015-12-23T22:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100404#M13311</link>
      <description>&lt;P&gt;Thanks &lt;A rel="user" href="https://community.cloudera.com/users/214/agillan.html" nodeid="214"&gt;@Ana Gillan&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2015 11:38:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100404#M13311</guid>
      <dc:creator>KuldeepK</dc:creator>
      <dc:date>2015-12-24T11:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100405#M13312</link>
      <description>&lt;P&gt;Thanks &lt;A rel="user" href="https://community.cloudera.com/users/393/aervits.html" nodeid="393"&gt;@Artem Ervits&lt;/A&gt; - will try this&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2015 11:38:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100405#M13312</guid>
      <dc:creator>KuldeepK</dc:creator>
      <dc:date>2015-12-24T11:38:45Z</dc:date>
    </item>
    <item>
      <title>Re: Oozie shell action - Permission denied: user=xyz, access=EXECUTE, inode="/user/yarn/.staging":yarn:supergroup:drwx------</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100406#M13313</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/504/kkulkarni.html" nodeid="504"&gt;@Kuldeep Kulkarni&lt;/A&gt; has this been resolved? Can you post your solution or accept best answer?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Feb 2016 22:32:38 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Oozie-shell-action-Permission-denied-user-xyz-access-EXECUTE/m-p/100406#M13313</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-02T22:32:38Z</dc:date>
    </item>
  </channel>
</rss>

