Re: BUG #9416: Setting up postgresql-9.1 (9.1.12-0wheezy1) Fails Configuration - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #9416: Setting up postgresql-9.1 (9.1.12-0wheezy1) Fails Configuration
Date
Msg-id 7216.1393859322@sss.pgh.pa.us
Whole thread Raw
In response to BUG #9416: Setting up postgresql-9.1 (9.1.12-0wheezy1) Fails Configuration  (pboake@gmail.com)
Responses Re: BUG #9416: Setting up postgresql-9.1 (9.1.12-0wheezy1) Fails Configuration  (Patrick Boake <pboake@gmail.com>)
List pgsql-bugs
pboake@gmail.com writes:
> apt-get upgrade returns;

> Setting up postgresql-9.1 (9.1.12-0wheezy1) ...
> [....] Starting PostgreSQL 9.1 database server: main[....] The PostgreSQL
> server failed to start. Please check the log output: 2014-03-02 22:13:28 EST
> LOG: could not bind IPv4 socket: Cannot assign requested address 2014-03-02
> 22:13:28 EST HINT: Is another postmaster already running on port 5432? If
> not, wait a few seconds and retry. 2014-03-02 22:13:28 EST LOG: could not
> bind IPv6 socket: Cannot assign requested address 2014-03-02 22:13:28 EST
> HINT: Is another postmaster already running on port 5432? If not, wait a few
> seconds and retry. 2014-03-02 22:1[FAILEST WARNING: could not create listen
> socket for "localhost" 2014-03-02 22:13:28 EST FATAL: could not create any
> TCP/IP sockets ... failed!
>  failed!
> invoke-rc.d: initscript postgresql, action "start" failed.

What that looks like is that the package's upgrade script forgot to stop
the old postmaster version before trying to start the new one; or perhaps
slightly more likely, failed to wait for the old postmaster to finish
stopping.

Either way, that would be a bug in the packaging, which you should take
up with the Debian package maintainer, not with the upstream project.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: BUG #9422: PostgreSQL Zero downtime during deployement
Next
From: Dean Rasheed
Date:
Subject: Re: BUG #9371: pg_dump acquiring ROW EXCLUSIVE locks on tables