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 4BD0B32A75C for ; Tue, 19 Oct 2004 04:12:38 +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 18729-02 for ; Tue, 19 Oct 2004 03:12:34 +0000 (GMT) Received: from gizmo03ps.bigpond.com (gizmo03ps.bigpond.com [144.140.71.13]) by svr1.postgresql.org (Postfix) with SMTP id B7FA332A12A for ; Tue, 19 Oct 2004 04:12:32 +0100 (BST) Received: (qmail 19332 invoked from network); 19 Oct 2004 03:12:28 -0000 Received: from unknown (HELO psmam03.bigpond.com) (144.135.25.75) by gizmo03ps.bigpond.com with SMTP; 19 Oct 2004 03:12:28 -0000 Received: from cpe-61-9-197-223.nsw.bigpond.net.au ([61.9.197.223]) by psmam03.bigpond.com(MAM REL_3_4_2a 89/2093648) with SMTP id 2093648; Tue, 19 Oct 2004 13:12:28 +1000 Message-ID: <41748682.3010101@didymodesigns.com.au> Date: Tue, 19 Oct 2004 13:14:10 +1000 From: Ashley Maher User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: postmaster stopps References: <416B4FA1.4010107@didymodesigns.com.au> <27628.1097553294@sss.pgh.pa.us> In-Reply-To: <27628.1097553294@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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/227 X-Sequence-Number: 15220 Tom Lane wrote: >When you've got some evidence to look at, we'll be glad to help you >interpret it, but there's no point in speculating without evidence. > > Thanks Tom, 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 start postgresql with the script by Ryan Kirkpatrick (basis used by the BSD script from the postgresql site). This logs to /usr/local/pgsql/data/serverlog. this is an extract: LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection FATAL: lock file "/usr/local/pgsql/data/postmaster.pid" already exists HINT: Is another postmaster (PID 1427) running in data directory "/usr/local/pgsql/data"? LOG: database system was interrupted at 2004-09-13 11:29:44 EST LOG: checkpoint record is at 0/16982C0 LOG: redo record is at 0/16982C0; undo record is at 0/0; shutdown FALSE LOG: next transaction ID: 37412; next OID: 54829 LOG: database system was not properly shut down; automatic recovery in progress LOG: record with zero length at 0/1698300 LOG: redo is not required LOG: database system is ready As you can see I tried to restart the postmaster before removing the pid 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? As I said I've "googled" but not gotten very far. Regards, Ashley