<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine ) in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158005#M36481</link>
    <description>&lt;P&gt;
	From ambari logfile&lt;/P&gt;&lt;P&gt;
	31 Jul 2016 07:03:08,401  INFO [main] Configuration:594 - Reading password from existing file

	31 Jul 2016 07:03:08,447  INFO [main] Configuration:864 - Hosts Mapping File null

	31 Jul 2016 07:03:08,448  INFO [main] HostsMap:60 - Using hostsmap file null

	31 Jul 2016 07:03:09,669  INFO [main] ControllerModule:185 - Detected POSTGRES as the database type from the JDBC URL

	31 Jul 2016 07:03:12,339  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher

	31 Jul 2016 07:03:12,375  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher

	31 Jul 2016 07:03:12,678  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher

	31 Jul 2016 07:04:29,015  INFO [main] Configuration:594 - Reading password from existing file

	31 Jul 2016 07:04:29,061  INFO [main] Configuration:864 - Hosts Mapping File null

	31 Jul 2016 07:04:29,061  INFO [main] HostsMap:60 - Using hostsmap file null

	31 Jul 2016 07:04:30,049  INFO [main] ControllerModule:185 - Detected POSTGRES as the database type from the JDBC URL

	31 Jul 2016 07:04:32,210  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher

	31 Jul 2016 07:04:32,227  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher

	31 Jul 2016 07:04:32,388  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher

	31 Jul 2016 07:05:38,265 ERROR [main] DBAccessorImpl:100 - Error while creating database accessor

	&lt;STRONG&gt;org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.&lt;/STRONG&gt;

	  at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:207)

	  at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64)

	  at org.postgresql.jdbc2.AbstractJdbc2Connection.&amp;lt;init&amp;gt;(AbstractJdbc2Connection.java:138)

	  at org.postgresql.jdbc3.AbstractJdbc3Connection.&amp;lt;init&amp;gt;(AbstractJdbc3Connection.java:29)&lt;/P&gt;&lt;P&gt;
	.&lt;/P&gt;&lt;P&gt;
	.&lt;/P&gt;&lt;P&gt;
	.&lt;/P&gt;&lt;P&gt;
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)

	  at com.google.inject.internal.InjectionRequestProcessor$StaticInjection.injectMembers(InjectionRequestProcessor.java:110)

	  at com.google.inject.internal.InjectionRequestProcessor.injectMembers(InjectionRequestProcessor.java:78)

	  at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:170)

	  at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)

	  at com.google.inject.Guice.createInjector(Guice.java:95)

	  at com.google.inject.Guice.createInjector(Guice.java:72)

	  at com.google.inject.Guice.createInjector(Guice.java:62)

	  &lt;STRONG&gt;at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:701)

	Caused by: java.net.ConnectException: Connection timed out

	  at java.net.PlainSocketImpl.socketConnect(Native Method)&lt;/STRONG&gt;

	  at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)

	  at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

	  at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

	  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

	  at java.net.Socket.connect(Socket.java:589)

	  at java.net.Socket.connect(Socket.java:538)

	  at org.postgresql.core.PGStream.&amp;lt;init&amp;gt;(PGStream.java:60)

	  at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:101)

	  ... 47 more&lt;/P&gt;&lt;P&gt;
	Please can you help&lt;/P&gt;</description>
    <pubDate>Sun, 31 Jul 2016 13:19:10 GMT</pubDate>
    <dc:creator>shivkumar82015</dc:creator>
    <dc:date>2016-07-31T13:19:10Z</dc:date>
    <item>
      <title>Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158005#M36481</link>
      <description>&lt;P&gt;
	From ambari logfile&lt;/P&gt;&lt;P&gt;
	31 Jul 2016 07:03:08,401  INFO [main] Configuration:594 - Reading password from existing file

	31 Jul 2016 07:03:08,447  INFO [main] Configuration:864 - Hosts Mapping File null

	31 Jul 2016 07:03:08,448  INFO [main] HostsMap:60 - Using hostsmap file null

	31 Jul 2016 07:03:09,669  INFO [main] ControllerModule:185 - Detected POSTGRES as the database type from the JDBC URL

	31 Jul 2016 07:03:12,339  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher

	31 Jul 2016 07:03:12,375  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher

	31 Jul 2016 07:03:12,678  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher

	31 Jul 2016 07:04:29,015  INFO [main] Configuration:594 - Reading password from existing file

	31 Jul 2016 07:04:29,061  INFO [main] Configuration:864 - Hosts Mapping File null

	31 Jul 2016 07:04:29,061  INFO [main] HostsMap:60 - Using hostsmap file null

	31 Jul 2016 07:04:30,049  INFO [main] ControllerModule:185 - Detected POSTGRES as the database type from the JDBC URL

	31 Jul 2016 07:04:32,210  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher

	31 Jul 2016 07:04:32,227  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher

	31 Jul 2016 07:04:32,388  INFO [main] ControllerModule:558 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher

	31 Jul 2016 07:05:38,265 ERROR [main] DBAccessorImpl:100 - Error while creating database accessor

	&lt;STRONG&gt;org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.&lt;/STRONG&gt;

	  at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:207)

	  at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:64)

	  at org.postgresql.jdbc2.AbstractJdbc2Connection.&amp;lt;init&amp;gt;(AbstractJdbc2Connection.java:138)

	  at org.postgresql.jdbc3.AbstractJdbc3Connection.&amp;lt;init&amp;gt;(AbstractJdbc3Connection.java:29)&lt;/P&gt;&lt;P&gt;
	.&lt;/P&gt;&lt;P&gt;
	.&lt;/P&gt;&lt;P&gt;
	.&lt;/P&gt;&lt;P&gt;
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1024)

	  at com.google.inject.internal.InjectionRequestProcessor$StaticInjection.injectMembers(InjectionRequestProcessor.java:110)

	  at com.google.inject.internal.InjectionRequestProcessor.injectMembers(InjectionRequestProcessor.java:78)

	  at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:170)

	  at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:109)

	  at com.google.inject.Guice.createInjector(Guice.java:95)

	  at com.google.inject.Guice.createInjector(Guice.java:72)

	  at com.google.inject.Guice.createInjector(Guice.java:62)

	  &lt;STRONG&gt;at org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:701)

	Caused by: java.net.ConnectException: Connection timed out

	  at java.net.PlainSocketImpl.socketConnect(Native Method)&lt;/STRONG&gt;

	  at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)

	  at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)

	  at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)

	  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

	  at java.net.Socket.connect(Socket.java:589)

	  at java.net.Socket.connect(Socket.java:538)

	  at org.postgresql.core.PGStream.&amp;lt;init&amp;gt;(PGStream.java:60)

	  at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:101)

	  ... 47 more&lt;/P&gt;&lt;P&gt;
	Please can you help&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jul 2016 13:19:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158005#M36481</guid>
      <dc:creator>shivkumar82015</dc:creator>
      <dc:date>2016-07-31T13:19:10Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158006#M36482</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Ambari is not able to connect to postgres database. Please check for below possible errors.&lt;/P&gt;&lt;P&gt;1] Postgres SQL is listening on a different port that what is configured under /etc/ambari-server/conf/ambari.properties&lt;/P&gt;&lt;P&gt;2] Postgres is not running&lt;/P&gt;&lt;P&gt;3] firewall issues&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jul 2016 13:40:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158006#M36482</guid>
      <dc:creator>sgowda</dc:creator>
      <dc:date>2016-07-31T13:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158007#M36483</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/11907/shivkumar82015.html" nodeid="11907"&gt;@Shiv kumar&lt;/A&gt;&lt;P style="margin-left: 20px;"&gt;Please let us know if the issue is resolved&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jul 2016 13:41:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158007#M36483</guid>
      <dc:creator>sgowda</dc:creator>
      <dc:date>2016-07-31T13:41:16Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158008#M36484</link>
      <description>&lt;P&gt;Thank you for reply&lt;/P&gt;&lt;P&gt;I was able to connect when i have installed &amp;amp; Setup the ambar, however now not able to login&lt;/P&gt;&lt;P&gt;1) Postgrec SQl is listening the port to 5432&lt;/P&gt;&lt;P&gt;2) Its running fine , please find log &lt;/P&gt;&lt;P&gt;postgres  1604  1  0 11:01 ?  00:00:00 /usr/bin/postmaster -p 5432 -D /var/lib/pgsql/data
postgres  1606  1604  0 11:01 ?  00:00:00 postgres: logger process
postgres  1608  1604  0 11:01 ?  00:00:01 postgres: writer process&lt;/P&gt;&lt;P&gt;3) How to verify the firewall , kindly advise&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jul 2016 14:04:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158008#M36484</guid>
      <dc:creator>shivkumar82015</dc:creator>
      <dc:date>2016-07-31T14:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158009#M36485</link>
      <description>&lt;P&gt;1] If you ambari-server and postgres database is running on different hosts then try "telnet post-gres-hostname 5432" from the ambari-server machine&lt;/P&gt;&lt;P&gt;2] Make sure ambari.properties has the correct end point configured&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jul 2016 14:11:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158009#M36485</guid>
      <dc:creator>sgowda</dc:creator>
      <dc:date>2016-07-31T14:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158010#M36486</link>
      <description>&lt;P&gt;1)Both Installed on same server &lt;/P&gt;&lt;P&gt;2)Could you elaborate ambari-properties has correct end point ?&lt;/P&gt;</description>
      <pubDate>Sun, 31 Jul 2016 20:13:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158010#M36486</guid>
      <dc:creator>shivkumar82015</dc:creator>
      <dc:date>2016-07-31T20:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: Ambari 2.1 , not able to connect WI error as (Unable to connect to ambari server. Confirm Ambari Server is running and you can reach Ambari Server from this machine )</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158011#M36487</link>
      <description>&lt;P&gt;Thanks for your reply. I did the following this it worked for me.&lt;/P&gt;&lt;P&gt;1) Stopped the Ambari and Postgresql database&lt;/P&gt;&lt;P&gt;[root@centos ~]# ambari-server stop
Using python  /usr/bin/python2.6
Stopping ambari-server
Ambari Server stopped
[root@centos ~]# service postgresql stop
Stopping postgresql service:  [  OK  ]
[root@centos ~]#&lt;/P&gt;&lt;P&gt;2) Changed the network setting VM ware from Bridge to NAT&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="6220-z27ll.png" style="width: 689px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/20838i3658DEADC60D61C5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="6220-z27ll.png" alt="6220-z27ll.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;3) Restarted the Network Service &lt;/P&gt;&lt;P&gt;#service network restart&lt;/P&gt;&lt;P&gt;4) Started the Postgresql database &lt;/P&gt;&lt;P&gt;[root@centos ~]# service postgresql start
Starting postgresql service:  [  OK  ]&lt;/P&gt;&lt;P&gt;5) Stared the Ambari-service &lt;/P&gt;&lt;P&gt;[root@centos ~]# ambari-server stop
Using python  /usr/bin/python2.6
Starting  ambari-server&lt;/P&gt;&lt;P&gt;After complete this mine Ambari Web Interface was working fine.&lt;/P&gt;</description>
      <pubDate>Sun, 18 Aug 2019 12:13:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Ambari-2-1-not-able-to-connect-WI-error-as-Unable-to-connect/m-p/158011#M36487</guid>
      <dc:creator>shivkumar82015</dc:creator>
      <dc:date>2019-08-18T12:13:37Z</dc:date>
    </item>
  </channel>
</rss>

