<?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: Could not connect to Ambari log-on screen in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Could-not-connect-to-Ambari-log-on-screen/m-p/97500#M10956</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Symptoms:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Ambari-server.out logs a warning regarding&lt;STRONG&gt; A HTTP GET&lt;/STRONG&gt; method :&lt;/P&gt;&lt;P&gt;WARNING:&lt;EM&gt; A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.StacksService.getStackVersions(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Fix:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Only after changing &lt;EM&gt;client.threadpool.size.max=&lt;/EM&gt;&lt;STRONG&gt;&lt;EM&gt;&amp;lt;number of cores&amp;gt;&lt;/EM&gt; &lt;/STRONG&gt;in &lt;EM&gt;/etc/ambari-server/conf/&lt;/EM&gt;&lt;EM&gt;ambari.properties&lt;/EM&gt; &lt;/P&gt;&lt;P&gt;to match the number you get from running &lt;STRONG&gt;nproc &lt;/STRONG&gt;on the linux command line&lt;STRONG&gt;, &lt;/STRONG&gt;then restarting Ambari-server, would the &lt;/P&gt;&lt;P&gt;Ambari logon screen show.&lt;/P&gt;&lt;P&gt;At Linux shell command line run&lt;/P&gt;&lt;PRE&gt;  1. [root@SERVERNAME ~]#  nproc&lt;/PRE&gt;&lt;P&gt;                  Write down the number of core resulting from running &lt;STRONG&gt;nproc&lt;/STRONG&gt;. Ex.g:&lt;EM&gt; &lt;STRONG&gt;56&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;PRE&gt;  2.  [root@SERVERNAME ~]#  vi /etc/ambari-server/conf/ambari.properties&lt;/PRE&gt;&lt;STRONG&gt;&lt;/STRONG&gt;&lt;P&gt;                 Find &lt;STRONG&gt;client.threadpool.size.max=&lt;EM&gt;&amp;lt;number of cores&amp;gt;&lt;/EM&gt;,&lt;/STRONG&gt; then change to&lt;STRONG&gt; &lt;/STRONG&gt;&lt;STRONG&gt;client.threadpool.size.max=&lt;EM&gt;56&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;  3.  [root@SERVERNAME ~]#  ambari-server restart
&lt;/PRE&gt;&lt;P&gt;That should resolve this particular issue on on REHL 7.X.&lt;/P&gt;&lt;P&gt;Referencing  &lt;A href="https://issues.apache.org/jira/browse/AMBARI-9776"&gt;AMBARI-9776&lt;/A&gt;;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Nov 2015 22:33:15 GMT</pubDate>
    <dc:creator>adaher</dc:creator>
    <dc:date>2015-11-23T22:33:15Z</dc:date>
    <item>
      <title>Could not connect to Ambari log-on screen</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Could-not-connect-to-Ambari-log-on-screen/m-p/97499#M10955</link>
      <description>&lt;P&gt;During a recent installation at a customer site, on an 8 Node cluster, and after successfully going through the prep stages, and successfully installing and restarting Ambari server, was not able to connect to Ambari log-on screen.  &lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2015 21:49:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Could-not-connect-to-Ambari-log-on-screen/m-p/97499#M10955</guid>
      <dc:creator>adaher</dc:creator>
      <dc:date>2015-11-23T21:49:20Z</dc:date>
    </item>
    <item>
      <title>Re: Could not connect to Ambari log-on screen</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Could-not-connect-to-Ambari-log-on-screen/m-p/97500#M10956</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Symptoms:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Ambari-server.out logs a warning regarding&lt;STRONG&gt; A HTTP GET&lt;/STRONG&gt; method :&lt;/P&gt;&lt;P&gt;WARNING:&lt;EM&gt; A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.StacksService.getStackVersions(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String), should not consume any entity ...&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Fix:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Only after changing &lt;EM&gt;client.threadpool.size.max=&lt;/EM&gt;&lt;STRONG&gt;&lt;EM&gt;&amp;lt;number of cores&amp;gt;&lt;/EM&gt; &lt;/STRONG&gt;in &lt;EM&gt;/etc/ambari-server/conf/&lt;/EM&gt;&lt;EM&gt;ambari.properties&lt;/EM&gt; &lt;/P&gt;&lt;P&gt;to match the number you get from running &lt;STRONG&gt;nproc &lt;/STRONG&gt;on the linux command line&lt;STRONG&gt;, &lt;/STRONG&gt;then restarting Ambari-server, would the &lt;/P&gt;&lt;P&gt;Ambari logon screen show.&lt;/P&gt;&lt;P&gt;At Linux shell command line run&lt;/P&gt;&lt;PRE&gt;  1. [root@SERVERNAME ~]#  nproc&lt;/PRE&gt;&lt;P&gt;                  Write down the number of core resulting from running &lt;STRONG&gt;nproc&lt;/STRONG&gt;. Ex.g:&lt;EM&gt; &lt;STRONG&gt;56&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;PRE&gt;  2.  [root@SERVERNAME ~]#  vi /etc/ambari-server/conf/ambari.properties&lt;/PRE&gt;&lt;STRONG&gt;&lt;/STRONG&gt;&lt;P&gt;                 Find &lt;STRONG&gt;client.threadpool.size.max=&lt;EM&gt;&amp;lt;number of cores&amp;gt;&lt;/EM&gt;,&lt;/STRONG&gt; then change to&lt;STRONG&gt; &lt;/STRONG&gt;&lt;STRONG&gt;client.threadpool.size.max=&lt;EM&gt;56&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;PRE&gt;  3.  [root@SERVERNAME ~]#  ambari-server restart
&lt;/PRE&gt;&lt;P&gt;That should resolve this particular issue on on REHL 7.X.&lt;/P&gt;&lt;P&gt;Referencing  &lt;A href="https://issues.apache.org/jira/browse/AMBARI-9776"&gt;AMBARI-9776&lt;/A&gt;;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Nov 2015 22:33:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Could-not-connect-to-Ambari-log-on-screen/m-p/97500#M10956</guid>
      <dc:creator>adaher</dc:creator>
      <dc:date>2015-11-23T22:33:15Z</dc:date>
    </item>
  </channel>
</rss>

