Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D20609FB5DB for ; Fri, 9 Mar 2007 20:56:46 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 91008-01 for ; Fri, 9 Mar 2007 20:56:42 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from servata.com (ip-216-152-249-241.servata.com [216.152.249.241]) by postgresql.org (Postfix) with ESMTP id 087829FB58D for ; Fri, 9 Mar 2007 20:56:42 -0400 (AST) Received: from [209.162.219.253] (helo=dogma.v10.wvs) by servata.com with esmtpa (Exim 4.50) id 1HPpsz-0000HO-QU; Fri, 09 Mar 2007 16:56:37 -0800 Subject: Re: DBD-pg - server closed the connection unexpectedly From: Jeff Davis To: Frank Bax Cc: pgsql-interfaces@postgresql.org In-Reply-To: <5.2.1.1.0.20070309083841.03938e00@pop6.sympatico.ca> References: <5.2.1.1.0.20070307105703.009ff740@pop6.sympatico.ca> <5.2.1.1.0.20070307105703.009ff740@pop6.sympatico.ca> <5.2.1.1.0.20070309083841.03938e00@pop6.sympatico.ca> Content-Type: text/plain Date: Fri, 09 Mar 2007 16:56:40 -0800 Message-Id: <1173488200.23455.18.camel@dogma.v10.wvs> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.189 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO, SPF_HELO_PASS X-Spam-Level: X-Archive-Number: 200703/23 X-Sequence-Number: 6464 On Fri, 2007-03-09 at 08:44 -0500, Frank Bax wrote: > At 03:20 PM 3/7/07, Tom Lane wrote: > > >Frank Bax writes: > > > Here is a portion of my script. The system() call executes successfully > > > once, then script crashes. Any ideas why this would happen. > > > >What shows up in the postmaster log? Can you get a stack trace from the > >(presumably) crashing backend? > > > Backend is not crashing. When I looked at log on this busy system, I found > out this version is producing numerous warnings about escape sequences in > other scripts. I will attempt to clean that up; so I can isolate > messages. I see a few messages about "unexpected EOF on client > connection"; but I am not certain that they are from my problem script. I had a problem with similar symptoms on FreeBSD where a kernel bug caused a protocol violation. I am using SSL, and messages like "Host is down" appeared in the server logs. I'm not sure what exactly happens when not using SSL. The problem is described here: http://www.freebsd.org/cgi/query-pr.cgi?pr=100172 Thanks to AndrewSN for tracking it down originally. However, you need to post more information to determine the real cause. Regards, Jeff Davis