ambari URL not working

[#1]

We have HDP 2.6.4

Ambari URL is not loading

sudo ambari-server status

Using python /usr/bin/python

Ambari-server status

Ambari Server running

Found Ambari Server PID: 14654 at: /var/ambari-server/ambari-server.pid

01 Aug 2018 19:08:53,866 ERROR [ambari-client-thread-1088676] MetricsRequestHelper:115 - Error getting timeline metrics : Connection refused (Connection refused) 01 Aug 2018 19:08:53,867 ERROR [ambari-client-thread-1088676] MetricsRequestHelper:122 - Cannot connect to collector: SocketTimeoutException for ctcl-hdpedge1.msoit.com

01 Aug 2018 19:08:46,391 ERROR [ambari-client-thread-1088525] MetricsRequestHelper:122 - Cannot connect to collector: SocketTimeoutException for ctcl-hdpedge1.msoit.com 01 Aug 2018 19:08:53,867 ERROR [ambari-client-thread-1088676] MetricsRequestHelper:122 - Cannot connect to collector: SocketTimeoutException for ctcl-hdpedge1.msoit.com

[#2]

@vishal dutt

Have you tried restarting the ambari-server and agents !

First, stop the ambari-server and agent

# ambari-server stop
#ambari-agent stop

As the root user change the following session related parameters

##################################################
# Change the timeout of the ambari server
##################################################
echo 'server.startup.web.timeout=120' >> /etc/ambari-server/conf/ambari.properties
echo 'server.jdbc.connection-pool.acquisition-size=5' >> /etc/ambari-server/conf/ambari.properties
echo 'server.jdbc.connection-pool.max-age=0' >> /etc/ambari-server/conf/ambari.properties
echo 'server.jdbc.connection-pool.max-idle-time=14400' >> /etc/ambari-server/conf/ambari.properties
echo 'server.jdbc.connection-pool.max-idle-time-excess=0' >> /etc/ambari-server/conf/ambari.properties
echo 'server.jdbc.connection-pool.idle-test-interval=7200' >> /etc/ambari-server/conf/ambari.properties

Then

# ambari-server start
# ambari-agent start

Monitor and revert

[#3]

Thanks

Amabri URL is up and running.We did not do anything

[#4]

@vishal dutt

The error that you mentioned as following:

MetricsRequestHelper:122 - Cannot connect to collector: SocketTimeoutException for xxx.com 
MetricsRequestHelper:122 - Cannot connect to collector: SocketTimeoutException for xxx.com

.

Above error can be commonly seen in ambari server log when the Ambari Metrics Collector process can not be reached from ambari server host. It mostly happens when the Ambari Metrics Collector goes down (may be some tuning is needed at AMS side). So when the AMS collector is down that time ambari will not be able to communicate with it hence you might see the above kind of error in amabri-server.log.

But as by default the AMS "Service Auto restart" Feature is enabled by default hence when ambari will notice that the AMS collector is down then it will automatically start the AMS collector hence the Error related to Cannot connect will disappear from the ambari server log.

https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-operations/content/enable_service...

.

If you really want to find the root cause to know why the AMS was went down then it might require some AMS troubleshooting & tuning.

https://cwiki.apache.org/confluence/display/AMBARI/Configurations+-+Tuning

.