X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 675EBD1B1E3 for ; Fri, 4 Jun 2004 00:57:25 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 94319-06 for ; Fri, 4 Jun 2004 03:57:24 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by svr1.postgresql.org (Postfix) with ESMTP id B9231D1B1DC for ; Fri, 4 Jun 2004 00:57:22 -0300 (ADT) Received: from localhost.localdomain (c-67-162-79-220.client.comcast.net[67.162.79.220]) by comcast.net (rwcrmhc13) with ESMTP id <2004060403572101500me0e0e>; Fri, 4 Jun 2004 03:57:22 +0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i543uEDC021212; Thu, 3 Jun 2004 22:56:15 -0500 Received: (from spike@localhost) by localhost.localdomain (8.12.11/8.12.11/Submit) id i543uESS021209; Thu, 3 Jun 2004 22:56:14 -0500 X-Authentication-Warning: localhost.localdomain: spike set sender to mike@thegodshalls.com using -f Subject: Re: URGENT : StreamServerPort: bind() failed: Cannot From: mike g Reply-To: mike@thegodshalls.com To: sirath@cisco.com Cc: pgsql-admin@postgresql.org In-Reply-To: <09af01c449da$cb2e3dc0$2c6345ab@amer.cisco.com> References: <09af01c449da$cb2e3dc0$2c6345ab@amer.cisco.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1086321373.21104.11.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Thu, 03 Jun 2004 22:56:14 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200406/28 X-Sequence-Number: 13688 Hi, I believe a fast shutdown prevents new connections to the db, sends termination signals to any applications with current connections, and then after it receives confirmation that those applications have aborted their transactions and closed their connections the db stops. It sounds like your application is either not responding to or confirming the shutdown request from the db. The details in that archive were trying to explain how to find which process / application are still connected to the db after the fast shutdown attempted to terminate them. Without root access though maybe you aren't able to see which process is still attached to the db? Try doing a ps -A and see if the postmaster is still showing up in the process list. If it is then you know for sure that the db is not truly shutdown. On Thu, 2004-06-03 at 21:22, Siddharth Rath (sirath) wrote: > Hi, > I've an application running on RedHat Linux and we are using Postgres as our DB. Initially the DB was running perfectly but due to > some requirement we stopped the DB with " pg_ctl stop -m 'fast' " command. When I tried to restart the DB/Postmaster it says : > > StreamServerPort: bind() failed: Cannot assign requested address > Is another postmaster already running on port 5432? > If not, wait a few seconds and retry. > cannot create INET stream port > > Since I don't have root access , I took the help of the Sysadmin to reboot the system and the DB server(POSTGRES) started correctly > , but when I stopped the DB server with above mentioned command and started again it throws back the same old error. Is there anyway > to get rid of these. > > I found some details in archieves at http://list.linux-vserver.org/archive/vserver/msg04095.html . But I don't understand what to do > next. > > The O/P of >netstat -plunt | grep 5432 > > (Not all processes could be identified, non-owned process info > will not be shown, you would have to be root to see it all.) > tcp 0 0 0.0.0.0:54320 0.0.0.0:* LISTEN - > udp 0 0 0.0.0.0:54321 0.0.0.0:* - > > And O/P of netstat -ranv > > Kernel IP routing table > Destination Gateway Genmask Flags MSS Window irtt Iface > 10.83.103.0 0.0.0.0 255.255.255.192 U 0 0 0 eth2 > 64.102.29.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 64.102.29.1 0.0.0.0 UG 0 0 0 eth0 > > Any pointers/help in resolving this issue will be highly appreciated. > > Thanx and regards > Sidd > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly