Support Questions
Find answers, ask questions, and share your expertise

ambari web ui not accessible

Highlighted

ambari web ui not accessible

Explorer

I have started ambari server but when i open ambari web ui it shows me connection time out .

I ran telnet command :

telnet ambari_ipaddress 8080

trying ....

telnet: connect to address Connection timed out

I am beginner to hadoop please help me out

Thanks in advance

3 REPLIES 3
Highlighted

Re: ambari web ui not accessible

Super Mentor

@Shyam Mishra

1. Please check if the ambari server started successfully or not? Check the ambari-server logs for any error. If any errors found then please share the logs.

# less /var/log/ambari-server/ambari-server.log

2. After restartign ambari-server please check if the default ambari port 8080 is opened properly or not?

# netstat -tnlpa | grep 8080
(OR)
# netstat -tnlpa | grep $AMBARI_PID

3. Also please check if the firewall/iptables disabled on the ambari server host or not?

# service iptables status
# service iptables stop

.

Now try to do telnet from the Client machine and try opening browser to connect to ambari.

# telnet Ambari_IP_Address 8080
AND
# telnet Ambari_Hostname 8080

.

Re: ambari web ui not accessible

Explorer

@Jay Kumar SenSharma

Qorg/apache/ambari/server/controller/AmbariServer.class class in file:/usr/lib/ambari-server/ambari-server-2.6.0.0.267.jar!/org/apache/ambari/server/controller/AmbariServer.class 05 Jan 2018 05:06:29,311 INFO [main] Configuration:3048 - Reading password from existing file 05 Jan 2018 05:06:29,320 INFO [main] Configuration:3542 - Hosts Mapping File null 05 Jan 2018 05:06:29,321 INFO [main] HostsMap:60 - Using hostsmap file null 05 Jan 2018 05:06:29,793 INFO [main] ControllerModule:224 - Detected POSTGRES as the database type from the JDBC URL 05 Jan 2018 05:06:29,842 INFO [main] ControllerModule:545 - Searching package org.apache.ambari.server for annotations matching [interface org.apache.ambari.server.EagerSingleton, interface org.apache.ambari.server.StaticallyInject, interface org.apache.ambari.server.AmbariService] 05 Jan 2018 05:06:30,128 INFO [main] ClasspathScannerUtils:54 - Checking package [org.apache.ambari.server] for binding candidates. 05 Jan 2018 05:06:30,664 INFO [main] ControllerModule:587 - Registering service class org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService 05 Jan 2018 05:06:30,671 INFO [main] ControllerModule:587 - Registering service class org.apache.ambari.server.state.services.AlertNoticeDispatchService 05 Jan 2018 05:06:30,673 INFO [main] ControllerModule:587 - Registering service class org.apache.ambari.server.state.services.AmbariServerAlertService 05 Jan 2018 05:06:30,674 INFO [main] ControllerModule:587 - Registering service class org.apache.ambari.server.state.services.CachedAlertFlushService 05 Jan 2018 05:06:30,827 INFO [main] ControllerModule:587 - Registering service class org.apache.ambari.server.state.services.MetricsRetrievalService 05 Jan 2018 05:06:30,829 INFO [main] ControllerModule:587 - Registering service class org.apache.ambari.server.state.services.RetryUpgradeActionService 05 Jan 2018 05:06:30,849 INFO [main] ControllerModule:615 - Searching package org.apache.ambari.server.notifications.dispatchers for dispatchers matching interface org.apache.ambari.server.notifications.NotificationDispatcher 05 Jan 2018 05:06:30,930 INFO [main] ControllerModule:655 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher 05 Jan 2018 05:06:30,937 INFO [main] ControllerModule:655 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher 05 Jan 2018 05:06:30,944 INFO [main] ControllerModule:655 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher 05 Jan 2018 05:06:30,945 INFO [main] ControllerModule:655 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AmbariSNMPDispatcher 05 Jan 2018 05:06:30,946 INFO [main] ControllerModule:679 - Searching package org.apache.ambari.server.checks for classes matching class org.apache.ambari.server.checks.AbstractCheckDescriptor 05 Jan 2018 05:06:31,111 INFO [main] ControllerModule:715 - Registered pre-upgrade check class org.apache.ambari.server.checks.HostsMasterMaintenanceCheck 05 Jan 2018 05:06:31,111 INFO [main] ControllerModule:715 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesMaintenanceModeCheck

tcp6 0 0 :::8080 :::* LISTEN 2710/java

service iptables status :

● iptables.service - IPv4 firewall with iptables Loaded: loaded (/usr/lib/systemd/system/iptables.service; disabled; vendor preset: disabled) Active: inactive (dead)

[root@namenode ~]# telnet 104.197.146.171 8080 Trying 104.197.146.171... telnet: connect to address 104.197.146.171: Connection timed out

[root@namenode ~]# telnet namenode.c.famous-augury-181309.internal 8080 Trying 10.128.0.2... Connected to namenode.c.famous-augury-181309.internal. Escape character is '^]'.

nOte : I am using google cloud platfrom vm instance to install cluster.

[root@namenode ~]# telnet namenode.c.famous-augury-181309.internal 8080 Trying 10.128.0.2... Connected to namenode.c.famous-augury-181309.internal. Escape character is '^]'.

if i open ambari web ui replacing ip address with hostname it shows :

This site can’t be reached

namenode.c.famous-augury-181309.internal’s server IP address could not be found.

ERR_NAME_NOT_RESOLVED

Highlighted

Re: ambari web ui not accessible

Super Mentor

@Shyam Mishra

Are you sure that all your cluster nodes and Ambari servers are on the same Network? Or their IPAddress and Hostname mappings are correct?

- I see that your NameNode address is 10.128.0.2 but your Ambari server address is completely in a different range "104.197.146.171" is that intentional or by mistake it is mapped to an incorrect address?

- Also please check the FQDN of your every host including ambari-server is correct and is being resolved properly from other Agent machines.

# hostname -f
# cat /etc/hosts

.

Please make sure that the "/etc/hosts" file mapping on all hosts are correct (means has correct IP Address and Hostname combination). And the Hostname (FQDN) is correct (hostname -f) as we expect.

.