Re: URGENT : StreamServerPort: bind() failed: Cannot assign requested address

Hi Tom,
Thanx for the reply and suggestion. Actually , I did wait for more than 5 hrs before posting this issue in this alias. It will be
really great if you can advise on how to proceed from here. Does the below information points to any issue with my Linux Box
configuration is it an issue with POSTGRES:

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

Thanx in advance.

Regards
Sidd

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Thursday, June 03, 2004 9:05 PM
To: sirath(at)cisco(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] URGENT : StreamServerPort: bind() failed: Cannot assign requested address

"Siddharth Rath (sirath)" <sirath(at)cisco(dot)com> writes:
> 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

Did you try waiting a while, as suggested by the error message? Many TCP stacks have a timeout before they will let a pre-existing
port number be reassigned. (This is to prevent any risk of packets for old connections getting delivered to the new owner of the
port.)

regards, tom lane