unexplainable error

Started by pobox@verysmall.orgover 18 years ago3 messagesgeneral
Jump to latest
#1pobox@verysmall.org
pobox@verysmall.org

I have Apache/php/PostgreSQL on FreeBSD, all latest stable versions.

Every time, after mass import into the database (it's a development
server, so the import updates the database with full dump from the
production server) - the first several clicks on the development web
site return -

PGSQL ERROR: FATAL: terminating connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

After hitting few times the refresh button of the browser, all is back
to normal until the next import.

If the FreeBSD is restarted before that, the problem does not exist.

Could anybody advice on the possible reason?

Kind regards,
Iv

#2Sam Mason
sam@samason.me.uk
In reply to: pobox@verysmall.org (#1)
Re: unexplainable error

On Fri, Nov 16, 2007 at 01:58:21PM +0100, pobox@verysmall.org wrote:

Every time, after mass import into the database (it's a development
server, so the import updates the database with full dump from the
production server) - the first several clicks on the development web
site return -

PGSQL ERROR: FATAL: terminating connection due to administrator command
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

My only guess would be something to do with a strange interaction with
connection pooling.

Sam

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: pobox@verysmall.org (#1)
Re: unexplainable error

"pobox@verysmall.org" <pobox@verysmall.org> writes:

I have Apache/php/PostgreSQL on FreeBSD, all latest stable versions.
Every time, after mass import into the database (it's a development
server, so the import updates the database with full dump from the
production server) - the first several clicks on the development web
site return -

PGSQL ERROR: FATAL: terminating connection due to administrator command

This means that something sent the backend a SIGTERM signal. You need
to find out what's doing that.

regards, tom lane