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 BD173D1B49B for ; Fri, 4 Jun 2004 17:42:36 -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 17648-06 for ; Fri, 4 Jun 2004 20:42:35 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by svr1.postgresql.org (Postfix) with ESMTP id 0DA49D1B488 for ; Fri, 4 Jun 2004 17:42:32 -0300 (ADT) X-Sasl-enc: yyHMgoN/QSlsjj04cS31mA 1086381751 Received: from [10.10.12.12] (unknown [198.144.200.210]) by www.fastmail.fm (Postfix) with ESMTP id 896C3C0476F; Fri, 4 Jun 2004 16:42:31 -0400 (EDT) Message-ID: <40C0DD67.8090403@itsbeen.sent.com> Date: Fri, 04 Jun 2004 13:36:55 -0700 From: Rob User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: sirath@cisco.com Cc: pgsql-admin@postgresql.org Subject: Re: URGENT : StreamServerPort: bind() failed: Cannotassign References: <001b01c44a6f$7a072390$2c6345ab@amer.cisco.com> In-Reply-To: <001b01c44a6f$7a072390$2c6345ab@amer.cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/46 X-Sequence-Number: 13706 Siddharth Rath (sirath) wrote: > Hi Rob, > I did run the script from http://myclass.missouri.edu/~atb6x2/NETSERV/NS_serverpl.html and it didn't give any error and the O/P of > netstat -plunta | 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 - > tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN 9481/perl > udp 0 0 0.0.0.0:54321 0.0.0.0:* - > > But I don't understand why I cant bind to the same port thru POSTGRES. Please let me know what to do now to resolve this. > > Thanx and regards > Sidd OK, well given that that starts up (you ran it under the same user id that you are running pg with, right?), you should (kill that perl script) then try to start up pg under strace, that will give the clearest indication of what is going wrong. If you use : strace -f -e trace=network /usr/local/pgsql/bin... > s.out 2> s.err it might reduce the amount of output from strace but try : strace -f /usr/local/pgsql/bin... > s.out 2> s.err also. If you have a web site where you can post the files and then include the URL in your replies that might be better than trying cut & paste parts of the output to the mailing list if the output is long (the network one might be nice and short and contain the troublesome system calls and responses if you are lucky).