You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Chad Roberts (JIRA)" <ji...@apache.org> on 2013/12/06 22:43:35 UTC
[jira] [Resolved] (AMBARI-1792) Postgres init commands change on
Fedora 16+
[ https://issues.apache.org/jira/browse/AMBARI-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chad Roberts resolved AMBARI-1792.
----------------------------------
Resolution: Fixed
commit 764ea58e19daac317ab9d2f1bbb7d3a92fce1aed
Author: Chad Roberts <cr...@redhat.com>
Date: Fri Dec 6 16:39:28 2013 -0500
AMBARI-1792. Postgres init commands change on Fedora 16+ (Trevor McKay via croberts).
> 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
> Fix For: 1.5.0
>
> Attachments: AMARI-1792.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 was sent by Atlassian JIRA
(v6.1#6144)