Re: could not bind IPv4 socket - Mailing list pgsql-general

From Adrian Klaver
Subject Re: could not bind IPv4 socket
Date
Msg-id 200905040618.53296.aklaver@comcast.net
Whole thread Raw
In response to Re: could not bind IPv4 socket  (Grzegorz Buś <gall@p-team.org>)
Responses Re: could not bind IPv4 socket
List 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@comcast.net

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: diff-/patch-functionality for text-type data inside PostgreSQL
Next
From: Martijn van Oosterhout
Date:
Subject: Re: diff-/patch-functionality for text-type data inside PostgreSQL