Tom Lane-2 wrote: > > Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx> writes: >> Yes, with gssapi. > > Well, then we have our smoking gun, but it's still not clear *why* > the setsockopt() call failed. > > regards, tom lane > I know why it failed. I just had two independent database servers (8.4.4 and 9.0.0 on Solaris) crash AT THE SAME TIME with the exact same error. Reason? nmap. Our system administrator ran nmap on the subnet in question to scan for hosts with open TCP ports, which caused the setsockopt() call to fail. I know the bug has already been fixed, but it's good to know anyway. --Al -- View this message in context: http://postgresql.1045698.n5.nabble.com/Postgres-Crash-tp3299776p3888697.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
