Re: could not bind IPv4 socket

From: Adrian Klaver <aklaver(at)comcast(dot)net>
To: pgsql-general(at)postgresql(dot)org
Cc: Grzegorz Buś <gall(at)p-team(dot)org>
Subject: Re: could not bind IPv4 socket
Date: 2009-05-04 13:18:53
Message-ID: 200905040618.53296.aklaver@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday 04 May 2009 4:29:27 am Grzegorz Buś wrote:
> When I run separately start/stop commands I still get "could not bind
> socket" message:
>
> # service postgresql stop
> Stopping postgresql service: [ OK ]
> # netstat -plunt | grep 5432
> # ps -A | grep postmaster
> # rm /var/lib/pgsql/pgstartup.log
> rm: remove regular file `/var/lib/pgsql/pgstartup.log'? y
> # service postgresql start
> Starting postgresql service: [ OK ]
> # cat /var/lib/pgsql/pgstartup.log
> 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.
>
> --
> Kind Regards,
> Grzegorz Bus
>
> -----Original Message-----
>

In my /tmp directory I have the following when the server is running. These
files are removed on shutdown. When you do your shutdown, check and see if they
are still there and what there timestamp is. Could be there are left over files
from your previous version.

/tmp$
srwxrwxrwx 1 postgres postgres 0 2009-05-04 05:51 .s.PGSQL.5432
-rw------- 1 postgres postgres 27 2009-05-04 05:51 .s.PGSQL.5432.lock

--
Adrian Klaver
aklaver(at)comcast(dot)net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2009-05-04 13:30:23 Re: diff-/patch-functionality for text-type data inside PostgreSQL
Previous Message Tom Lane 2009-05-04 13:03:33 Re: diff-/patch-functionality for text-type data inside PostgreSQL