Re: Cannot Start Postgres After System Boot - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Cannot Start Postgres After System Boot
Date
Msg-id AANLkTimBJZz9B_MVjRd-utFH6UyGvFTDdPoDuVD0vJCd@mail.gmail.com
Whole thread Raw
In response to Cannot Start Postgres After System Boot  (Rich Shepard <rshepard@appl-ecosys.com>)
List pgsql-general
On Wed, Oct 20, 2010 at 4:53 PM, Rich Shepard <rshepard@appl-ecosys.com> wrote:
>  For reasons I do not understand, the Slackware start-up file for postgres
> (/etc/rc.d/rc.postgresql) fails to work properly after I reboot the system.
> (Reboots normally occur only after a kernel upgrade or with a hardware
> failure that crashes the system.)
>
>  Trying to restart the system manually (su postgres -c 'postgres -D
> /var/lib/pgsql/data &') regardless of the presence of /tmp/.s.PGSQL.5432
> and /var/lib/pgsql/postmaster.pid. Here's what I see:
>
> [rshepard@salmo ~]$ su postgres -c 'postgres -D /var/lib/pgsql/data &'
> Password: [rshepard@salmo ~]$ LOG:  could not bind IPv4 socket: Address
> already in use
> HINT:  Is another postmaster already running on port 5432? If not, wait a
> few seconds and retry.
> WARNING:  could not create listen socket for "localhost"
> FATAL:  could not create any TCP/IP sockets

Are you sure postgresql isn't getting started by some other init
script before this one runs?  warnings that a port can't be bound to
is usually just that.  something else is on it.  What does lsof tell
you is running on that port?

pgsql-general by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Problem with Postgresql 9.0 streaming replication on Solaris 10 (x86)
Next
From: Tom Lane
Date:
Subject: Re: pg_temp implicit search path: functions vs. tables