Ambari won't following admin password reset

[#1]

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".

Here's what I get once I followed the instructions for changing the admin password using the shell web client:

[root@sandbox-hdp ~]# ambari-admin-password-reset
Please set the password for admin:
Please retype the password for admin:
Passwords do not match. Please try again.

Please set the password for admin:
Please retype the password for admin:

The admin password has been set.
Restarting ambari-server to make the password change effective...

Using python /usr/bin/python
Restarting ambari-server
Waiting for server stop...
Ambari Server stopped
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server
start............................................................
DB configs consistency check: no errors and warnings were found.
ERROR: Exiting with exit code 1.
REASON: Server not yet listening on http port 8080 after 50 seconds.
Exiting.
[root@sandbox-hdp ~]#

...what is the next logical troubleshooting step to get the ambari server to start?

[#2]

@Bill Brooks

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. http://localhost:8080. with the new credentials that you have set

ERROR: Exiting with exit code 1.
REASON: Server not yet listening on http port 8080 after 50 seconds.

.

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

So edit the "/etc/ambari-server/conf/ambari.properties" and increase the following property value to 120 or 150 seconds.

server.startup.web.timeout=120 

and then hopefully you should not see that error again.

[#3 · Accepted solution]

@Bill Brooks

That error is due to the timeout setting you can alter that by adding the server.startup.web.timeout property (measured in seconds) to /etc/ambari-server/conf/ambari.properties you can change the timeout to something like this:

server.startup.web.timeout=120

Incidentally, the ambari could be accessible have you tried accessing the http://ambari-server:8080

[#4]

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 /etc/ambari-server/conf/ambari.properties to set to a higher value.

[#5]

@Bill Brooks

Hello, if this is still an issue at this time, could you please pastebin the logs from /var/log/ambari-server?

[#6]

The provided answer above was correct, the server eventually started successfully.