Well, I killed it. Oddly giving a "stop" to the rc script hung after I did
the kill -9. Not sure if that matters.
At any rate, I restarted, and the database seems just fine after repeated
port scans. So either that was just coincidental, or it was a
combination of the port scan and something else???
I will keep an eye on things, and repost if it locks up again after a port
scan, but for now I seem to be ok.
thanks for your help,
Philip
On Fri, 11 May 2001, Tom Lane wrote:
> > (gdb) bt
> > #0 0x4013da02 in __libc_accept () from /lib/libc.so.6
> > #1 0x80c34b9 in StreamConnection ()
> > #2 0x80e07b1 in ConnCreate ()
> > #3 0x80e0239 in ServerLoop ()
> > #4 0x80dfdb3 in PostmasterMain ()
> > #5 0x80c3fa5 in main ()
> > #6 0x400a39cb in __libc_start_main (main=0x80c3ec0 <main>, argc=4,
>
> Hmph. Waiting to accept a connection that's evidently not coming
> through. Maybe that portscan did cause this.
>
> I'd say go ahead and kill it, and after restarting try another portscan
> to see if that really does cause the problem.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
------------------------------------------------------------------------
Philip Crotwell (803)777-0955 (803)777-0906 fax crotwell@seis.sc.edu
------------------------------------------------------------------------
