From: | Holger Marzen <holger(at)marzen(dot)de> |
---|---|
To: | Gavin Scott <gavin(at)pokerpages(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Defunct postmasters |
Date: | 2002-02-28 19:25:02 |
Message-ID: | Pine.LNX.4.44.0202282022180.24693-100000@bluebell.marzen.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 28 Feb 2002, Gavin Scott wrote:
> On Mon, 2002-02-25 at 16:59, Tom Lane wrote:
> > Gavin Scott <gavin(at)pokerpages(dot)com> writes:
> > > We have lately begun having problems with our production database
> > > running postgres 7.1 on linux kernel v 2.4.17. The system had run
> > > without incident for many months (there were occasional reboots). Since
> > > we upgraded to kernel 2.4.17 on Dec. 31 it ran non-stop without problem
> > > until Feb 13, when postmaster appeared to stop taking new incoming
> > > connections. We restarted and then the problem struck again Saturday
> > > night (Feb 23).
> >
> > If it happens again, could you attach to the postmaster with gdb and get
> > a stack trace from it?
>
> Just happened again this morning. It turns out this looks like an
> openssl problem, not a postgresql one:
Just for the record: I once had the problem that I couldn't connect to
postgres after 7 days. A restart fixed this for 7 days more.
Solution: I had a "delete all files in /tmp that are older than 7 days"
cronjob that deleted the postgres fifo/socket.
From | Date | Subject | |
---|---|---|---|
Next Message | jtp | 2002-02-28 19:54:34 | killed select? |
Previous Message | Dino Hoboloney | 2002-02-28 18:57:17 | SQL statement : list table details |
From | Date | Subject | |
---|---|---|---|
Next Message | jtp | 2002-02-28 19:54:34 | killed select? |
Previous Message | Peter Eisentraut | 2002-02-28 19:20:08 | Re: elog() patch |