pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Siddharth Rath (sirath) <sirath@cisco.com>
To: 'Rob' <pgadmin@itsbeen.sent.com>
To: pgsql-admin@postgresql.org
Subject: Re: URGENT : StreamServerPort: bind() failed: Cannotassign
Date: Fri, 4 Jun 2004 13:06:48 -0700
Message-ID: <001b01c44a6f$7a072390$2c6345ab@amer.cisco.com> (raw)
In-Reply-To: <40C0BB4C.5050008@itsbeen.sent.com>

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


-----Original Message-----
From: Rob [mailto:pgadmin@itsbeen.sent.com] 
Sent: Friday, June 04, 2004 11:11 AM
To: sirath@cisco.com; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] URGENT : StreamServerPort: bind() failed: Cannotassign


Tom Lane wrote:
> "Siddharth Rath (sirath)" <sirath@cisco.com> 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.




view thread (16+ messages)  latest in thread

Message-ID: <001b01c44a6f$7a072390$2c6345ab@amer.cisco.com>
Permalink:  ../001b01c44a6f$7a072390$2c6345ab@amer.cisco.com/
Also on:    postgresql.org/message-id/001b01c44a6f$7a072390$2c6345ab@amer.cisco.com

 · 

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: sirath@cisco.com, pgadmin@itsbeen.sent.com
  Subject: Re: URGENT : StreamServerPort: bind() failed: Cannotassign
  In-Reply-To: <001b01c44a6f$7a072390$2c6345ab@amer.cisco.com>
  References: <40C0BB4C.5050008@itsbeen.sent.com> <001b01c44a6f$7a072390$2c6345ab@amer.cisco.com>

* 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