Follow

The Ambari UI page fails to load

Issue

When attempting to access the Ambari UI (http[s]://<AMBARI_NODE_FQDN>:[PORT]) the page fails to load. The error message is as follows:

  • Chrome - This site can't be reached
  • Safari - Safari can't connect to the Server
  • Internet Explorer 11 - Can't reach this page
  • Microsoft Edge - Hmmm…can't reach this page
  • Firefox - The connection has timed out

Cause

This is normally caused by either:

  • Port 8080/8440/8441 being blocked; and/or
  • Ambari-Server daemon not running

Resolution Steps

It is recommended to validate if the Ambari-Server daemon is running, and if the ports are accessible from a system that is not part of the Interset cluster.

Ambari-Server validation

  1. Log on to the AMBARI Node as the Interset user.
  2. Type in the following command to validate if the ambari-server daemon is running:
    • sudo ambari-server status
  3. If the daemon is running, please continue to Port accessibility validation
  4. If the daemon is NOT running, type in the following command to start the daemon:
    • sudo ambari-server start
  5. Once the ambari-server daemon has started, open up a web browser, and navigate to the Ambari UI URL:
    • http(s)://<AMBARI_NODE_FQDN>:<PORT>
  6. If the Ambari UI page still fails to load, please continue to the Port accessibility validation section

Port accessibility validation

NOTE: In order to perform the steps below, telnet must be installed.

  1. Log on to a system that is not part of the Interset cluster.
  2. Type in the following command to telnet to the AMBARI Node and attempt to connect to port 8080/8440/8441:
    • sudo telnet <AMBARI_NODE_FQDN> <PORT>
      • EXAMPLE: sudo telnet ambari.acme.com 8080
  3. If telnet fails to connect, the error message will be outputted as follow:
    • Trying <IP_Address>...
    • telnet: connect to address <IP_Address>: Connection refused
    • telnet: Unable to connect to remote host
  4. The next will be to check if iptables and ip6tables daemon are running.

iptables/ip6tables/firewalld validation

  1. Log on to the AMBARI NODE as the Interset user
  2. Type in the following command to check if iptables/ip6tables/firewalld daemon is running:
    • For EL6:
      • sudo service iptables status
      • sudo service ip6tables status
    • For EL7:
      • sudo systemctl status firewalld
      • sudo systemctl status iptables
  3. If iptables/ip6tables/firewalld is running, type in the following command to stop the daemon(s).
    • NOTE: Please verify with your network security team if this is appropriate
      • For EL6:
        • sudo service iptables stop
        • sudo service ip6tables stop
      • For EL7:
        • sudo systemctl stop firewalld
        • sudo systemctl stop iptables
  4. To prevent this from occurring in the future, iptables/ip6tables/firewalld can be disabled on the Linux systems by typing in the following command:
    • For EL6:
      • sudo chkconfig iptables off
      • sudo chkconfig ip6tables off
    • For EL7:
      • sudo systemctl disable firewalld
      • sudo systemctl disable iptables
  5. Once iptables/ip6tables/firewalld is disabled, it is time to restart the ambari-server to reload its configuration and daemon. Type in the following command to restart the ambari-server:
    • sudo ambari-server restart
  6. Once the ambari-server is restarted, open up a web-browser and navigate to the Ambari UI URL:
  7. If the Ambari UI page loads, log in with the Ambari admin UI. The default credential is:
    • Username: admin
    • Password: admin
  8. Once logged in, some Ambari components (may be all) may need to be restarted (Red Alerts beside the components). In the Ambari UI, click the Actions button, and click Start All

Applies To

  • Interset 5.4.x or higher
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk