"incomplete startup packet" on SGI

From: David Rysdam <drysdam(at)ll(dot)mit(dot)edu>
To: "pg >> Postgres General" <pgsql-general(at)postgresql(dot)org>
Subject: "incomplete startup packet" on SGI
Date: 2005-12-13 20:12:26
Message-ID: 439F2B2A.6030905@ll.mit.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have a working 8.1 server running on Linux and I can connect to it
from other Linux clients. I built postgresql 8.1 on an SGI (using
--without-readline but otherwise stock) and it compiled OK and installed
fine. But when I try to connect to the Linux server I get "could not
send startup packet: transport endpoint is not connected" on the client
end and "incomplete startup packet" on the server end. Connectivity
between the two machines is working.

I could find basically no useful references to the former and the only
references to the latter were portscans and the like.

Browsing the source, I see a couple places that message could come
from. One relates to SSL, which the output from configure says is
turned off on both client and server. The other is just a generic comm
error--but would could cause a partial failure like that?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John Taber 2005-12-13 20:34:50 php + postgresql pg_connect problem
Previous Message kbforge 2005-12-13 20:07:03 New release: - kbforge 1.20 Free desktop search application with PGSQL database option