<?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: cant start Standby NameNode in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197127#M73830</link>
    <description>&lt;P&gt;can I run like - &lt;STRONG&gt;hdfs namenode -bootstrap.... on the active node , if yes then what is the complete syntax ? &lt;BR /&gt;  &lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jan 2018 06:42:17 GMT</pubDate>
    <dc:creator>mike_bronson7</dc:creator>
    <dc:date>2018-01-25T06:42:17Z</dc:date>
    <item>
      <title>cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197121#M73824</link>
      <description>&lt;P&gt;we are trying to start the Standby NameNode on master03 machines but withou success&lt;/P&gt;&lt;P&gt;from the error log we can see the follwing&lt;/P&gt;&lt;P&gt;but we cant capture what is the problem , please advice what chuld be the reason that namenode not started according to the follwing log &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 424, in &amp;lt;module&amp;gt;
    NameNode().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 314, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py", line 100, 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 167, in namenode
    create_log_dir=True
  File "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py", line 271, in service
    Execute(daemon_cmd, not_if=process_id_exists_command, environment=hadoop_env_exports)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 155, 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/core/providers/system.py", line 262, in action_run
    tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 72, in inner
    result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 102, in checked_call
    tries=tries, try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 150, in _call_wrapper
    result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 303, in _call
    raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'ambari-sudo.sh su hdfs -l -s /bin/bash -c 'ulimit -c unlimited ;  /usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh --config /usr/hdp/current/hadoop-client/conf start namenode'' returned 1. starting namenode, logging to /var/log/hadoop/hdfs/hadoop-hdfs-namenode-master03.sys57.com.out&lt;/PRE&gt;</description>
      <pubDate>Wed, 24 Jan 2018 22:04:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197121#M73824</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-01-24T22:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197122#M73825</link>
      <description>&lt;P&gt;when I run it alone we get - &lt;/P&gt;&lt;PRE&gt; su hdfs -l -s /bin/bash -c 'ulimit -c unlimited ;  /usr/hdp/current/hadoop-client/sbin/hadoop-daemon.sh --config /usr/hdp/current/hadoop-client/conf start namenode'
starting namenode, logging to /var/log/hadoop/hdfs/hadoop-hdfs-namenode-master03.sys57.com.out
echo $?
1&lt;/PRE&gt;</description>
      <pubDate>Wed, 24 Jan 2018 22:38:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197122#M73825</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-01-24T22:38:36Z</dc:date>
    </item>
    <item>
      <title>Re: cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197123#M73826</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If this error is somewhat related to the other thread that you posted recently: &lt;A href="https://community.hortonworks.com/questions/168750/ambari-cluster-no-valid-image-files-found.html?childToView=168771#answer-168771" target="_blank"&gt;https://community.hortonworks.com/questions/168750/ambari-cluster-no-valid-image-files-found.html?childToView=168771#answer-168771&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Then please apply the same solution and close one of the thread.&lt;/P&gt;&lt;P&gt;Pasting the steps here:&lt;/P&gt;&lt;P&gt;Please check if the &lt;STRONG&gt;dfs.namenode.name.dir&lt;/STRONG&gt; (default path: /hadoop/hdfs/namenode) directory is empty by any chance, due to disk issue the files are not present there.
&lt;/P&gt;&lt;P&gt;If this is the case and the Active NameNode is already running (this must be true) then you can try the following:&lt;BR /&gt;&lt;BR /&gt;Try running the following command:&lt;/P&gt;&lt;PRE&gt;# su - hdfs 
# hdfs namenode -bootstrapStandby &amp;lt;br&amp;gt;&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;NOTE: &lt;/STRONG&gt;Please
 run this command ONLY on Standby NameNode. DO NOT run this command on 
Active NameNode. This command will try to recover all metadata on 
Standby NameNode. &lt;BR /&gt;.&lt;/P&gt;&lt;P&gt;- Now try to start Standby NameNode from Ambari&lt;BR /&gt;- Also please Restart ZKFailoverController from Ambari&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 05:09:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197123#M73826</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-01-25T05:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197124#M73827</link>
      <description>&lt;P&gt;@jay I run the &lt;STRONG&gt;hdfs namenode -bootstrapStandby &lt;/STRONG&gt;on stand by but I get&lt;/P&gt;&lt;P&gt;Retrying connect to server: master01.sys57.com/100.4.3.21:8020. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS)&lt;/P&gt;&lt;P&gt;and that because both name node are down - I can start the name node on both machines&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 05:29:19 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197124#M73827</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-01-25T05:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197125#M73828</link>
      <description>&lt;P&gt;@Jay so how to connue from this step? &lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 05:39:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197125#M73828</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-01-25T05:39:43Z</dc:date>
    </item>
    <item>
      <title>Re: cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197126#M73829</link>
      <description>&lt;P&gt;One NN should be active to run the bootstrap command. you need to bring the healthy NN up and running first.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 06:32:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197126#M73829</guid>
      <dc:creator>sandyy006</dc:creator>
      <dc:date>2018-01-25T06:32:37Z</dc:date>
    </item>
    <item>
      <title>Re: cant start Standby NameNode</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197127#M73830</link>
      <description>&lt;P&gt;can I run like - &lt;STRONG&gt;hdfs namenode -bootstrap.... on the active node , if yes then what is the complete syntax ? &lt;BR /&gt;  &lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 06:42:17 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cant-start-Standby-NameNode/m-p/197127#M73830</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-01-25T06:42:17Z</dc:date>
    </item>
  </channel>
</rss>

