[
https://issues.apache.org/jira/browse/AMBARI-12480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Edwards resolved AMBARI-12480.
------------------------------------
Resolution: Implemented
I realized I had installed an older version of Ambari than I thought I had.
This issue is not relevant to the current version.
> Ambari Setup shouldn't start PostgreSQL immediately
> ---------------------------------------------------
>
> Key: AMBARI-12480
> URL: https://issues.apache.org/jira/browse/AMBARI-12480
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 1.2.0
> Reporter: Scott Edwards
> Priority: Trivial
>
> Ambari allows possibilities to configure with other databases other than the
> default installed PostgreSQL, but the default Ambari-Server Setup will start
> the local Ambari installed PostgreSQL before it even begins Setup.
> In the init script /usr/sbin/ambari-server:
> setup)
> echo -e "Run postgresql initdb"
> initdb_res=`/sbin/service postgresql initdb`
> if [ "0" == "$?" ]; then
> echo -e "${initdb_res}"
> fi
> echo -e "Run postgresql start"
> /sbin/service postgresql start
> echo -e "Setup ambari-server"
> $PYTHON /usr/sbin/ambari-server.py $@
> ;;
> I recommend placing a flag on the Ambari install process to allow you to
> choose installing a local copy of PostgreSQL or decline and continue install
> without it.
> During setup) PostgreSQL shouldn't start unless Ambari did install a local
> copy of Postgres, as selected during install. Otherwise, you should have
> options of specifying database connection information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
