From: Tony Webb <amw@sanger.ac.uk>
To: pgsql-admin@postgresql.org
Subject: pg_ctlcluster not logging error (memory problem likely)
Date: Thu, 26 Mar 2009 09:26:13 +0000
Message-ID: <49CB4A35.1030002@sanger.ac.uk> (raw)
Hi,
I'm trying to find out why my cluster won't start. It looks like I'm
pushing up max_connections too high although I think my memory and
semaphore settings are OK. Thing is, when the cluster fails to start I
can't see any errors in pg_log or in /var/log/messages.
When the cluster is up and running it seems to write normally to these
locations.
Could pg_ctlcluster be writing somewhere else? can I do something to see
more verbose messages (more than the empty string) other than setting
log parameters in postgres.conf?
I'm running 8.3 on Debian btw.
Cheers
Pif
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: amw@sanger.ac.uk
Subject: Re: pg_ctlcluster not logging error (memory problem likely)
In-Reply-To: <49CB4A35.1030002@sanger.ac.uk>
* 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