Hello All, Installed amabari 2.6 , chose all by default pratameters . started server ,when I try to open it via GUI ,It doesnt open. Below is the log .

[#1]

[root@namenode01 ~]# tail -f /var/log/ambari-server/ambari-server.log
19 Jul 2018 17:29:19,641 INFO [main] MetricsRetrievalService:227 - Initializing the Metrics Retrieval Service with core=4, max=8, workerQueue=80, threadPriority=5
19 Jul 2018 17:29:19,641 INFO [main] MetricsRetrievalService:232 - Metrics Retrieval Service request TTL cache is enabled and set to 5 seconds
19 Jul 2018 17:29:19,641 INFO [main] AmbariServer:569 - ********* Started Services **********
19 Jul 2018 17:29:19,642 INFO [main] MetricsServiceImpl:48 - ********* Initializing AmbariServer Metrics Service **********
19 Jul 2018 17:29:19,647 INFO [RetryUpgradeActionService STARTING] RetryUpgradeActionService:121 - Will not start service RetryUpgradeActionService used to auto-retry failed actions during Stack Upgrade since since the property stack.upgrade.auto.retry.timeout.mins is either invalid/missing or set to 0
19 Jul 2018 17:29:19,708 INFO [main] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:29:19,714 INFO [main] AmbariMetricSinkImpl:95 - No clusters configured.
19 Jul 2018 17:29:19,714 INFO [main] MetricsServiceImpl:88 - ********* Configuring Metric Sources **********
19 Jul 2018 17:29:19,734 INFO [main] JvmMetricsSource:63 - Initialized JVM Metrics source...
19 Jul 2018 17:29:19,734 INFO [main] JvmMetricsSource:80 - Started JVM Metrics source...
19 Jul 2018 17:31:19,673 INFO [Thread-23] AbstractPoolBackedDataSource:212 - Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, contextClassLoaderSource -> caller, dataSourceName -> 2xfegy9w1dtv39oruqbmq|6bfc5296, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> org.postgresql.Driver, extensions -> {}, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, forceSynchronousCheckins -> false, forceUseNamedDriverClass -> false, identityToken -> 2xfegy9w1dtv39oruqbmq|6bfc5296, idleConnectionTestPeriod -> 50, initialPoolSize -> 3, jdbcUrl -> jdbc:postgresql://localhost/ambari, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 5, maxStatements -> 0, maxStatementsPerConnection -> 120, minPoolSize -> 1, numHelperThreads -> 3, preferredTestQuery -> select 0, privilegeSpawnedThreads -> false, properties -> {user=******, password=******}, propertyCycle -> 0, statementCacheNumDeferredCloseThreads -> 0, testConnectionOnCheckin -> true, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, userOverrides -> {}, usesTraditionalReflectiveProxies -> false ]
19 Jul 2018 17:31:19,763 INFO [Thread-23] JobStoreTX:861 - Freed 0 triggers from 'acquired' / 'blocked' state.
19 Jul 2018 17:31:19,815 INFO [Thread-23] JobStoreTX:871 - Recovering 0 jobs that were in-progress at the time of the last shut-down.
19 Jul 2018 17:31:19,815 INFO [Thread-23] JobStoreTX:884 - Recovery complete.
19 Jul 2018 17:31:19,816 INFO [Thread-23] JobStoreTX:891 - Removed 0 'complete' triggers.
19 Jul 2018 17:31:19,818 INFO [Thread-23] JobStoreTX:896 - Removed 0 stale fired job entries.
19 Jul 2018 17:31:19,824 INFO [Thread-23] QuartzScheduler:575 - Scheduler ExecutionScheduler_$_NON_CLUSTERED started.
19 Jul 2018 17:34:19,735 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
19 Jul 2018 17:34:19,736 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:34:19,736 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.
19 Jul 2018 17:39:19,737 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
19 Jul 2018 17:39:19,737 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:39:19,737 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.
19 Jul 2018 17:44:19,737 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
19 Jul 2018 17:44:19,738 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:44:19,738 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.
19 Jul 2018 17:49:19,738 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
19 Jul 2018 17:49:19,738 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:49:19,738 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.
19 Jul 2018 17:54:19,739 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
19 Jul 2018 17:54:19,739 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:54:19,739 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.
19 Jul 2018 17:59:19,739 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
19 Jul 2018 17:59:19,739 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
19 Jul 2018 17:59:19,740 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.

[#2]

@shekhar D Can you try and check if your firewall is allowing connections to ambari-server host and port?

telnet  ambariHost  8080

Also check ambari-server status to see if it's running:

ambari-server status

Compare pid of the above command output with the pid in the following:

cat /var/run/ambari-server/ambari-server.pid

[#3]

[root@namenode01 ~]# cat /var/run/ambari-server/ambari-server.pid
5617
[root@namenode01 ~]# ambari-server status
Using python /usr/bin/python
Ambari-server status
Ambari Server running
Found Ambari Server PID: 5617 at: /var/run/ambari-server/ambari-server.pid
[root@namenode01 ~]#

[root@node01 opt]# telnet 35.185.14.14 8080
Trying 35.185.14.14...
telnet: connect to address 35.185.14.14: Connection refused
[root@node01 opt]#

[#4]

@shekhar D as you can see you cannot establish a connection to port 8080, because it's probably being blocked by a firewall.

If you are just testing ambari installation, just disable the firewall in your ambari host:

chkconfig iptables off
chkconfig ip6tables off
service iptables stop
service ip6tables stop

If not please revert to your network administrator to open port 8080 on host 35.185.14.14

[#5]

[root@namenode01 ~]#
login as: root
Server refused our key
root@35.185.14.14's password:
Last login: Fri Jul 20 11:25:48 2018 from 111.93.141.170
[root@namenode01 ~]# chkconfig iptables off
[root@namenode01 ~]# chkconfig ip6tables off
[root@namenode01 ~]# service iptables stop
[root@namenode01 ~]# service ip6tables stop
ip6tables: Setting chains to policy ACCEPT: filter [ OK ]
ip6tables: Flushing firewall rules: [ OK ]
ip6tables: Unloading modules: [ OK ]
[root@namenode01 ~]#

Looks like its a network firewall thing. Will check with network admin and update you all. thanks

[#6]

@shekhar D Let me know if that solved the issue. And if yes please take a moment to login and click "Accept" below the answer.

[#7]

I deleted all vm instances and recreated them. have reinstalled amabari server . All gets installed clean - but doesn't start GUI . port 8080 also I do not see running on Linux .port8080.png..

[#8]

[root@master /]# netstat -ano |grep 8080
tcp 0 0 :::8080 :::* LISTEN off (0.00/0/0)
tcp 0 0 ::1:8080 ::1:57354 TIME_WAIT timewait (37.78/0/0)
[root@master /]#

[#9]

[root@master /]# tail -f /var/log/ambari-server/ambari-server.log
21 Jul 2018 18:36:15,969 INFO [Thread-23] AbstractPoolBackedDataSource:212 - Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, contextClassLoaderSource -> caller, dataSourceName -> 2xfegy9w1gr2b0ktdjw44|c7cbc2d, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> org.postgresql.Driver, extensions -> {}, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, forceSynchronousCheckins -> false, forceUseNamedDriverClass -> false, identityToken -> 2xfegy9w1gr2b0ktdjw44|c7cbc2d, idleConnectionTestPeriod -> 50, initialPoolSize -> 3, jdbcUrl -> jdbc:postgresql://localhost/ambari, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 5, maxStatements -> 0, maxStatementsPerConnection -> 120, minPoolSize -> 1, numHelperThreads -> 3, preferredTestQuery -> select 0, privilegeSpawnedThreads -> false, properties -> {user=******, password=******}, propertyCycle -> 0, statementCacheNumDeferredCloseThreads -> 0, testConnectionOnCheckin -> true, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, userOverrides -> {}, usesTraditionalReflectiveProxies -> false ]
21 Jul 2018 18:36:16,049 INFO [Thread-23] JobStoreTX:861 - Freed 0 triggers from 'acquired' / 'blocked' state.
21 Jul 2018 18:36:16,062 INFO [Thread-23] JobStoreTX:871 - Recovering 0 jobs that were in-progress at the time of the last shut-down.
21 Jul 2018 18:36:16,062 INFO [Thread-23] JobStoreTX:884 - Recovery complete.
21 Jul 2018 18:36:16,063 INFO [Thread-23] JobStoreTX:891 - Removed 0 'complete' triggers.
21 Jul 2018 18:36:16,063 INFO [Thread-23] JobStoreTX:896 - Removed 0 stale fired job entries.
21 Jul 2018 18:36:16,066 INFO [Thread-23] QuartzScheduler:575 - Scheduler ExecutionScheduler_$_NON_CLUSTERED started.
21 Jul 2018 18:39:16,064 INFO [pool-18-thread-1] MetricsServiceImpl:65 - Attempting to initialize metrics sink
21 Jul 2018 18:39:16,065 INFO [pool-18-thread-1] MetricsServiceImpl:81 - ********* Configuring Metric Sink **********
21 Jul 2018 18:39:16,065 INFO [pool-18-thread-1] AmbariMetricSinkImpl:95 - No clusters configured.

[#10]

Since you are trying to open ambari UI from your local system. can u check from ur local if you are able to connect to port 8080

i.e telnet <ambari_host> 8080

[#11]

@shekhar D

Can you ensure you have an entry in your local /etc/hosts for the ambari host the format is?

IP.......FQDN......ALIAS eg

192.168.203.90   ambari.com   ambari

If you have done the installation in AWS make sure you opened the port 8080 restricting it to your IP or open to the world if not production and use the public IP not internal.

HTH