<?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: Ambari won't following admin password reset in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185030#M75713</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/62433/wwbrooks.html" nodeid="62433"&gt;@Bill Brooks&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you are worrying about the following error message then it is not to be worried much as sometimes due to slow startup ambari might take more than the default 50 seconds time to be completely Up and running.  So you can ignore the error if you are able to access the ambari. Try accessing ambari server URL. &lt;A href="http://localhost:8080" target="_blank"&gt;http://localhost:8080&lt;/A&gt;.     with the new credentials that you have set &lt;/P&gt;&lt;PRE&gt;ERROR: Exiting with exit code 1.
REASON: Server not yet listening on http port 8080 after 50 seconds.&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Some explanation about this error you can find tin the following thread:  \https://community.hortonworks.com/questions/149848/change-the-port-for-ambari-server.html&lt;/P&gt;&lt;P&gt;So edit the "&lt;STRONG&gt;/etc/ambari-server/conf/ambari.properties&lt;/STRONG&gt;" and increase the following property value to 120 or 150 seconds.&lt;/P&gt;&lt;PRE&gt;server.startup.web.timeout=120 &lt;/PRE&gt;&lt;P&gt;and then hopefully you should not see that error again.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Mar 2018 13:30:14 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2018-03-13T13:30:14Z</dc:date>
    <item>
      <title>Ambari won't following admin password reset</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185029#M75712</link>
      <description>&lt;P&gt;Recently installed sandbox on Docker with Mac OS X as the underlying OS. I'm following the tutorial  "learning the ropes of the hortonworks sandbox". &lt;/P&gt;&lt;P&gt;Here's what I get once I followed the instructions for changing the admin password using the shell web client:&lt;/P&gt;&lt;P&gt;[root@sandbox-hdp ~]# ambari-admin-password-reset&lt;BR /&gt;
Please set the password for admin:&lt;BR /&gt;
Please retype the password for admin:&lt;BR /&gt;
Passwords do not match.  Please try again.&lt;BR /&gt;
&lt;BR /&gt;
Please set the password for admin:&lt;BR /&gt;
Please retype the password for admin:&lt;BR /&gt;
&lt;BR /&gt;
The admin password has been set.&lt;BR /&gt;
Restarting ambari-server to make the password change effective...&lt;BR /&gt;
&lt;BR /&gt;
Using python  /usr/bin/python&lt;BR /&gt;
Restarting ambari-server&lt;BR /&gt;
Waiting for server stop...&lt;BR /&gt;
Ambari Server stopped&lt;BR /&gt;
Ambari Server running with administrator privileges.&lt;BR /&gt;
Organizing resource files at /var/lib/ambari-server/resources...&lt;BR /&gt;
Ambari database consistency check started...&lt;BR /&gt;
Server PID at: /var/run/ambari-server/ambari-server.pid&lt;BR /&gt;
Server out at: /var/log/ambari-server/ambari-server.out&lt;BR /&gt;
Server log at: /var/log/ambari-server/ambari-server.log&lt;BR /&gt;
Waiting for server&lt;BR /&gt;
start............................................................&lt;BR /&gt;
DB configs consistency check: no errors and warnings were found.&lt;BR /&gt;
ERROR: Exiting with exit code 1.&lt;BR /&gt;
REASON: Server not yet listening on http port 8080 after 50 seconds.&lt;BR /&gt;
Exiting.&lt;BR /&gt;
[root@sandbox-hdp ~]#&lt;/P&gt;&lt;P&gt;...what is the next logical troubleshooting step to get the ambari server to start?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Mar 2018 13:14:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185029#M75712</guid>
      <dc:creator>cloudbringer</dc:creator>
      <dc:date>2018-03-13T13:14:57Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari won't following admin password reset</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185030#M75713</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/62433/wwbrooks.html" nodeid="62433"&gt;@Bill Brooks&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If you are worrying about the following error message then it is not to be worried much as sometimes due to slow startup ambari might take more than the default 50 seconds time to be completely Up and running.  So you can ignore the error if you are able to access the ambari. Try accessing ambari server URL. &lt;A href="http://localhost:8080" target="_blank"&gt;http://localhost:8080&lt;/A&gt;.     with the new credentials that you have set &lt;/P&gt;&lt;PRE&gt;ERROR: Exiting with exit code 1.
REASON: Server not yet listening on http port 8080 after 50 seconds.&lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Some explanation about this error you can find tin the following thread:  \https://community.hortonworks.com/questions/149848/change-the-port-for-ambari-server.html&lt;/P&gt;&lt;P&gt;So edit the "&lt;STRONG&gt;/etc/ambari-server/conf/ambari.properties&lt;/STRONG&gt;" and increase the following property value to 120 or 150 seconds.&lt;/P&gt;&lt;PRE&gt;server.startup.web.timeout=120 &lt;/PRE&gt;&lt;P&gt;and then hopefully you should not see that error again.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Mar 2018 13:30:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185030#M75713</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-03-13T13:30:14Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari won't following admin password reset</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185031#M75714</link>
      <description>&lt;P&gt;&lt;EM&gt;@&lt;A href="https://community.hortonworks.com/users/62433/wwbrooks.html"&gt;Bill Brooks&lt;/A&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;That error is due to the timeout setting you can alter that by adding the&lt;STRONG&gt; server.startup.web.timeout&lt;/STRONG&gt; property (measured in seconds) to &lt;STRONG&gt;/etc/ambari-server/conf/ambari.properties&lt;/STRONG&gt; you can change the timeout to something like this:&lt;/EM&gt;&lt;/P&gt;&lt;PRE&gt;server.startup.web.timeout=120&lt;/PRE&gt;&lt;P&gt;&lt;EM&gt;Incidentally, the ambari could be accessible  have you tried accessing the  &lt;STRONG&gt;&lt;A href="http://ambari-server:8080" target="_blank"&gt;http://ambari-server:8080&lt;/A&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Mar 2018 13:38:08 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185031#M75714</guid>
      <dc:creator>Shelton</dc:creator>
      <dc:date>2018-03-13T13:38:08Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari won't following admin password reset</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185032#M75715</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/62433/wwbrooks.html" nodeid="62433"&gt;@Bill Brooks&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Hello, if this is still an issue at this time, could you please pastebin the logs from /var/log/ambari-server? &lt;/P&gt;</description>
      <pubDate>Tue, 13 Mar 2018 17:02:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185032#M75715</guid>
      <dc:creator>glupu</dc:creator>
      <dc:date>2018-03-13T17:02:56Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari won't following admin password reset</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185033#M75716</link>
      <description>&lt;P&gt;This may have worked on a previous version, but I am running the sandbox on virtualbox, HDP 2.6.4 and I wasn't able to find a property 'server.startup.web.timeout' in the configuration file &lt;EM&gt;&lt;STRONG&gt;/etc/ambari-server/conf/ambari.properties&lt;/STRONG&gt;&lt;/EM&gt; to set to a higher value. &lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Mar 2018 11:16:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185033#M75716</guid>
      <dc:creator>cloudbringer</dc:creator>
      <dc:date>2018-03-14T11:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari won't following admin password reset</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185034#M75717</link>
      <description>&lt;P&gt;The provided answer above was correct, the server eventually started successfully.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Mar 2018 11:22:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-won-t-following-admin-password-reset/m-p/185034#M75717</guid>
      <dc:creator>cloudbringer</dc:creator>
      <dc:date>2018-03-14T11:22:27Z</dc:date>
    </item>
  </channel>
</rss>

