Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id BD098B5DBEC for ; Thu, 19 May 2011 21:07:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 79781-04 for ; Fri, 20 May 2011 00:07:25 +0000 (UTC) X-Greylist: delayed 02:19:11.187347 by SQLgrey-1.7.6 Received: from mxdfbv01i.wellsfargo.com (mxdfbv01i.wellsfargo.com [151.151.26.135]) by mail.postgresql.org (Postfix) with ESMTP id 16521B5DBBF for ; Thu, 19 May 2011 21:07:24 -0300 (ADT) Received: from mxdcmv02i.wellsfargo.com (mxdcmv02i.wellsfargo.com [151.151.26.138]) by mxdfbv01i.wellsfargo.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p4JLmHIt030044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 19 May 2011 21:48:17 GMT Received: from mxicmv02.wellsfargo.com (mxicmv02.wellsfargo.com [10.91.24.72]) by mxdcmv02i.wellsfargo.com (Switch-3.4.1/Switch-3.4.1) with ESMTP id p4JLmBc6030351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 19 May 2011 21:48:12 GMT Received: from mxiinx02.wellsfargo.com (mxiinx02.wellsfargo.com [162.102.137.61]) by mxicmv02.wellsfargo.com (Switch-3.4.1/Switch-3.4.1) with ESMTP id p4JLmBNF002698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 19 May 2011 21:48:11 GMT Received: from mxv04.wellsfargo.com (mxv04.wellsfargo.com [10.91.194.150]) by mxiinx02.wellsfargo.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p4JLmA5N028488; Thu, 19 May 2011 21:48:10 GMT Received: from mxv04.wellsfargo.com (localhost [127.0.0.1]) by mxv04.wellsfargo.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id p4JLmAoi019622; Thu, 19 May 2011 16:48:10 -0500 Received: (from root@localhost) by mxv04.wellsfargo.com (Switch-3.3.2/Switch-3.3.0/Submit) id p4JLmAXn019562 for shieldj@wellsfargo.com; Thu, 19 May 2011 16:48:10 -0500 Message-Id: <201105192148.p4JLmAXn019562@mxv04.wellsfargo.com> turn-Path: Received: from [127.0.0.1] by mxissv91.wellsfargo.com with LMTPS (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 17 May 2011 22:52:26 +0000 Received: from mxdinv04i.wellsfargo.com (mxdinv04i.wellsfargo.com [151.151.26.151]) by mxissv91.wellsfargo.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p4HMqQcE026555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 17 May 2011 22:52:26 GMT Received: from mx1.hub.org (mx1.hub.org [200.46.208.106]) by mxdinv04i.wellsfargo.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p4HMqP3W014153 for ; Tue, 17 May 2011 22:52:25 GMT Received: from postgresql.org (mail.postgresql.org [200.46.204.86]) by mx1.hub.org (Postfix) with ESMTP id 7B70C326266D; Tue, 17 May 2011 22:52:20 +0000 (UTC) Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 47658B5DBE0 for ; Tue, 17 May 2011 19:52:11 -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 15756-04 for ; Tue, 17 May 2011 22:52:04 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f46.google.com (mail-bw0-f46.google.com [209.85.214.46]) by mail.postgresql.org (Postfix) with ESMTP id 1A500B5DBDE for ; Tue, 17 May 2011 19:52:02 -0300 (ADT) Received: by bwz15 with SMTP id 15so910123bwz.19 for ; Tue, 17 May 2011 15:52:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=SisQ/AzrTPmYaD9XP2z8eKKH0jmLnZf2XOT51QzUj9o=; b=YVcAWJCPK0klTjnhVrIfDhbo7u2qTnMDaX7PGBdjp4xt/Pz4628HulSHA4DLzP+emF r2F0sWISeD/KCWMFJKybDKIrr6tjkYq0dTW0O6VrZMI3Xxc7C46PySV8HC8jVjogH7oK DgtKqUHtlr0bpEiav69r/8bD/WiIfN4dZ3dGY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=hWPxXJ6z/KQH2IrMCjmXpo/saHzLn+AizFiRkB9jMustXs4qdRBsjAKNx3WDISv4Ig Hd7qPy7dt+ddXMBDNLqbTvePt+qtTtwjlJiFKtaYFN6RH5u29UwZdaNNyXax72HZ3ZtW +jP7eIxE/v84HWzOzCSFEdPemCiY4pwTdwXmM= MIME-Version: 1.0 Received: by 10.204.154.215 with SMTP id p23mr1195287bkw.113.1305672722222; Tue, 17 May 2011 15:52:02 -0700 (PDT) Received: by 10.204.98.210 with HTTP; Tue, 17 May 2011 15:52:02 -0700 (PDT) In-Reply-To: References: Date: Wed, 18 May 2011 08:22:02 +0930 X-WFB-Orig-Message-ID: Subject: Re: Unable To Establish Connections From: Sam Stearns To: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Mailing-List: pgsql-admin Precedence: bulk X-MM-CM-Score: 0.00% X-MM-CM-Analysis: v=1.1 cv=9qWcnxpLfWyOsZopf8Nxb+enPMROfNoL/v1AsxOvNkg= c=1 sm=1 a=JaP9UDOblbgA:10 a=nDghuxUhq_wA:10 a=8nJEP1OIZ-IA:10 a=kQW87JryYMgaD5Fy6jdT0Q==:17 a=pGLkceISAAAA:8 a=epTmVMiNAAAA:8 a=Ip-_zVxn3MPCXhbgDNIA:9 a=w3A5B_fMsqtz9ygvnsYA:7 a=wPNLvfGTeEIA:10 a=MSl-tDqOz04A:10 a=YObXiYvaVLwA:10 a=kQW87JryYMgaD5Fy6jdT0Q==:117 X-MM-CT-Classification: not spam X-MM-CT-RefID: str=0001.0A090209.4DD2FC2A.003C:SCFSTAT4386128, ss=1, re=-4.000, fgs=0 X-SMI-MM-WFB-Virus-Classification: Unscannable X-WFB-Orig-Env-Recipients: shieldj@wellsfargo.com X-WFB-Orig-Hdr-To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.887 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, MSGID_FROM_MTA_HEADER=0.001, RFC_ABUSE_POST=0.001, T_TO_NO_BRKTS_FREEMAIL=0.01 X-Spam-Level: X-Archive-Number: 201105/147 X-Sequence-Number: 37584 Anyone have any ideas on this? We're an ISP. I was thinking of the possibility of a hack attempt. On Tue, May 17, 2011 at 6:52 PM, Sam Stearns wrote: > Howdy, > > Environment: > > Postgres 8.2.3 > Solaris 10 > > We were unable to make a remote postgres connection for ~2 hours this > afternoon. =A0Receiving the following message in the postgres log every > 30 seconds: > > LOG: =A0expected password response, got message type 88 > > Connection limit is 300. =A017 active connections at the time. =A0Bounced > postgres successfully but the above error message was still being > logged. =A0About 20 minutes later the error message stopped and > connections started to re-establish. > > Any ideas? > > Thank you, > > Sam > --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin