Bug 812220 - sepostgresql does not start or stop with systemctl
sepostgresql does not start or stop with systemctl
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: sepostgresql (Show other bugs)
16
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: KaiGai Kohei
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-13 02:53 EDT by William Brown
Modified: 2012-06-05 11:16 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-05 11:16:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description William Brown 2012-04-13 02:53:23 EDT
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 11:16:32 EDT
Issue resolved - These packages are not the method for using sepgsql now. They are slated for removal.

Note You need to log in before you can comment on or make changes to this bug.