From: | "Siddharth Rath (sirath)" <sirath(at)cisco(dot)com> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "'Rob'" <pgadmin(at)itsbeen(dot)sent(dot)com>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: URGENT : StreamServerPort: bind() failed: Cannotassign |
Date: | 2004-06-04 18:01:43 |
Message-ID: | 001201c44a5d$ff7ef1e0$2c6345ab@amer.cisco.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Tom,
I don't understand what you meant by "This is a kernel-level issue and you need to be inquiring ..." . If you please tell me what
and how I should enquire and what may be the possible reason for this bind call failure then I can contact our Sysadmin to help me
out.
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 Tom Lane
Sent: Friday, June 04, 2004 10:01 AM
To: sirath(at)cisco(dot)com
Cc: 'Rob'; pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] URGENT : StreamServerPort: bind() failed: Cannotassign
"Siddharth Rath (sirath)" <sirath(at)cisco(dot)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
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Rob | 2004-06-04 18:11:24 | Re: URGENT : StreamServerPort: bind() failed: Cannotassign |
Previous Message | Chris Hoover | 2004-06-04 17:30:45 | Re: Setting vacuum_mem for vacuumdb utility |