Skip site navigation (1) Skip section navigation (2)

Re: Why would PostgreSQL close the 'backend unexpectedly'

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Wouter van Vliet <wouter(at)springt(dot)nl>
Cc: <pgsql-admin(at)postgresql(dot)org>,"Wouter (at) Witbier" <wouter(at)witbier(dot)myweb(dot)nl>
Subject: Re: Why would PostgreSQL close the 'backend unexpectedly'
Date: 2002-09-30 15:00:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Mon, 30 Sep 2002, Wouter van Vliet wrote:

> Hi Folks,
> I'm running a server, 1gig ram, 1ghz cpu, enough hd space. On it, s'pose you
> guessed it, i'm having some problems with PostgresSQL. Also on the server,
> there is a website, about 70 active users online at the same time. Results
> in quite some memory usage. The gig is used in full for the most of the
> time.
> Now comes the problem, every now and then, it seemed to be totally random
> (since it is a computer, it can't be, I know), there appears an error in the
> error log saying: PgRead() connection failed: the database system closed
> backend unexpectedly. It might be in some other phrase (somehow, the back of
> my mind is whispering: Backend closed the channel unexpectedly), but just at
> this moment I couldn't find the exact words in the logs. If you know how to
> solve this problem, you'll probalby know what I mean.

The log in the area of the message should give some hints (it'll probably
say something like Backend closed with signal 11 or something like that
anyway).  You may also want to look to see if you've got a core file in
your database directory.

In response to

pgsql-admin by date

Next:From: Bruce MomjianDate: 2002-09-30 15:06:27
Subject: Re: [DBmirror Issue] recordchange() dies in packageData unless
Previous:From: Andrew SullivanDate: 2002-09-30 14:33:09
Subject: Re: old db on a new system

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group