[
https://issues.apache.org/jira/browse/AMBARI-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753662#comment-13753662
]
Trevor McKay commented on AMBARI-1792:
--------------------------------------
In Fedora 18+, there is actually a patch that will issue
/usr/bin/postgresql-setup initdb if service postgresql initdb is issued.
But, using postgresql-setup if it is there in ambari-server is safer. First of
all it still works pre-F18, and second of all it will continue to work if the
compatibility patch is removed from Fedora for some reason (or another distro
has the same issue)
> Postgres init commands change on Fedora 16+
> --------------------------------------------
>
> Key: AMBARI-1792
> URL: https://issues.apache.org/jira/browse/AMBARI-1792
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.2.0
> Environment: Fedora 16 (and higher)
> Reporter: Trevor McKay
> Assignee: Trevor McKay
> Attachments: initdb.patch
>
>
> Migration to systemd instead of initd began in Fedora 15 and the postgres
> version changed to 9 in Fedora 16. As a consequence, in Fedora 16+ the
> postgres initdb commands have changed and the /usr/sbin/ambari-server.py
> script cannot initialize the database.
> Fortunately, there is a Fedora project (cumin) which has dealt with this
> exact issue from a shell script and should yield a patch :)
--
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
