X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C3FD7D1CCB1 for ; Sat, 13 Mar 2004 18:22:20 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 20487-10 for ; Sat, 13 Mar 2004 14:22:18 -0400 (AST) Received: from smurfer.pastoraat (minas-2.demon.nl [212.238.194.105]) by svr1.postgresql.org (Postfix) with ESMTP id E3542D1C9E1 for ; Sat, 13 Mar 2004 14:22:14 -0400 (AST) Received: from minas.demon.nl (athlon.pastoraat [192.168.1.1]) by smurfer.pastoraat (8.12.8/8.12.8) with ESMTP id i2DIQ0hv032724 for ; Sat, 13 Mar 2004 19:26:00 +0100 Message-ID: <4053506E.5090506@minas.demon.nl> Date: Sat, 13 Mar 2004 19:18:22 +0100 From: Michiel Lange User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: tcp port References: <200403081854.38409.philippe.haas@free.fr> <200403100842.40464.peter_e@gmx.net> In-Reply-To: <200403100842.40464.peter_e@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/206 X-Sequence-Number: 12775 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 > > >