Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 53CE89FB615 for ; Mon, 2 Apr 2007 06:39:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 23252-07 for ; Mon, 2 Apr 2007 06:39:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 036AA9FA4AD for ; Mon, 2 Apr 2007 06:39:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mercure.sigma.fr (mercure.sigma.fr [195.25.81.9]) by svr4.postgresql.org (Postfix) with ESMTP id 032B55AF0B2 for ; Mon, 2 Apr 2007 09:39:33 +0000 (GMT) Received: from localhost (localhost.localdomain [127.0.0.1]) by mercure.sigma.fr (Postfix) with ESMTP id 8FB2046863 for ; Mon, 2 Apr 2007 11:39:30 +0200 (CEST) Received: from mercure.sigma.fr ([127.0.0.1]) by localhost (mercure-1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01256-152 for ; Mon, 2 Apr 2007 11:39:30 +0200 (CEST) Received: from marc (unknown [192.168.1.1]) by mercure.sigma.fr (Postfix) with ESMTP id 7164946855 for ; Mon, 2 Apr 2007 11:39:30 +0200 (CEST) From: Marc Cousin Organization: Sigma Informatique Subject: Re: SSL broken pipe Date: Mon, 2 Apr 2007 11:39:29 +0200 User-Agent: KMail/1.9.6 Cc: pgsql-admin@postgresql.org References: <200703281443.14234.mcousin@sigma.fr> <4544e0330703291040y504091f1v8df2597629a75c3a@mail.gmail.com> In-Reply-To: <4544e0330703291040y504091f1v8df2597629a75c3a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline To: Undisclosed.Recipients: ; Message-Id: <200704021139.29632.mcousin@sigma.fr> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=BAYES_50=0.001 X-Spam-Level: X-Archive-Number: 200704/7 X-Sequence-Number: 25071 It seems to be what occurred : the windows client crashed ... Still, it's a bit of a problem to have a filesystem full in a matter of minutes just because a client machine crashed while having an SSL connection opened on the postgresql server... On Thursday 29 March 2007 19:40:18 Peter Koczan wrote: > I saw this on one of my servers a few weeks ago (it was running > postgres 7.4under linux, and I believe the users in question were just > running psql). I > talked to someone more knowledgeable about SSL about this, and he said that > these errors are usually due to some abrupt disconnection somewhere (in any > application, not just postgres). My best guess is that the connection was > broken while data was trying to be fed, causing the server to say "Hey, > where'd you go?...Here's your data again...Hey where'd you go?..." ad > infinitum. > > Other than that, I have no idea what would cause this or how to fix it > short of restarting the postgres server or rebooting the machine. > > That being said, I don't know a whole lot about SSL, and people with more > knowledge are more than welcome to weigh in. > > Peter >