pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Sullivan <ajs@crankycanuck.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: postmaster stopps
Date: Tue, 19 Oct 2004 11:51:21 -0400
Message-ID: <16384.1098201081@sss.pgh.pa.us> (raw)
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>

Andrew Sullivan <ajs@crankycanuck.ca> 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



view thread (5+ messages)

Message-ID: <16384.1098201081@sss.pgh.pa.us>
Permalink:  ../16384.1098201081@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16384.1098201081@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ajs@crankycanuck.ca
  Subject: Re: postmaster stopps
  In-Reply-To: <16384.1098201081@sss.pgh.pa.us>
  References: <416B4FA1.4010107@didymodesigns.com.au> <27628.1097553294@sss.pgh.pa.us> <41748682.3010101@didymodesigns.com.au> <20041019152846.GD3359@phlogiston.dyndns.org> <16384.1098201081@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox