Bug 812220

Summary: sepostgresql does not start or stop with systemctl
Product: [Fedora] Fedora Reporter: William Brown <william>
Component: sepostgresqlAssignee: KaiGai Kohei <kaigai>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: kaigai
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-05 15:16:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description William Brown 2012-04-13 06:53:23 UTC
Description of problem:
When starting sepostgresql from systemctl start sepostgresql.service, the start process hangs for a period of time, and then fails. Additionally, stopping the daemon results in an exit status 0, but the process still remains.

Version-Release number of selected component (if applicable):
sepostgresql 9.0.3

How reproducible:
Always

Steps to Reproduce:
1. Install sepostgresql. initdb
2. Run systemctl start sepostgresql.service
3. Wait
4. run systemctl stop sepostgresql.service
  
Actual results:
Sepostgresql starts, but the init script fails to acknowledge this. Additionally, the service is not stopped

Expected results:
sepostgresql script returns 0 status, and is able to stop the daemon correctly.

Comment 1 William Brown 2012-06-05 15:16:32 UTC
Issue resolved - These packages are not the method for using sepgsql now. They are slated for removal.