From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: postmaster stopps
Date: Tue, 19 Oct 2004 11:28:46 -0400
Message-ID: <20041019152846.GD3359@phlogiston.dyndns.org> (raw)
In-Reply-To: <41748682.3010101@didymodesigns.com.au>
References: <416B4FA1.4010107@didymodesigns.com.au>
<27628.1097553294@sss.pgh.pa.us>
<41748682.3010101@didymodesigns.com.au>
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
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: ajs@crankycanuck.ca
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>
* 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