pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michiel Lange <michiel@minas.demon.nl>
To: pgsql-admin@postgresql.org
Subject: Re: tcp port
Date: Sat, 13 Mar 2004 19:18:22 +0100
Message-ID: <4053506E.5090506@minas.demon.nl> (raw)
In-Reply-To: <200403100842.40464.peter_e@gmx.net>
References: <200403081854.38409.philippe.haas@free.fr>
	<200403100842.40464.peter_e@gmx.net>

It is possible that due some weird stuff the port is not made free... 
check with

$ netstat --all --numeric-ports -p | grep 5432

this -for example- is my output:
tcp        0      0 0.0.0.0:5432            0.0.0.0:*               
LISTEN      12775/postmaster
unix  2      [ ACC ]     STREAM     LISTENING     24015  
12775/postmaster    /tmp/.s.PGSQL.5432

If there is output, then check the PID which is just before the slash, 
in this case 12775

$ ps 12775

output:
  PID TTY      STAT   TIME COMMAND
12775 ?        S      0:00 /usr/local/pgsql/bin/postmaster -i

As you can see: there is a postmaster running
You might want to try to kill -TERM the process... don't use kill -KILL 
(or kill -9) on a running database, as you may very well very much 
damage your database...
Don't use kill -SEGV either! It's even more devastating...
kill -TERM is a request to shutdown as soon as possible. The process is 
allowed to shut down nicely and neatly.
kill -KILL is an order to stop immediately. There's no buffer flushing, 
finishing writes etc etc
kill -SEGV tells the program it made a segmentation fault and it crashed 
(core dump situation)

hope this information helps...

Peter Eisentraut wrote:

>philippe haas wrote:
>  
>
>>port 5432 (postmaster postgres reserved) on my machine(suze 8.2),
>>with PostgreSQL 7.4.1 ) is unreachable
>>When i launche postmaster with tcp/op option, i've the message :
>>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.
>>    
>>
>
>You can ignore this problem.  Notice that it does not say "ERROR" 
>anywhere.
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>               http://archives.postgresql.org
>
>  
>




view thread (3+ messages)

Message-ID: <4053506E.5090506@minas.demon.nl>
Permalink:  ../4053506E.5090506@minas.demon.nl/
Also on:    postgresql.org/message-id/4053506E.5090506@minas.demon.nl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: michiel@minas.demon.nl
  Subject: Re: tcp port
  In-Reply-To: <4053506E.5090506@minas.demon.nl>
  References: <200403081854.38409.philippe.haas@free.fr> <200403100842.40464.peter_e@gmx.net> <4053506E.5090506@minas.demon.nl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox