Bug 151421 - PostgreSQL server does not start after crash because wrong PID file location
PostgreSQL server does not start after crash because wrong PID file location
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: postgresql (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Lane
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-03-17 13:52 EST by Milan Kerslager
Modified: 2013-07-02 23:04 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-01 09:24:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milan Kerslager 2005-03-17 13:52:55 EST
After the system crash (reboot) the PostgreSQL server does not start because PID
file /var/lib/pgsql/data/postmaster.pid is not removed by initscripts at the
startup sequence. This is not a fault of initscripts but this is a bug in the
default PostgreSQL configuration.

The PostgreSQL server should have only one PID file in
/var/run/postmaster.<PID>.pid or the second PID file in /var/run/postgresql
subdirectory. After this relocation, initscripts should be fixed (postgresql
directory added, see line 943 in /etc/rc.d/rc.sysinit).

This is a very anoying longstandig bug so please make a REAL fix. When the
service does not start after the reboot (when NO other posmaster is able to run)
I think something is wrong in the bix complecity of /etc/init.d/postgresql. Also
I'm wondering why the hell there are two different same PID files...
Comment 1 Tom Lane 2005-03-17 14:15:02 EST
AFAIK this has been fixed for months (since postgresql-7.4.5-3 to be specific). 
You have not provided any details, like say the Postgres version you are using.
Comment 2 Milan Kerslager 2005-03-17 14:21:56 EST
As filled above, this is fully up-to-date RHEL4.
With OOPSing kernel (probably HW problem).
Comment 3 Tom Lane 2005-03-17 19:18:51 EST
After a suitable period of contemplation, I have realized that the fix
previously applied did not catch all the cases it was intended to :-(.


Will work on it.  It may be too late for RHEL4U1 though.
Comment 4 Josh Bressers 2005-06-01 09:24:10 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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