DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk;
	h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=5qXxEEgRLDAHVtMQgMZT0AZ1qp8iqDVTctYgbL7LzP3ixzbpl4JgXkfnAv7dPYe59GQDXow0ZPvG1AwDZk4gNbQzS8m2HxWVkNQmSG3AZSqvmIv3XXPEQigA/T56Kgr1X2wHbZwicW+q8/PAR51rR1cIS2SajVlGFu+OnJ83atw=;
Message-ID: <738034.69424.qm@web25805.mail.ukl.yahoo.com>
Date: Fri, 27 Mar 2009 09:47:20 +0000 (GMT)
From: val <valiouk@yahoo.co.uk>
Subject: Re: pg_ctlcluster not logging error (memory problem likely)
To: Tom Lane <tgl@sss.pgh.pa.us>, Tony Webb <amw@sanger.ac.uk>
Cc: pgsql-admin@postgresql.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable


> Tom Lane wrote:
> > Tony Webb <amw@sanger.ac.uk>
> writes:
> >=A0=A0=A0
> >> 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.
> >>=A0 =A0=A0=A0
> >=20
> >=A0=A0=A0
> >> When the cluster is up and running it seems to
> write normally to these locations.
> >>=A0 =A0=A0=A0
> >=20
> >=A0=A0=A0
> >> Could pg_ctlcluster be writing somewhere else?
> >>=A0 =A0=A0=A0
> >=20
> > I'm not familar with pg_ctlcluster, but it seems
> possible that the
> > Debian setup is such that messages issued early in
> startup go somewhere
> > else than where messages go once the postmaster is
> fully up and running.
> > In particular, until the postmaster has absorbed the
> logging settings
> > in postgresql.conf, it's *always* going to write to
> its stderr.=A0 I've
> > seen startup scripts that send postmaster stderr to
> /dev/null :-(
> > because they suppose that pointing log_destination to
> syslog or some
> > such means that everything of interest will go there.
> >=20
> > Advice is to look into the startup script, see where
> it sends
> > postmaster's stderr, and fix that if it's not
> someplace you can read.
> >=20
> > =A0=A0=A0 =A0=A0=A0
> =A0=A0=A0 regards, tom lane
> >=A0=A0=A0
> Thanks Tom.
>=20
> Good advice - I'll check out the pg_ctlcluster script.
>=20
> I've not looked yet. I'm hoping it's a shell script, not
> perl :-).
>=20
> Cheers
>=20
> Pif
>

It is a perl script :-). The purpose of which is to make it easier to start=
 and stop several postgres clusters which might not even be the same versio=
n.

It usually writes to /var/log/postgresql/postgresql-X.X-main.log. But you c=
an just try starting the postmaster from the command line with /etc/init.d/=
postgresql-X.X star, that way if there were any errors you will see them pr=
inted on the terminal.

Regards

Val=0A=0A=0A