Re: URGENT : StreamServerPort: bind() failed: Cannotassign requested address

Hi Mike,
Thanx for the response. The ps -A don't have POSTMASTER and I did check it earlier too. Do you foresee any issue with
Linux
configuration or is it the POSTGRES issue? Please let me know how to proceed from here.

Thanx in advance.

Regards
Sidd

-----Original Message-----
From: mike g [mailto:mike@thegodshalls.com]
Sent: Thursday, June 03, 2004 8:56 PM
To: sirath@cisco.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] URGENT : StreamServerPort: bind() failed: Cannotassign requested address


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
dbafter 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
thatthe 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