Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 744791337C11 for ; Thu, 17 Mar 2011 14:03:29 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 53529-07 for ; Thu, 17 Mar 2011 17:03:19 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mail.postgresql.org (Postfix) with ESMTP id F3D521337C0D for ; Thu, 17 Mar 2011 14:03:18 -0300 (ADT) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Q0GbW-0005qZ-4l for pgsql-admin@postgresql.org; Thu, 17 Mar 2011 10:03:18 -0700 Date: Thu, 17 Mar 2011 10:03:18 -0700 (PDT) From: agfk To: pgsql-admin@postgresql.org Message-ID: <1300381398135-3888697.post@n5.nabble.com> In-Reply-To: <14434.1291956744@sss.pgh.pa.us> References: <68B59BEDCD36854AADBDF17E91B2937A07844CD029@EXCHMAIL.staff.internode.com.au> <68B59BEDCD36854AADBDF17E91B2937A07844CD02E@EXCHMAIL.staff.internode.com.au> <13055.1291952802@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD04D@EXCHMAIL.staff.internode.com.au> <13945.1291954973@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD059@EXCHMAIL.staff.internode.com.au> <14104.1291955542@sss.pgh.pa.us> <68B59BEDCD36854AADBDF17E91B2937A07844CD061@EXCHMAIL.staff.internode.com.au> <14434.1291956744@sss.pgh.pa.us> Subject: Re: Postgres Crash MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.757 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, T_FRT_STOCK2=0.01, T_TO_NO_BRKTS_FREEMAIL=0.01, URI_HEX=1.122 X-Spam-Level: X-Archive-Number: 201103/193 X-Sequence-Number: 37065 Tom Lane-2 wrote: > > Samuel Stearns <SStearns@internode.com.au> 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.