Re: URGENT : StreamServerPort: bind() failed: Cannotassign - Mailing list pgsql-admin

From Siddharth Rath (sirath)
Subject Re: URGENT : StreamServerPort: bind() failed: Cannotassign
Date
Msg-id 002101c44a7d$0968b140$2c6345ab@amer.cisco.com
Whole thread Raw
In response to Re: URGENT : StreamServerPort: bind() failed: Cannotassign  (Rob <pgadmin@itsbeen.sent.com>)
Responses Re: URGENT : StreamServerPort: bind() failed: Cannotassign
List pgsql-admin
Hi Rob,
Please find the output of "strace -f /apps/systran/postgresql/bin/pg_ctl start -D /apps/systran/postgresql/data-linux >
s.out2> 
s.err"  in the below provided URLs:

http://us.f2.yahoofs.com/bc/40c0ea30_116c8/bc/My+Documents/s.err.err?bfd6OwABBgQwEsbt

http://us.f2.yahoofs.com/bc/40c0ea30_116c8/bc/My+Documents/s.out.out?bfd6OwABCrTeXvUl

I couldnot understand much of the s.err messages. It will be great if you please spare some time to go thru the same
andadvise me 
how to proceed from here.

Thanx and regards
Sidd


-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rob
Sent: Friday, June 04, 2004 1:37 PM
To: sirath@cisco.com
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] URGENT : StreamServerPort: bind() failed: Cannotassign


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).

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings


pgsql-admin by date:

Previous
From: "Paul Gimpelj"
Date:
Subject: win32/w98 'How much/minimum disk space req'd for postgresql?' [ref:ppg.%001%^]
Next
From: Gaetano Mendola
Date:
Subject: Re: determining when a database was created