<?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: How to resolve  Pig view errors on kerbereized cluster? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200428#M71538</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/39293/kabadourawia.html" nodeid="39293"&gt;@raouia &lt;/A&gt;&lt;/P&gt;&lt;P&gt;- Which version of ambari are you using?  There is a "auth" property which is only needed if the view is Custom Configured or Ambari Server is Kerberized before 2.4.0.  &lt;/P&gt;&lt;P&gt;- If you are using prior version of ambari then can you please check if you have set the ambari-server principal to your pig view for auth?  You can refer to the following doc to get more detailed information about it: &lt;A href="https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/section_pig_view_kerberos_config.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/section_pig_view_kerberos_config.html&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;auth=KERBEROS;proxyuser=&amp;lt;ambari-principal-name&amp;gt;&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;You can find the ambariserver principal name inside the following file "/etc/ambari-server/conf/krb5JAASLogin.conf"&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Example:&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;# cat /etc/ambari-server/conf/krb5JAASLogin.conf
com.sun.security.jgss.krb5.initiate {
        com.sun.security.auth.module.Krb5LoginModule required
        renewTGT=false
        doNotPrompt=true
        useKeyTab=true
        keyTab="/etc/security/keytabs/ambari.server.keytab"
        principal="ambari-server-kerberos_ambari@EXAMPLE.COM"
        storeKey=true
        useTicketCache=false;
    };&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Also please check if you have configured the "hadoop.proxyuser" property set properly for the "HDFS" and "WebHCAT"  as described in the following doc: &lt;A href="https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/configuring_your_cluster_for_pig_view.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/configuring_your_cluster_for_pig_view.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Nov 2017 02:23:14 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2017-11-22T02:23:14Z</dc:date>
    <item>
      <title>How to resolve  Pig view errors on kerbereized cluster?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200427#M71537</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I need to test a script through Pig View on my kerbereized cluster.&lt;/P&gt;&lt;P&gt;I attached my script details in &lt;A href="https://community.cloudera.com/legacyfs/online/attachments/42691-script.png"&gt;script.png.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;When i run this script i got the error mentioned in &lt;A href="https://community.cloudera.com/legacyfs/online/attachments/42692-error.png"&gt;error.png&lt;/A&gt; through /var/log/ambari-server/pig-view/pig-view.log.&lt;/P&gt;&lt;P&gt;I access to Ambari UI with admin as username.&lt;/P&gt;&lt;P&gt;How can i resolve this issue?&lt;/P&gt;&lt;P&gt;I'll be really grateful if someone could help me.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 00:44:11 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200427#M71537</guid>
      <dc:creator>kabadou_rawia</dc:creator>
      <dc:date>2017-11-22T00:44:11Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve  Pig view errors on kerbereized cluster?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200428#M71538</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/39293/kabadourawia.html" nodeid="39293"&gt;@raouia &lt;/A&gt;&lt;/P&gt;&lt;P&gt;- Which version of ambari are you using?  There is a "auth" property which is only needed if the view is Custom Configured or Ambari Server is Kerberized before 2.4.0.  &lt;/P&gt;&lt;P&gt;- If you are using prior version of ambari then can you please check if you have set the ambari-server principal to your pig view for auth?  You can refer to the following doc to get more detailed information about it: &lt;A href="https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/section_pig_view_kerberos_config.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/section_pig_view_kerberos_config.html&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;auth=KERBEROS;proxyuser=&amp;lt;ambari-principal-name&amp;gt;&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;You can find the ambariserver principal name inside the following file "/etc/ambari-server/conf/krb5JAASLogin.conf"&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Example:&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;# cat /etc/ambari-server/conf/krb5JAASLogin.conf
com.sun.security.jgss.krb5.initiate {
        com.sun.security.auth.module.Krb5LoginModule required
        renewTGT=false
        doNotPrompt=true
        useKeyTab=true
        keyTab="/etc/security/keytabs/ambari.server.keytab"
        principal="ambari-server-kerberos_ambari@EXAMPLE.COM"
        storeKey=true
        useTicketCache=false;
    };&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Also please check if you have configured the "hadoop.proxyuser" property set properly for the "HDFS" and "WebHCAT"  as described in the following doc: &lt;A href="https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/configuring_your_cluster_for_pig_view.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-views/content/configuring_your_cluster_for_pig_view.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 02:23:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200428#M71538</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-11-22T02:23:14Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve  Pig view errors on kerbereized cluster?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200429#M71539</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/3418/jsensharma.html" nodeid="3418"&gt;@Jay Kumar SenSharma&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for your reply. &lt;/P&gt;&lt;P&gt;- My ambari version is Version
      2.5.1.0.&lt;/P&gt;&lt;P&gt;- My ambari server is running with &lt;STRONG&gt;root use&lt;/STRONG&gt;r. So,i resecured my cluster with the principal "&lt;STRONG&gt;root@ROSAFI.COM&lt;/STRONG&gt;" and made all the necessary configurations by following this link:  
     &lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.1.0/bk_ambari-security/content/set_up_kerberos_for_ambari_server.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.1.0/bk_ambari-security/content/set_up_kerberos_for_ambari_server.html&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;The output of file "/etc/ambari-server/conf/krb5JAASLogin.conf" is:&lt;/P&gt;&lt;PRE&gt;com.sun.security.jgss.krb5.initiate {
    com.sun.security.auth.module.Krb5LoginModule required
    renewTGT=false
    doNotPrompt=true
    useKeyTab=true
    keyTab="/etc/security/keytabs/root.server.keytab"
    principal="root@ROSAFI.COM"
    storeKey=true
    useTicketCache=false;
};&lt;/PRE&gt;&lt;P&gt;- I've also made the necessary configuration in Pig view as mentioned in &lt;A href="https://community.cloudera.com/legacyfs/online/attachments/42705-pig-auth.png"&gt;pig-auth.png.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;- I've set "hadoop.proxyuser" in HDFS as shown in &lt;A href="https://community.cloudera.com/legacyfs/online/attachments/42706-proxyuser.png"&gt;proxyuser.png.&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I'm really stuck. Please help me understanding the cause of this issue. &lt;/P&gt;&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/3418/jsensharma.html" nodeid="3418"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 16:39:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200429#M71539</guid>
      <dc:creator>kabadou_rawia</dc:creator>
      <dc:date>2017-11-22T16:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve  Pig view errors on kerbereized cluster?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200430#M71540</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/39293/kabadourawia.html" nodeid="39293"&gt;@raouia &lt;/A&gt;&lt;/P&gt;&lt;P&gt;Based on your "/etc/ambari-server/conf/krb5JAASLogin.conf" file setting "principal" we see that your ambari server principal name is "root@ROSAFI.COM" hence your PigView Auth setting should be something like following, Which is correctly set in your case.&lt;/P&gt;&lt;PRE&gt;auth=KERBEROS;proxyuser=root&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;.&lt;BR /&gt;But we noticed the following error inside your "error.png" image saying that&lt;/P&gt;&lt;PRE&gt;org.apache.ambari.view.utils.ambari.AmbariApiException: {"error":"User: HTTP/ambari@ROSAFI.COM is not allowed to impersonate admin"} &lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;.&lt;BR /&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Suggestion:&lt;/STRONG&gt;&lt;BR /&gt;Which indicates that you have not set the following property properly inside the hadoop  core-site.xml inside the proxyuser settings:&lt;/P&gt;&lt;PRE&gt;hadoop.proxyuser.HTTP.hosts=*
hadoop.proxyuser.HTTP.group=*&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;So can you please try adding the above two properties and then try again. Also please do a kinit as following isnide ambari server host and then restart ambari-server once.&lt;/P&gt;&lt;PRE&gt;# kdestroy
# kinit -kt /etc/security/keytabs/root.server.keytab  root@ROSAFI.COM
# klist
# ambari-server stop
# ambari-server start&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Then  try to access the ambari UI again.&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 17:41:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200430#M71540</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2017-11-22T17:41:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to resolve  Pig view errors on kerbereized cluster?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200431#M71541</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/3418/jsensharma.html" nodeid="3418"&gt;@Jay Kumar SenSharma&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thank you very much. Your suggestion worked for me.&lt;BR /&gt;&lt;A rel="user" href="https://community.cloudera.com/users/3418/jsensharma.html" nodeid="3418"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Wed, 22 Nov 2017 18:30:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-resolve-Pig-view-errors-on-kerbereized-cluster/m-p/200431#M71541</guid>
      <dc:creator>kabadou_rawia</dc:creator>
      <dc:date>2017-11-22T18:30:05Z</dc:date>
    </item>
  </channel>
</rss>

