X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C211A32A033 for ; Tue, 19 Oct 2004 16:28:55 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30909-07 for ; Tue, 19 Oct 2004 15:28:49 +0000 (GMT) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by svr1.postgresql.org (Postfix) with SMTP id 4869132A01F for ; Tue, 19 Oct 2004 16:28:48 +0100 (BST) Received: from unknown (HELO phlogiston.dydns.org) (a.sullivan@rogers.com@65.49.125.184 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 19 Oct 2004 15:28:47 -0000 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 3FA254058; Tue, 19 Oct 2004 11:28:46 -0400 (EDT) Date: Tue, 19 Oct 2004 11:28:46 -0400 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: postmaster stopps Message-ID: <20041019152846.GD3359@phlogiston.dyndns.org> Mail-Followup-To: pgsql-admin@postgresql.org References: <416B4FA1.4010107@didymodesigns.com.au> <27628.1097553294@sss.pgh.pa.us> <41748682.3010101@didymodesigns.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41748682.3010101@didymodesigns.com.au> User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/231 X-Sequence-Number: 15224 On Tue, Oct 19, 2004 at 01:14:10PM +1000, Ashley Maher wrote: > My original post stated I'd had the postmaster stop without explanation. > I now have log files. I can see nothing in messaegs or syslog of interest. I agree there's not much there: > LOG: unexpected EOF on client connection > LOG: unexpected EOF on client connection > LOG: unexpected EOF on client connection > LOG: unexpected EOF on client connection These are cases where the client has gone away without shutting down its connection properly. At the TCP timeout, the postmaster checks the client, discovers it isn't there, and shuts down the connection. So this tells you that a client disconnected abnormally, but it also tells you that the postmaster was working correctly then. > FATAL: lock file "/usr/local/pgsql/data/postmaster.pid" already exists And this is your start up attempt. > file. There is alot of the "unexpected EOF on client connection". I've > done a search for the cause of this error without much success, in the > hope it is the reason the postmaster dies. Is this a hint to my problem? I doubt it very much. I think you probably need to increase the verbosity of your logging in order to make it clearer what's going on. Also, timestamps would help: from the output that's there, you can't tell how long it was between the last known-alive postmaster event (unexpected EOF) and the start-up attempt. You'll probably want to send the output through a log rotator if you increase the verbosity: multi-gig log files aren't so good. A -- Andrew Sullivan | ajs@crankycanuck.ca The plural of anecdote is not data. --Roger Brinner