Re: postgres startup failure

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Matt Bartolome <mattxbart(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: postgres startup failure
Date: 2010-05-20 21:44:07
Message-ID: 9224.1274391847@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Matt Bartolome <mattxbart(at)gmail(dot)com> writes:
> gdb output...

> DEBUG: -----------------------------------------
> DEBUG: invoking IpcMemoryCreate(size=32595968)
> DEBUG: max_safe_fds = 980, usable_fds = 1000, already_open = 10
> Detaching after fork from child process 18310.
> Detaching after fork from child process 18311.

> Program exited with code 01.

Huh. So it called exit(1) somewhere, without generating any error
message first. That's pretty unfriendly. Try setting a breakpoint
at exit(), and if you can get it to stop there, get a stack trace
from that point.

Dunno if you're familiar with gdb, but the quick way to do this is
to say
b exit
and then the "run" command. It's possible that the attempt to set
the breakpoint will fail because libc.so isn't loaded yet, in
which case you need two steps:
b main
run ...
when control stops at main:
b exit
continue

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Matt Bartolome 2010-05-20 22:07:10 Re: postgres startup failure
Previous Message Alvaro Herrera 2010-05-20 21:24:59 Re: Postgres stats collector showing high disk I/O