From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "otisg" <otisg(at)iVillage(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Cannot (re)start PostgreSQL |
Date: | 2002-05-06 04:03:28 |
Message-ID: | 200205060003.28600.lamar.owen@wgcr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Monday 06 May 2002 12:04 am, Tom Lane wrote:
> "otisg" <otisg(at)iVillage(dot)com> writes:
> > Is there a way to get a more verbose error message from PostgreSQL that
> > will tell me why I can't start the DB?
> I'd venture that your /etc/rc script is preventing Postgres from telling
> you anything useful. Try starting PG by hand ... or at the very least,
> find out what the script is doing with the postmaster's error output.
For debugging purposes, either editing /etc/rc.d/init.d/postgresql to change
the output redirect, or enabling syslog as documented in
/usr/share/doc/postgresql-7.2 (or 7.2.1, as applicable).
> There are way too many of those scripts that think routing stderr
> to /dev/null is a good idea.
And until our stderr is rollable it will remain a good idea. Sorry. Syslog
is the best bet with our current non-rollable stderr.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-05-06 04:04:16 | Re: Cannot (re)start PostgreSQL |
Previous Message | otisg | 2002-05-06 03:38:21 | Cannot (re)start PostgreSQL |