[
https://issues.apache.org/jira/browse/AMBARI-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749041#comment-13749041
]
Siddharth Wagle commented on AMBARI-3020:
-----------------------------------------
+1 LGTM
> Running ambari-server setup more than once to reconfigure postgres settings
> fails
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-3020
> URL: https://issues.apache.org/jira/browse/AMBARI-3020
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.4.0
> Reporter: Artem Baranchuk
> Assignee: Artem Baranchuk
> Priority: Critical
> Fix For: 1.4.0
>
> Attachments: AMBARI-3020.patch
>
>
> The first scenario:
> * ran ambari-server setup twice
> * the first time with default DB name, DB User and Password
> * the second time with custom DB name
> As result we have server setup process broken with
> {code}
> ERROR: Database bootstrap failed. Please, provide correct connection
> properties.
> ERROR: Exiting with exit code 2. Reason: Error while configuring connection
> properties. Exiting
> {code}
> The second scenario:
> * ran ambari-server setup twice
> * the first time with default DB name, DB User and Password
> * the second time with custom DB User
> Ambari Server 'setup' completed successfully. But when we try to start ambari
> server it failed to start with the error:
> {code}
> [EL Info]: 2013-08-10 07:15:27.286--ServerSession(22221156)--EclipseLink,
> version: Eclipse Persistence Services - 2.4.0.v20120608-r11652
> [EL Severe]: ejb: 2013-08-10 07:15:27.345--ServerSession(22221156)--Exception
> [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120608-r11652):
> org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf
> entry for host "127.0.0.1", user "ambariuser", database "ambari", SSL off
> Error Code: 0
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
