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 ACFFFD1B220 for ; Fri, 4 Jun 2004 15:17:05 -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 54462-01 for ; Fri, 4 Jun 2004 18:17:03 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by svr1.postgresql.org (Postfix) with ESMTP id 39F43D1B17C for ; Fri, 4 Jun 2004 15:16:58 -0300 (ADT) X-Sasl-enc: oGtHlE4OS0jj+7dmqwCeHQ 1086373016 Received: from [10.10.12.12] (unknown [198.144.200.210]) by www.fastmail.fm (Postfix) with ESMTP id 62A11C042D6; Fri, 4 Jun 2004 14:16:56 -0400 (EDT) Message-ID: <40C0BB4C.5050008@itsbeen.sent.com> Date: Fri, 04 Jun 2004 11:11:24 -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, pgsql-admin@postgresql.org Subject: Re: URGENT : StreamServerPort: bind() failed: Cannotassign References: <001a01c44a4e$d945eec0$15b8a943@amer.cisco.com> <3951.1086368460@sss.pgh.pa.us> In-Reply-To: <3951.1086368460@sss.pgh.pa.us> 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/44 X-Sequence-Number: 13704 Tom Lane wrote: > "Siddharth Rath (sirath)" writes: > >>Surprisingly .s.PGSQL.5432 file is not getting created in /tmp directory ( I believe this should be created). > > > No, it shouldn't, because that is associated with the creation of the > Unix socket file, which happens after creation of the TCP socket. > > Given that you're seeing a kernel error on attempt to create the TCP > socket, I'm convinced that you're wasting your time thinking about > Postgres-internal conditions. This is a kernel-level issue and you > need to be inquiring into what state the kernel is in that is making > it reject the bind(). > > regards, tom lane You might try to set up a simple web server like thttpd or simpler on port 5432 and that way you can troubleshoot opening the socket listener is a more simple environment with possibly some different error messages. Also you can run a simple perl/python/ruby/java script (like this http://myclass.missouri.edu/~atb6x2/NETSERV/NS_serverpl.html) to (try to) open a socket listener on 5432 and have it just sit there. If you do that the output from strace would be shorter than trying to start up pg and you might get an idea where the socket problem is.