[
https://issues.apache.org/jira/browse/AMBARI-12510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724144#comment-14724144
]
Sumit Mohanty commented on AMBARI-12510:
----------------------------------------
[~tctruong213], do you have a sample of the output on RHEL7?
The change looks safe to me except I am not sure how to quickly verify that the
status codes are the same for all OSes. I think the return codes of 0 and 3 are
what the command should return based on
http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html.
> ambari-server failed to properly detect of postgresql database status on RHEL
> 7.x
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-12510
> URL: https://issues.apache.org/jira/browse/AMBARI-12510
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Environment: RHEL 7.0, 7.1
> Reporter: Tuong Truong
> Assignee: Tuong Truong
> Labels: RHEL7.1
> Fix For: 2.1.2
>
> Attachments: AMBARI-12510-0.patch
>
>
> Ambari-server failed to initalize the postgre db when postgresql packages are
> installed as part of Ambari installation on RHEL 7.1, and 7.0 in some
> scenario.
> Ambari-server detects status of Postgre via the "service postgresql status"
> call, and perform regex on the output for "running" or "stopped". This
> works OK for RHEL 6, but not for RHEL 7 as its output may include "running"
> when postgres is not actually running.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)