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 1BA83329EBB for ; Tue, 19 Oct 2004 16:51:35 +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 39908-09 for ; Tue, 19 Oct 2004 15:51:24 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 89541329E4C for ; Tue, 19 Oct 2004 16:51:23 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9JFpLYV016385; Tue, 19 Oct 2004 11:51:21 -0400 (EDT) To: Andrew Sullivan Cc: pgsql-admin@postgresql.org Subject: Re: postmaster stopps In-reply-to: <20041019152846.GD3359@phlogiston.dyndns.org> References: <416B4FA1.4010107@didymodesigns.com.au> <27628.1097553294@sss.pgh.pa.us> <41748682.3010101@didymodesigns.com.au> <20041019152846.GD3359@phlogiston.dyndns.org> Comments: In-reply-to Andrew Sullivan message dated "Tue, 19 Oct 2004 11:28:46 -0400" Date: Tue, 19 Oct 2004 11:51:21 -0400 Message-ID: <16384.1098201081@sss.pgh.pa.us> From: Tom Lane 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/232 X-Sequence-Number: 15225 Andrew Sullivan writes: >> 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. Strictly speaking, it's possible that the postmaster died earlier, leaving orphan backends that logged these messages sometime later. My private suspicion is that the postmaster is being killed either because of exceeding a ulimit setting or by the infamous Linux "OOM kill" kernel bug^H^H^Hfeature. In either case, the postmaster log will not be the place to look; instead check for a core file left behind or for a notice in the kernel log about OOM kill. But really the first thing to do is to check that the postmaster is being started under reasonable ulimit settings ... and while you are at it, make sure it's "ulimit -c unlimited" not "ulimit -c 0". The latter would prevent a core file from being dropped. If it's not an OOM kill situation then the core file is the only way to learn more. regards, tom lane