<?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: Not able to start Resource Manager using amabri but able to start using cli in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Not-able-to-start-Resource-Manager-using-amabri-but-able-to/m-p/344523#M234194</link>
    <description>&lt;P&gt;I solved this by adding value as * in Hadoop.proxy.user.host in hdfs-core-site.xml&lt;/P&gt;</description>
    <pubDate>Thu, 26 May 2022 10:00:04 GMT</pubDate>
    <dc:creator>KPG1</dc:creator>
    <dc:date>2022-05-26T10:00:04Z</dc:date>
    <item>
      <title>Not able to start Resource Manager using amabri but able to start using cli</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Not-able-to-start-Resource-Manager-using-amabri-but-able-to/m-p/332979#M231329</link>
      <description>&lt;P&gt;I am facing an issue while starting resource manager using ambari but able to start it using CLI.&lt;/P&gt;&lt;P&gt;when starting using ambari no logs is generated in /var/log/haoop-yarn/ location.&lt;/P&gt;&lt;P&gt;Please find logs on ambari.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Traceback (most recent call last):&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 995, in restart&lt;BR /&gt;self.status(env)&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py", line 150, in status&lt;BR /&gt;check_process_status(status_params.resourcemanager_pid_file)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/check_process_status.py", line 43, in check_process_status&lt;BR /&gt;raise ComponentIsNotRunning()&lt;BR /&gt;ComponentIsNotRunning&lt;/P&gt;&lt;P&gt;The above exception was the cause of the following exception:&lt;/P&gt;&lt;P&gt;Traceback (most recent call last):&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py", line 261, in &amp;lt;module&amp;gt;&lt;BR /&gt;Resourcemanager().execute()&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 352, in execute&lt;BR /&gt;method(env)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 1006, in restart&lt;BR /&gt;self.start(env, upgrade_type=upgrade_type)&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py", line 135, in start&lt;BR /&gt;self.configure(env) # FOR SECURITY&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/resourcemanager.py", line 62, in configure&lt;BR /&gt;yarn(name='resourcemanager')&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89, in thunk&lt;BR /&gt;return fn(*args, **kwargs)&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/yarn.py", line 369, in yarn&lt;BR /&gt;setup_atsv2_backend(name,config_dir)&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/yarn.py", line 637, in setup_atsv2_backend&lt;BR /&gt;setup_system_services(config_dir)&lt;BR /&gt;File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/yarn.py", line 769, in setup_system_services&lt;BR /&gt;group=params.user_group&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166, in __init__&lt;BR /&gt;self.env.run()&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 160, in run&lt;BR /&gt;self.run_action(resource, action)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line 124, in run_action&lt;BR /&gt;provider_action()&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 677, in action_create_on_execute&lt;BR /&gt;self.action_delayed("create")&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 674, in action_delayed&lt;BR /&gt;self.get_hdfs_resource_executor().action_delayed(action_name, self)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 373, in action_delayed&lt;BR /&gt;self.action_delayed_for_nameservice(None, action_name, main_resource)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 403, in action_delayed_for_nameservice&lt;BR /&gt;self._create_resource()&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 419, in _create_resource&lt;BR /&gt;self._create_file(self.main_resource.resource.target, source=self.main_resource.resource.source, mode=self.mode)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 534, in _create_file&lt;BR /&gt;self.util.run_command(target, 'CREATE', method='PUT', overwrite=True, assertable_result=False, file_to_put=source, **kwargs)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 214, in run_command&lt;BR /&gt;return self._run_command(*args, **kwargs)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py", line 282, in _run_command&lt;BR /&gt;_, out, err = get_user_call_output(cmd, user=self.run_user, logoutput=self.logoutput, quiet=False)&lt;BR /&gt;File "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/get_user_call_output.py", line 62, in get_user_call_output&lt;BR /&gt;raise ExecutionFailed(err_msg, code, files_output[0], files_output[1])&lt;BR /&gt;resource_management.core.exceptions.ExecutionFailed: Execution of 'curl -sS -L -w '%{http_code}' -X PUT --data-binary @/usr/hdp/3.1.0.0-78/hadoop/conf/core-site.xml -H 'Content-Type: application/octet-stream' '&lt;A href="http://masternode:50070/webhdfs/v1/user/yarn-ats/3.1.0.0-78/core-site.xml?op=CREATE&amp;amp;user.name=hdfs&amp;amp;overwrite=True" target="_blank" rel="noopener"&gt;http://masternode:50070/webhdfs/v1/user/yarn-ats/3.1.0.0-78/core-site.xml?op=CREATE&amp;amp;user.name=hdfs&amp;amp;overwrite=True&lt;/A&gt;' 1&amp;gt;/tmp/tmpTdj1DW 2&amp;gt;/tmp/tmpJ4DHHk' returned 52. curl: (52) Empty reply from server&lt;BR /&gt;100&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Dec 2021 05:54:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Not-able-to-start-Resource-Manager-using-amabri-but-able-to/m-p/332979#M231329</guid>
      <dc:creator>KPG1</dc:creator>
      <dc:date>2021-12-30T05:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: Not able to start Resource Manager using amabri but able to start using cli</title>
      <link>https://community.cloudera.com/t5/Support-Questions/Not-able-to-start-Resource-Manager-using-amabri-but-able-to/m-p/344523#M234194</link>
      <description>&lt;P&gt;I solved this by adding value as * in Hadoop.proxy.user.host in hdfs-core-site.xml&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 10:00:04 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/Not-able-to-start-Resource-Manager-using-amabri-but-able-to/m-p/344523#M234194</guid>
      <dc:creator>KPG1</dc:creator>
      <dc:date>2022-05-26T10:00:04Z</dc:date>
    </item>
  </channel>
</rss>

