Unable to connect to server error while logging from Ambari console as admin

[#1]

Hi im getting the below error while i try to login as admin user id from ambari console. It was working fine till yesterday. Today i tried to login it was not. Restarted ambari server few times and does not help. No firewall or nothing in between. port 8080 was in listening state once i start my ambari server. All iptables / selinux are disabled only. Cleared all cache and history from the browser and tried with no luck (IE and Firefox) Kindly help if anything else can be checked to fix the issue?

" Unable to connect to Ambari Server. Confirm Ambari Server is running and you can reach Ambari Server from this machine. "

Ambari-server logambari-dev-login-error.png

06 Oct 2016 13:10:55,347  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HIVE_SERVER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:10:55,359  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component MYSQL_SERVER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:10:55,365  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HIVE_METASTORE on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:10:55,371  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component WEBHCAT_SERVER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:10:55,383  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component NODEMANAGER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:04,786  INFO [main] AbstractConnector:338 - Started SelectChannelConnector@0.0.0.0:8080
06 Oct 2016 13:11:04,786  INFO [main] Server:272 - jetty-8.1.17.v20150415
06 Oct 2016 13:11:06,639  INFO [main] SslContextFactory:300 - Enabled Protocols [SSLv2Hello, TLSv1, TLSv1.1, TLSv1.2] of [SSLv2Hello, SSLv3, TLSv1, TLSv1.1, TLSv1.2]
06 Oct 2016 13:11:06,645  INFO [main] AbstractConnector:338 - Started SslSelectChannelConnector@0.0.0.0:8440
06 Oct 2016 13:11:06,663  INFO [main] SslContextFactory:300 - Enabled Protocols [SSLv2Hello, TLSv1, TLSv1.1, TLSv1.2] of [SSLv2Hello, SSLv3, TLSv1, TLSv1.1, TLSv1.2]
06 Oct 2016 13:11:06,667  INFO [main] AbstractConnector:338 - Started SslSelectChannelConnector@0.0.0.0:8441
06 Oct 2016 13:11:06,667  INFO [main] AmbariServer:539 - ********* Started Server **********
06 Oct 2016 13:11:06,667  INFO [main] ActionManager:77 - Starting scheduler thread
06 Oct 2016 13:11:06,667  INFO [main] ServerActionExecutor:138 - Starting Server Action Executor thread...
06 Oct 2016 13:11:06,669  INFO [main] ServerActionExecutor:165 - Server Action Executor thread started.
06 Oct 2016 13:11:06,669  INFO [main] AmbariServer:542 - ********* Started ActionManager **********
06 Oct 2016 13:11:06,669  INFO [main] ExecutionScheduleManager:201 - Starting scheduler
06 Oct 2016 13:11:06,715  INFO [main] MLog:80 - MLog clients using log4j logging.
06 Oct 2016 13:11:06,777  INFO [main] C3P0Registry:204 - Initializing c3p0-0.9.1.1 [built 15-March-2007 01:32:31; debug? true; trace: 10]
06 Oct 2016 13:11:06,801  INFO [main] StdSchedulerFactory:1184 - Using default implementation for ThreadExecutor
06 Oct 2016 13:11:06,815  INFO [main] SchedulerSignalerImpl:61 - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
06 Oct 2016 13:11:06,815  INFO [main] QuartzScheduler:240 - Quartz Scheduler v.2.2.1 created.
06 Oct 2016 13:11:06,816  INFO [main] JobStoreTX:670 - Using thread monitor-based data access locking (synchronization).
06 Oct 2016 13:11:06,816  INFO [main] JobStoreTX:59 - JobStoreTX initialized.
06 Oct 2016 13:11:06,817  INFO [main] QuartzScheduler:305 - Scheduler meta-data: Quartz Scheduler (v2.2.1) 'ExecutionScheduler' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 5 threads.
  Using job-store 'org.quartz.impl.jdbcjobstore.JobStoreTX' - which supports persistence. and is not clustered.

06 Oct 2016 13:11:06,817  INFO [main] StdSchedulerFactory:1339 - Quartz scheduler 'ExecutionScheduler' initialized from an externally provided properties instance.
06 Oct 2016 13:11:06,817  INFO [main] StdSchedulerFactory:1343 - Quartz scheduler version: 2.2.1
06 Oct 2016 13:11:06,818  INFO [main] QuartzScheduler:2311 - JobFactory set to: org.apache.ambari.server.state.scheduler.GuiceJobFactory@3d73f2a1
06 Oct 2016 13:11:06,818  INFO [main] AmbariServer:545 - ********* Started Scheduled Request Manager **********
06 Oct 2016 13:11:06,822  INFO [main] AmbariServer:548 - ********* Started Services **********
06 Oct 2016 13:11:06,851  INFO [AmbariServerAlertService] AmbariServerAlertService:257 - Scheduled server alert ambari_server_agent_heartbeat to run every 2 minutes
06 Oct 2016 13:11:52,489  WARN [qtp-ambari-agent-51] SecurityFilter:103 - Request https://ip-172-27-3-42.ap-southeast-1.compute.internal:8440/ca doesn't match any pattern.
06 Oct 2016 13:11:52,489  WARN [qtp-ambari-agent-51] SecurityFilter:62 - This request is not allowed on this port: https://ip-172-27-3-42.ap-southeast-1.compute.internal:8440/ca
06 Oct 2016 13:11:53,101  INFO [qtp-ambari-agent-51] HeartBeatHandler:927 - agentOsType = redhat7
06 Oct 2016 13:11:53,153  INFO [qtp-ambari-agent-51] HostImpl:285 - Received host registration, host=[hostname=ip-172-27-3-43,fqdn=ip-172-27-3-43.ap-southeast-1.compute.internal,domain=ap-southeast-1.compute.internal,architecture=x86_64,processorcount=8,physicalprocessorcount=8,osname=redhat,osversion=7.2,osfamily=redhat,memory=62450636,uptime_hours=3908,mounts=(available=2979420,mountpoint=/,used=17979792,percent=86%,size=20959212,device=/dev/xvda2,type=xfs)(available=31333092,mountpoint=/dev,used=0,percent=0%,size=31333092,device=devtmpfs,type=devtmpfs)(available=31225316,mountpoint=/dev/shm,used=0,percent=0%,size=31225316,device=tmpfs,type=tmpfs)(available=30856168,mountpoint=/run,used=369148,percent=2%,size=31225316,device=tmpfs,type=tmpfs)(available=1824350156,mountpoint=/data0,used=667996,percent=1%,size=1922709696,device=/dev/xvdb,type=ext4)(available=1824365240,mountpoint=/data1,used=652912,percent=1%,size=1922709696,device=/dev/xvdc,type=ext4)(available=1824365112,mountpoint=/data2,used=653040,percent=1%,size=1922709696,device=/dev/xvdd,type=ext4)(available=1820131272,mountpoint=/data3,used=4886880,percent=1%,size=1922709696,device=/dev/xvde,type=ext4)(available=1824365244,mountpoint=/data4,used=652908,percent=1%,size=1922709696,device=/dev/xvdf,type=ext4)(available=1824365232,mountpoint=/data5,used=652920,percent=1%,size=1922709696,device=/dev/xvdg,type=ext4)(available=6245064,mountpoint=/run/user/0,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)(available=6245064,mountpoint=/run/user/1009,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)(available=6245064,mountpoint=/run/user/1002,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)]
, registrationTime=1475730713101, agentVersion=2.2.1.0
06 Oct 2016 13:11:53,183  INFO [qtp-ambari-agent-51] TopologyManager:646 - TopologyManager.replayRequests: Entering
06 Oct 2016 13:11:53,183  INFO [qtp-ambari-agent-51] TopologyManager:316 - TopologyManager.onHostRegistered: Entering
06 Oct 2016 13:11:53,184  INFO [qtp-ambari-agent-51] TopologyManager:318 - TopologyManager.onHostRegistered: host = ip-172-27-3-43.ap-southeast-1.compute.internal is already associated with the cluster or is currently being processed
06 Oct 2016 13:11:53,274  INFO [qtp-ambari-agent-51] HeartBeatHandler:994 - Recovery configuration set to RecoveryConfig{, type=AUTO_START, maxCount=6, windowInMinutes=60, retryGap=5, maxLifetimeCount=1024, disabledComponents=, enabledComponents=METRICS_COLLECTOR}
06 Oct 2016 13:11:55,609  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:154 - Heartbeat lost from host ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,610  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component METRICS_MONITOR on ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,611  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component DATANODE on ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,612  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component NODEMANAGER on ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,641  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:154 - Heartbeat lost from host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,641  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component METRICS_MONITOR on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,642  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component DATANODE on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,643  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HIVE_SERVER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,644  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component MYSQL_SERVER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,644  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component HIVE_METASTORE on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,645  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component WEBHCAT_SERVER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:11:55,647  WARN [ambari-hearbeat-monitor] HeartbeatMonitor:169 - Setting component state to UNKNOWN for component NODEMANAGER on ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,972  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component METRICS_MONITOR of service AMBARI_METRICS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,974  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component METRICS_COLLECTOR of service AMBARI_METRICS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,976  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component ZOOKEEPER_SERVER of service ZOOKEEPER of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,979  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component SECONDARY_NAMENODE of service HDFS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,982  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component HISTORYSERVER of service MAPREDUCE2 of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,985  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component NAMENODE of service HDFS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,991  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component APP_TIMELINE_SERVER of service YARN of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:03,994  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component RESOURCEMANAGER of service YARN of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-43.ap-southeast-1.compute.internal
06 Oct 2016 13:12:05,548  WARN [qtp-ambari-agent-52] SecurityFilter:103 - Request https://ip-172-27-3-42.ap-southeast-1.compute.internal:8440/ca doesn't match any pattern.
06 Oct 2016 13:12:05,548  WARN [qtp-ambari-agent-52] SecurityFilter:62 - This request is not allowed on this port: https://ip-172-27-3-42.ap-southeast-1.compute.internal:8440/ca
06 Oct 2016 13:12:05,962  INFO [qtp-ambari-agent-51] HeartBeatHandler:927 - agentOsType = redhat7
06 Oct 2016 13:12:06,001  INFO [qtp-ambari-agent-51] HostImpl:285 - Received host registration, host=[hostname=ip-172-27-3-44,fqdn=ip-172-27-3-44.ap-southeast-1.compute.internal,domain=ap-southeast-1.compute.internal,architecture=x86_64,processorcount=8,physicalprocessorcount=8,osname=redhat,osversion=7.2,osfamily=redhat,memory=62450636,uptime_hours=4001,mounts=(available=7132304,mountpoint=/,used=13826908,percent=66%,size=20959212,device=/dev/xvda2,type=xfs)(available=31333092,mountpoint=/dev,used=0,percent=0%,size=31333092,device=devtmpfs,type=devtmpfs)(available=31225316,mountpoint=/dev/shm,used=0,percent=0%,size=31225316,device=tmpfs,type=tmpfs)(available=30405548,mountpoint=/run,used=819768,percent=3%,size=31225316,device=tmpfs,type=tmpfs)(available=6245064,mountpoint=/run/user/1009,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)(available=1818844928,mountpoint=/data0,used=6173224,percent=1%,size=1922709696,device=/dev/xvdb,type=ext4)(available=1819170444,mountpoint=/data1,used=5847708,percent=1%,size=1922709696,device=/dev/xvdc,type=ext4)(available=1819149136,mountpoint=/data2,used=5869016,percent=1%,size=1922709696,device=/dev/xvdd,type=ext4)(available=1818622620,mountpoint=/data3,used=6395532,percent=1%,size=1922709696,device=/dev/xvde,type=ext4)(available=1818458600,mountpoint=/data4,used=6559552,percent=1%,size=1922709696,device=/dev/xvdf,type=ext4)(available=1819329432,mountpoint=/data5,used=5688720,percent=1%,size=1922709696,device=/dev/xvdg,type=ext4)(available=6245064,mountpoint=/run/user/1002,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)]
, registrationTime=1475730725962, agentVersion=2.2.1.0
06 Oct 2016 13:12:06,001  INFO [qtp-ambari-agent-51] TopologyManager:316 - TopologyManager.onHostRegistered: Entering
06 Oct 2016 13:12:06,002  INFO [qtp-ambari-agent-51] TopologyManager:318 - TopologyManager.onHostRegistered: host = ip-172-27-3-44.ap-southeast-1.compute.internal is already associated with the cluster or is currently being processed
06 Oct 2016 13:12:06,030  INFO [qtp-ambari-agent-51] HeartBeatHandler:994 - Recovery configuration set to RecoveryConfig{, type=AUTO_START, maxCount=6, windowInMinutes=60, retryGap=5, maxLifetimeCount=1024, disabledComponents=, enabledComponents=METRICS_COLLECTOR}
06 Oct 2016 13:12:16,463  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component HIVE_SERVER of service HIVE of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:16,467  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component WEBHCAT_SERVER of service HIVE of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:16,469  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component MYSQL_SERVER of service HIVE of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:16,472  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component METRICS_MONITOR of service AMBARI_METRICS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:16,474  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component HIVE_METASTORE of service HIVE of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:16,475  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component NODEMANAGER of service YARN of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:16,477  INFO [qtp-ambari-agent-52] HeartBeatHandler:683 - State of service component DATANODE of service HDFS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-44.ap-southeast-1.compute.internal
06 Oct 2016 13:12:23,611  WARN [qtp-ambari-agent-52] SecurityFilter:103 - Request https://ip-172-27-3-42.ap-southeast-1.compute.internal:8440/ca doesn't match any pattern.
06 Oct 2016 13:12:23,611  WARN [qtp-ambari-agent-52] SecurityFilter:62 - This request is not allowed on this port: https://ip-172-27-3-42.ap-southeast-1.compute.internal:8440/ca
06 Oct 2016 13:12:24,024  INFO [qtp-ambari-agent-55] HeartBeatHandler:927 - agentOsType = redhat7
06 Oct 2016 13:12:24,048  INFO [qtp-ambari-agent-55] HostImpl:285 - Received host registration, host=[hostname=ip-172-27-3-45,fqdn=ip-172-27-3-45.ap-southeast-1.compute.internal,domain=ap-southeast-1.compute.internal,architecture=x86_64,processorcount=8,physicalprocessorcount=8,osname=redhat,osversion=7.2,osfamily=redhat,memory=62450636,uptime_hours=4001,mounts=(available=7582428,mountpoint=/,used=13376784,percent=64%,size=20959212,device=/dev/xvda2,type=xfs)(available=31333092,mountpoint=/dev,used=0,percent=0%,size=31333092,device=devtmpfs,type=devtmpfs)(available=31225316,mountpoint=/dev/shm,used=0,percent=0%,size=31225316,device=tmpfs,type=tmpfs)(available=30757844,mountpoint=/run,used=467472,percent=2%,size=31225316,device=tmpfs,type=tmpfs)(available=6245064,mountpoint=/run/user/1009,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)(available=1819347548,mountpoint=/data0,used=5670604,percent=1%,size=1922709696,device=/dev/xvdb,type=ext4)(available=1818929436,mountpoint=/data1,used=6088716,percent=1%,size=1922709696,device=/dev/xvdc,type=ext4)(available=1818785956,mountpoint=/data2,used=6232196,percent=1%,size=1922709696,device=/dev/xvdd,type=ext4)(available=1818854456,mountpoint=/data3,used=6163696,percent=1%,size=1922709696,device=/dev/xvde,type=ext4)(available=1818324588,mountpoint=/data4,used=6693564,percent=1%,size=1922709696,device=/dev/xvdf,type=ext4)(available=1819333412,mountpoint=/data5,used=5684740,percent=1%,size=1922709696,device=/dev/xvdg,type=ext4)(available=6245064,mountpoint=/run/user/0,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)(available=6245064,mountpoint=/run/user/1002,used=0,percent=0%,size=6245064,device=tmpfs,type=tmpfs)]
, registrationTime=1475730744023, agentVersion=2.2.1.0
06 Oct 2016 13:12:24,049  INFO [qtp-ambari-agent-55] TopologyManager:316 - TopologyManager.onHostRegistered: Entering
06 Oct 2016 13:12:24,050  INFO [qtp-ambari-agent-55] TopologyManager:318 - TopologyManager.onHostRegistered: host = ip-172-27-3-45.ap-southeast-1.compute.internal is already associated with the cluster or is currently being processed
06 Oct 2016 13:12:24,067  INFO [qtp-ambari-agent-55] HeartBeatHandler:994 - Recovery configuration set to RecoveryConfig{, type=AUTO_START, maxCount=6, windowInMinutes=60, retryGap=5, maxLifetimeCount=1024, disabledComponents=, enabledComponents=METRICS_COLLECTOR}
06 Oct 2016 13:12:34,431  INFO [qtp-ambari-agent-55] HeartBeatHandler:683 - State of service component DATANODE of service HDFS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:12:34,433  INFO [qtp-ambari-agent-55] HeartBeatHandler:683 - State of service component NODEMANAGER of service YARN of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:12:34,435  INFO [qtp-ambari-agent-55] HeartBeatHandler:683 - State of service component METRICS_MONITOR of service AMBARI_METRICS of cluster eim_edl_dev_cluster_1 has changed from UNKNOWN to STARTED at host ip-172-27-3-45.ap-southeast-1.compute.internal
06 Oct 2016 13:13:06,861  INFO [Thread-21] AbstractPoolBackedDataSource:462 - 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, dataSourceName -> 1br43sa9j16aawh419l599e|58230224, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> org.postgresql.Driver, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 1br43sa9j16aawh419l599e|58230224, idleConnectionTestPeriod -> 50, initialPoolSize -> 3, jdbcUrl -> jdbc:postgresql://localhost/ambari, lastAcquisitionFailureDefaultUser -> null, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 5, maxStatements -> 0, maxStatementsPerConnection -> 120, minPoolSize -> 1, numHelperThreads -> 3, numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery -> select 0, properties -> {user=******, password=******}, propertyCycle -> 0, testConnectionOnCheckin -> true, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false ]
06 Oct 2016 13:13:06,913  INFO [Thread-21] JobStoreTX:861 - Freed 0 triggers from 'acquired' / 'blocked' state.
06 Oct 2016 13:13:06,921  INFO [Thread-21] JobStoreTX:871 - Recovering 0 jobs that were in-progress at the time of the last shut-down.
06 Oct 2016 13:13:06,921  INFO [Thread-21] JobStoreTX:884 - Recovery complete.
06 Oct 2016 13:13:06,921  INFO [Thread-21] JobStoreTX:891 - Removed 0 'complete' triggers.
06 Oct 2016 13:13:06,923  INFO [Thread-21] JobStoreTX:896 - Removed 0 stale fired job entries.
06 Oct 2016 13:13:06,924  INFO [Thread-21] QuartzScheduler:575 - Scheduler ExecutionScheduler_$_NON_CLUSTERED started.

[#2 · Accepted solution]

Hi All,

The issue is fixed & it was a problem on the network firewall end in which they have done some changes which affected the ambari server ip which got NATing on the firewall. Today only they have responded with the details.

Really wanted to thank you for your valuable comments and time you have provided.

[#3]

Hi All,

The issue is fixed & it was a problem on the network firewall end in which they have done some changes which affected the ambari server ip which got NATing on the firewall. Today only they have responded with the details.

Really wanted to thank you for your valuable comments and time you have provided.