Bug 446104 - Postgres may not be fully started when the service script returns
Summary: Postgres may not be fully started when the service script returns
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Virtualization Tools
Classification: Community
Component: ovirt-server-suite
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Alan Pevec
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-12 19:00 UTC by Benjamin Kahn
Modified: 2010-03-16 17:13 UTC (History)
1 user (show)

Fixed In Version: 0.0.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-02 14:42:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Benjamin Kahn 2008-05-12 19:00:14 UTC
Description of problem:
Postgres may not be fully started when the service script returns.
This causes problems with the wui install scripts since they assume they can
start running database commands right away.

Version-Release number of selected component (if applicable):
ovirt-wui-0.0.4-2.fc8

How reproducible:
Happens every time on my machine, but likely won't happen on faster machines, or
machines with more RAM

Steps to Reproduce:
1.Run the wui first boot script
  
Actual results:
ovirt database doesn't get created

Expected results:
Database created

Additional info:
Putting a "sleep 2" in the startup script fixes the problem on my box, but there
should be a better way to ensure the database is actually started.

Comment 1 Alan Pevec 2008-05-12 22:05:55 UTC
indeed, postmaster is started in the background, so we'll need to loop after
service postgresql start, waiting for service postgresql status to return 0



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