Bug 812220 - sepostgresql does not start or stop with systemctl
Summary: sepostgresql does not start or stop with systemctl
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: sepostgresql
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KaiGai Kohei
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-13 06:53 UTC by William Brown
Modified: 2012-06-05 15:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-05 15:16:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


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