<?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: Failed to Start NameNode 403 error in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180328#M73110</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1215/lhfeilaile.html" nodeid="1215"&gt;@Hefei Li&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Wonderful!!!  Good to see that the issue is resolved. &lt;/P&gt;&lt;P&gt;As the issue is resolved, hence it will be also great if you can mark this HCC thread as Answered by clicking on the "Accept" Button on the correct answer. That way other HCC users can quickly find the solution when they encounter the same issue.&lt;/P&gt;&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1215/lhfeilaile.html" nodeid="1215"&gt;&lt;/A&gt; &lt;/P&gt;</description>
    <pubDate>Fri, 12 Jan 2018 14:23:10 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2018-01-12T14:23:10Z</dc:date>
    <item>
      <title>Failed to Start NameNode 403 error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180324#M73106</link>
      <description>&lt;P&gt;I have installed Ambari 2.6.0.0 version with HDP 2.6.3 and added some of the services.
But while enabling Kerberos I am facing one weird issue. The error log is:&lt;/P&gt;&lt;PRE&gt;Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", line 361, in &amp;lt;module&amp;gt;
    NameNode().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 367, in execute
    method(env)
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 970, in restart
    self.start(env, upgrade_type=upgrade_type)
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", line 99, in start
    upgrade_suspended=params.upgrade_suspended, env=env)
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, in thunk
    return fn(*args, **kwargs)
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py", line 234, in namenode
    create_hdfs_directories()
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py", line 301, in create_hdfs_directories
    mode=0777,
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 166, in __init__
    self.env.run()
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 160, in run
    self.run_action(resource, action)
  File "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", line 124, in run_action
    provider_action()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 604, in action_create_on_execute
    self.action_delayed("create")
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 601, in action_delayed
    self.get_hdfs_resource_executor().action_delayed(action_name, self)
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 328, in action_delayed
    self._assert_valid()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 287, in _assert_valid
    self.target_status = self._get_file_status(target)
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 430, in _get_file_status
    list_status = self.util.run_command(target, 'GETFILESTATUS', method='GET', ignore_status_codes=['404'], assertable_result=False)
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 177, in run_command
    return self._run_command(*args, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py", line 248, in _run_command
    raise WebHDFSCallException(err_msg, result_dict)
resource_management.libraries.providers.hdfs_resource.WebHDFSCallException: Execution of 'curl -sS -L -w '%{http_code}' -X GET --negotiate -u : 'http://a01-r03-i164-156-515w9ay.xxx.xxx:50070/webhdfs/v1/tmp?op=GETFILESTATUS'' returned status_code=403. 
&amp;lt;html&amp;gt;
&amp;lt;head&amp;gt;
&amp;lt;meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/&amp;gt;
&amp;lt;title&amp;gt;Error 403 org.apache.hadoop.security.authentication.client.AuthenticationException&amp;lt;/title&amp;gt;
&amp;lt;/head&amp;gt;
&amp;lt;body&amp;gt;&amp;lt;h2&amp;gt;HTTP ERROR 403&amp;lt;/h2&amp;gt;
&amp;lt;p&amp;gt;Problem accessing /webhdfs/v1/tmp. Reason:
&amp;lt;pre&amp;gt;    org.apache.hadoop.security.authentication.client.AuthenticationException&amp;lt;/pre&amp;gt;&amp;lt;/p&amp;gt;&amp;lt;hr /&amp;gt;&amp;lt;i&amp;gt;&amp;lt;small&amp;gt;Powered by Jetty://&amp;lt;/small&amp;gt;&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;                                                
&amp;lt;br/&amp;gt; &lt;/PRE&gt;&lt;P&gt;Any suggestions will be appreciated. Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 00:46:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180324#M73106</guid>
      <dc:creator>Hefei</dc:creator>
      <dc:date>2018-01-05T00:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start NameNode 403 error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180325#M73107</link>
      <description>&lt;P&gt;Can you kinit successfully as the Namenode prinicpal? Does the Namenode Principal have the correct permissions? Is your krb5.conf in /etc or in a non-standard directory? &lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2018 11:35:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180325#M73107</guid>
      <dc:creator>tletempt</dc:creator>
      <dc:date>2018-01-09T11:35:04Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start NameNode 403 error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180326#M73108</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1215/lhfeilaile.html" nodeid="1215"&gt;@Hefei Li&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Please check the Kerberos Principals and also the Hostname.  If the Hostname is in correct Case or not?&lt;/P&gt;&lt;P&gt;Sometimes this kind of error occurs if the "/etc/hosts" file has hostname in Mixed Case (LowerCase).&lt;/P&gt;&lt;P&gt;So please check if the NameNode host actually has the Hostname which is reported here "a01-r03-i164-156-515w9ay.xxx.xxx" ?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;.&lt;/P&gt;&lt;P&gt;Also please check if your Keytabs are correctly reflecting the hostname/realm name in proper case.&lt;/P&gt;&lt;PRE&gt;# klist -kte /etc/security/keytabs/hdfs.headless.keytab
# hostname -f
# cat /etc/hosts&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Please check the FQDN / Hostname which is mentioned in the above output matches the HDFS configuration files for the NameNode address. &lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2018 11:45:45 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180326#M73108</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-01-09T11:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start NameNode 403 error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180327#M73109</link>
      <description>&lt;P&gt;I have found the reason for the problem.&lt;/P&gt;&lt;P&gt;I changed the FQDN to lowercase, then it works ok.&lt;/P&gt;&lt;P&gt;Thank you for your reply&lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2018 14:18:34 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180327#M73109</guid>
      <dc:creator>Hefei</dc:creator>
      <dc:date>2018-01-12T14:18:34Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start NameNode 403 error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180328#M73110</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1215/lhfeilaile.html" nodeid="1215"&gt;@Hefei Li&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Wonderful!!!  Good to see that the issue is resolved. &lt;/P&gt;&lt;P&gt;As the issue is resolved, hence it will be also great if you can mark this HCC thread as Answered by clicking on the "Accept" Button on the correct answer. That way other HCC users can quickly find the solution when they encounter the same issue.&lt;/P&gt;&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/1215/lhfeilaile.html" nodeid="1215"&gt;&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Fri, 12 Jan 2018 14:23:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-NameNode-403-error/m-p/180328#M73110</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-01-12T14:23:10Z</dc:date>
    </item>
  </channel>
</rss>

