Hi
Not sure if this is helpful, but...
Am I doing this correctly, anything else to try before "pulling the plug"?
thanks,
PHilip
# gdb postmaster 29214
GNU gdb 19991004
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux"...
postmaster: No such file or directory.
/usr/local/src/29214: No such file or directory.
Attaching to Pid 29214
0x4013da02 in ?? ()
(gdb) bt
#0 0x4013da02 in ?? ()
#1 0x80e07b1 in ?? ()
#2 0x80e0239 in ?? ()
#3 0x80dfdb3 in ?? ()
#4 0x80c3fa5 in ?? ()
#5 0x400a39cb in ?? ()
(gdb) info frame
Stack level 0, frame at 0xbffff400:
eip = 0x4013da02; saved eip 0x80e07b1
called by frame at 0xbffff414
Arglist at 0xbffff400, args:
Locals at 0xbffff400, Previous frame's sp is 0x0
Saved registers:
ebp at 0xbffff400, eip at 0xbffff404
On Fri, 11 May 2001, Tom Lane wrote:
> Philip Crotwell <crotwell@seis.sc.edu> writes:
> > I am running postgres7.1 on redhat 6.2 and my database has gone belly up.
>
> > I know i am not supposed to "kill -9 " the postmaster, but it has become
> > completely unresponsive. pgsql just hangs as does stopping with the
> > rc.d script.
>
> Actually, kill -9 should be perfectly safe in PG 7.1; it was only
> earlier releases that didn't like it. But before you do that,
> would you attach to the top postmaster process (29214) with gdb
> and get a stack trace?
>
> > PS I don't know why this happened, but the only theory I have is that I am
> > running with -i to allow jdbc connections and I had port scanned the
> > machine with nmap shortly before noticing that I could no longer connect.
>
> Hmm, would you see if that's repeatable?
>
> regards, tom lane
>
------------------------------------------------------------------------
Philip Crotwell (803)777-0955 (803)777-0906 fax crotwell@seis.sc.edu
------------------------------------------------------------------------