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

Hi Rob,
Thanx for the response.
The O/P of netstat -na | grep 5432 is :

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:*

Surprisingly .s.PGSQL.5432 file is not getting created in /tmp directory ( I believe this should be created).
Details of /tmp is given below:

/>ls -ls | grep tmp
0 drwxrwxrwt 2 root root 140 Jun 3 23:14 tmp

/tmp >ls -al
total 64
drwxrwxrwt 2 root root 140 Jun 3 23:14 .
drwxr-xr-x 21 root root 4096 Jun 3 12:20 ..
-rw-r--r-- 1 root root 2037 Jun 3 12:21 bootinfo
-rwxr-xr-x 1 root root 578 Jun 3 23:14 find_perl5
-rw-r--r-- 1 root root 43732 Jun 3 23:14 mk_accounts_client
-rw-r--r-- 1 root root 1828 Jun 3 12:21 prtdiag-osaka.2004:06:03:12:21:22
-rw-r--r-- 1 root root 23 Jun 3 23:14 sendme.osaka

Please let me know how to proceed from here.

Thanx and regards
Sidd

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Rob
Sent: Friday, June 04, 2004 2:47 AM
To: sirath(at)cisco(dot)com; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] URGENT : StreamServerPort: bind() failed: Cannotassign

Siddharth Rath (sirath) wrote:
>>
>>The O/P of >netstat -plunt | grep 5432
>>

what about just :
netstat -na | grep 5432

to see if any 5432 stuff is hanging around and if so in
what state...

It may be that you are missing the evidence of the problem because you
filtered -plut (process id, listening, udp, tcp) but the error msg talks
about a StreamServerPort bind problem but those unix domain lines won't
be displayed with that set of filters and so it may be some weirdness
with stream and/or lock files in your /tmp directory? Just a guess.

Rob

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)