title: Ambari server can not start
body: <p>I have completed <a href="http://ambari.apache.org/" rel="nofollow">Ambari</a> setup in CentOS 6.5, and started Ambari server successfully. But when I run <code>netstat|grep Ambari</code> command, nothing is shown. </p>
  
  <p>I can not access the Ambari server with my browser. Please give me a hand, many thanks.</p>
  
  <p>Ambari server start status:</p>
  
  <pre><code>ps -ef|grep Ambari
  root     31424     1 10 17:45 pts/0    00:00:27 /usr/lib/jdk1.7.0_45/bin/java -server -XX:NewRatio=3 -XX:+UseConcMarkSweepGC -XX:-UseGCOverheadLimit -XX:CMSInitiatingOccupancyFraction=60 -Xms512m -Xmx2048m -Djava.security.auth.login.config=/etc/ambari-server/conf/krb5JAASLogin.conf -Djava.security.krb5.conf=/etc/krb5.conf -Djavax.security.auth.useSubjectCredsOnly=false -cp /etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/usr/lib/ambari-server/* org.apache.ambari.server.controller.AmbariServer
  </code></pre>
  
  <p>ambari-config-changes.log:</p>
  
  <pre><code>17:48:03,591  INFO [Thread-22] AbstractPoolBackedDataSource:462 - Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -&gt; 3, acquireRetryAttempts -&gt; 30, acquireRetryDelay -&gt; 1000, autoCommitOnClose -&gt; false, automaticTestTable -&gt; null, breakAfterAcquireFailure -&gt; false, checkoutTimeout -&gt; 0, connectionCustomizerClassName -&gt; null, connectionTesterClassName -&gt; com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName -&gt; 1bqon9k938saoxzky1njv|3d0c29a1, debugUnreturnedConnectionStackTraces -&gt; false, description -&gt; null, driverClass -&gt; org.postgresql.Driver, factoryClassLocation -&gt; null, forceIgnoreUnresolvedTransactions -&gt; false, identityToken -&gt; 1bqon9k938saoxzky1njv|3d0c29a1, idleConnectionTestPeriod -&gt; 50, initialPoolSize -&gt; 3, jdbcUrl -&gt; jdbc:postgresql://localhost/ambari, lastAcquisitionFailureDefaultUser -&gt; null, maxAdministrativeTaskTime -&gt; 0, maxConnectionAge -&gt; 0, maxIdleTime -&gt; 0, maxIdleTimeExcessConnections -&gt; 0, maxPoolSize -&gt; 5, maxStatements -&gt; 0, maxStatementsPerConnection -&gt; 120, minPoolSize -&gt; 1, numHelperThreads -&gt; 3, numThreadsAwaitingCheckoutDefaultUser -&gt; 0, preferredTestQuery -&gt; select 0, properties -&gt; {user=******, password=******}, propertyCycle -&gt; 0, testConnectionOnCheckin -&gt; true, testConnectionOnCheckout -&gt; false, unreturnedConnectionTimeout -&gt; 0, usesTraditionalReflectiveProxies -&gt; false ]
  17:48:03,676  INFO [Thread-22] JobStoreTX:861 - Freed 0 triggers from 'acquired' / 'blocked' state.
  17:48:03,694  INFO [Thread-22] JobStoreTX:871 - Recovering 0 jobs that were in-progress at the time of the last shut-down.
  17:48:03,694  INFO [Thread-22] JobStoreTX:884 - Recovery complete.
  17:48:03,695  INFO [Thread-22] JobStoreTX:891 - Removed 0 'complete' triggers.
  17:48:03,696  INFO [Thread-22] JobStoreTX:896 - Removed 0 stale fired job entries.
  17:48:03,708  INFO [Thread-22] QuartzScheduler:575 - Scheduler ExecutionScheduler_$_NON_CLUSTERED started.
  </code></pre>