<?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: Refresh Cluster fails on Secured Cluster in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34056#M8342</link>
    <description>&lt;P&gt;nop&lt;/P&gt;</description>
    <pubDate>Fri, 13 Nov 2015 05:47:05 GMT</pubDate>
    <dc:creator>ben123</dc:creator>
    <dc:date>2015-11-13T05:47:05Z</dc:date>
    <item>
      <title>Refresh Cluster fails on Secured Cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/32763#M8340</link>
      <description>&lt;P&gt;Hi !&lt;/P&gt;
&lt;P&gt;Im using CHD 5.4.0 with kerberos secured cluster&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When I run "Refresh Cluster" from Cloudera Manager, I get this message&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;Failed to update refreshable configuration files in the cluster&amp;nbsp;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this is the stderr&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;+ chown -R : /var/run/cloudera-scm-agent/process/1056-hdfs-DATANODE-refresh&lt;BR /&gt;+ acquire_kerberos_tgt hdfs.keytab&lt;BR /&gt;+ '[' -z hdfs.keytab ']'&lt;BR /&gt;+ '[' -n '' ']'&lt;BR /&gt;+ '[' validate-writable-empty-dirs = refresh-datanode ']'&lt;BR /&gt;+ '[' file-operation = refresh-datanode ']'&lt;BR /&gt;+ '[' bootstrap = refresh-datanode ']'&lt;BR /&gt;+ '[' failover = refresh-datanode ']'&lt;BR /&gt;+ '[' transition-to-active = refresh-datanode ']'&lt;BR /&gt;+ '[' initializeSharedEdits = refresh-datanode ']'&lt;BR /&gt;+ '[' initialize-znode = refresh-datanode ']'&lt;BR /&gt;+ '[' format-namenode = refresh-datanode ']'&lt;BR /&gt;+ '[' monitor-decommission = refresh-datanode ']'&lt;BR /&gt;+ '[' jnSyncWait = refresh-datanode ']'&lt;BR /&gt;+ '[' nnRpcWait = refresh-datanode ']'&lt;BR /&gt;+ '[' -safemode = '' -a get = '' ']'&lt;BR /&gt;+ '[' monitor-upgrade = refresh-datanode ']'&lt;BR /&gt;+ '[' finalize-upgrade = refresh-datanode ']'&lt;BR /&gt;+ '[' rolling-upgrade-prepare = refresh-datanode ']'&lt;BR /&gt;+ '[' rolling-upgrade-finalize = refresh-datanode ']'&lt;BR /&gt;+ '[' nnDnLiveWait = refresh-datanode ']'&lt;BR /&gt;+ '[' refresh-datanode = refresh-datanode ']'&lt;BR /&gt;+ '[' 3 -lt 3 ']'&lt;BR /&gt;+ DN_ADDR=bda1node02.company.com:50020&lt;BR /&gt;+ /opt/cloudera/parcels/CDH-5.4.0-1.cdh5.4.0.p0.27/lib/hadoop-hdfs/bin/hdfs --config /var/run/cloudera-scm-agent/process/1056-hdfs-DATANODE-refresh dfsadmin -reconfig datanode bda1node02.company.com:50020 start&lt;BR /&gt;15/10/07 16:27:43 WARN security.UserGroupInformation: PriviledgedActionException as:hdfs (auth:KERBEROS) cause:javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]&lt;BR /&gt;15/10/07 16:27:43 WARN ipc.Client: Exception encountered while connecting to the server : javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]&lt;BR /&gt;15/10/07 16:27:43 WARN security.UserGroupInformation: PriviledgedActionException as:hdfs (auth:KERBEROS) cause:java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]&lt;BR /&gt;reconfig: Failed on local exception: java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]; Host Details : local host is: "bda1node02.company.com/192.168.8.2"; destination host is: "bda1node02.company.com":50020;&lt;BR /&gt;+ RET=255&lt;BR /&gt;+ '[' 255 -ne 0 ']'&lt;BR /&gt;+ echo 'Unable to start reconfigure task on DataNode bda1node02.company.com:50020.'&lt;BR /&gt;+ exit 255&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any thoughts?&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;
&lt;P&gt;Ben&lt;/P&gt;</description>
      <pubDate>Tue, 08 Nov 2016 16:08:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/32763#M8340</guid>
      <dc:creator>ben123</dc:creator>
      <dc:date>2016-11-08T16:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: Refresh Cluster fails on Secured Cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34021#M8341</link>
      <description>&lt;P&gt;Any luck on this one? We just ran into it as well.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2015 20:15:02 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34021#M8341</guid>
      <dc:creator>cduranleau</dc:creator>
      <dc:date>2015-11-11T20:15:02Z</dc:date>
    </item>
    <item>
      <title>Re: Refresh Cluster fails on Secured Cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34056#M8342</link>
      <description>&lt;P&gt;nop&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2015 05:47:05 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34056#M8342</guid>
      <dc:creator>ben123</dc:creator>
      <dc:date>2015-11-13T05:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Refresh Cluster fails on Secured Cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34227#M8343</link>
      <description>&lt;P&gt;Spoke with a Cloudera rep. They suggested upgrading to CM 5.4.5 or later.&amp;nbsp;In the mean time, the&amp;nbsp;workaround was to manually kinit with the HDFS datanode keytab and kick of the refresh from the command line.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It will be a while before we get to try the upgrade, but I'll post back here after we complete it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2015 19:22:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/34227#M8343</guid>
      <dc:creator>cduranleau</dc:creator>
      <dc:date>2015-11-19T19:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: Refresh Cluster fails on Secured Cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/40555#M8344</link>
      <description>&lt;P&gt;On Cloudera Manager 5.7 I was seeing same problem, but luckily I fixed it by adding this to "YARN Service Advanced Configuration Snippet (Safety Valve) for hadoop-policy.xml"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;property&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;name&amp;gt;security.resourcemanager-administration.protocol.acl&amp;lt;/name&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;value&amp;gt;*&amp;lt;/value&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/property&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you found this helpful, please buy me beer &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2016 23:30:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/40555#M8344</guid>
      <dc:creator>ben123</dc:creator>
      <dc:date>2016-05-06T23:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: Refresh Cluster fails on Secured Cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/40556#M8345</link>
      <description>&lt;P&gt;Of course if you do this anyone can change resource pool settings using Cloudera Manager REST API or yarn admin command. When you get update error you can check specific user who perform the command from Cloudera Server log, but i didn't bother to check it.&lt;/P&gt;</description>
      <pubDate>Fri, 06 May 2016 23:35:00 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Refresh-Cluster-fails-on-Secured-Cluster/m-p/40556#M8345</guid>
      <dc:creator>ben123</dc:creator>
      <dc:date>2016-05-06T23:35:00Z</dc:date>
    </item>
  </channel>
</rss>

