From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robin Lynn Frank <rlfrank(at)paradigm-omega(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgresql dies without saying why |
Date: | 2004-01-10 19:10:31 |
Message-ID: | 11662.1073761831@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Robin Lynn Frank <rlfrank(at)paradigm-omega(dot)com> writes:
> The following appears when the machine is booted, but somehow postgresql
> silently dies (no message in logs). If I then use the same init script that
> is used during startup, it starts just fine and keeps running. Any thoughts
> on how I can determine/avoid the problem would be appreciated.
The postmaster will generally complain before quitting. I suspect you
have things configured so that the complaint message goes nowhere but
/dev/null. I'd suggest altering the init script to send postmaster's
stdout and stderr into a specific log file (make sure postgres has
permission to write this log file, too). Turn off syslog logging if
you have that selected in postgresql.conf.
Once you've managed to obtain a failure message, write back if you need
help interpreting it ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-01-10 19:15:19 | Re: psql \d option list overloaded |
Previous Message | Tom Lane | 2004-01-10 19:05:57 | Re: Bug in functions returning setof where table has dropped column? |